Starting and stopping the server

Server startup overview

Before you start the Gateway server

Starting and stopping the Gateway server

Starting and stopping the Navigator server

Starting and stopping the Axway MFT Navigator server

After you start the Gateway server

After you stop the Gateway server

Server startup overview

Gateway is composed of a group of related executable programs. The programs activated at startup depend on the options chosen during installation and configuration.

UNIX environments

Specify whether or not the server daemons (for the Gateway user interface) are started at the same time as the product. By default, the server daemons start automatically.

Windows environments

Start Gateway in one of two ways:

• Manually: select Start in the Gateway program folder created by the installation process
• Automatically: configure Gateway as a service to automatically start on system start

After startup is completed, select Process List in the Gateway program folder to view the list of currently activated programs.

Before you start the Gateway server

Before starting Gateway, check the network resources needed for communication between Gateway and its partners.

IPC Queues

Gateway uses the OS's IPC queues for inter-process communication.

Refer to the Installation Guide > Gateway kernel prerequisites for their configuring to avoid delays during high-load.

TCP/IP subsystems

To check that you can reach remote systems from your computer, use the standard ping command with the hostname or IP address as argument. For more details, refer to the ping documentation supplied with your system.

SNA LU 6.2 subsystems

To check the SNA configuration, activate each LU 6.2 connection that Gateway uses.

If you are unable to activate LU-LU sessions, check the LU 6.2 local and remote parameters.

If LU-LU sessions are activated, and the session establishment failed at file transfer time, check that:

• The Remote Site is active, and
• The mode and the transaction name requested in CPI symbolic destination are defined in the Remote Site

If the problem persists, activate the audit function and the SNA trace.

Starting and stopping the Gateway server

You do not have to initialize this version of Gateway. The Installer executes the gateinit command for you.

Windows environments: Starting

To start Gateway, go to the Windows Start menu and select:

Programs > Axway Software > Axway [ProjectName]> Gateway > Start Gateway

You can configure Gateway to continue running between login sessions by installing it as a system service.

Windows environments: Stopping

To stop Gateway, go to the Windows Start menu and select:

Programs > Axway Software > Axway [ProjectName]> Gateway > Stop Gateway

If you started Gateway as a system service, you must stop it via a Service applet in the Control Panel. Alternatively, use the net stop xxxxx command.

The Axway MFT Navigator server and the Gateway GUI server stop at the same time as the product.

UNIX environments: Starting and stopping

The gatestart and gatestop utilities enable you to start and stop Gateway in the UNIX environment.

Before using Gateway program files, set the product environment for your UNIX session.

Execute the Shell script profile, located by default in:

<Gateway installation directory>/run_time/etc

Starting

To start Gateway, enter the command:

gatestart

This command starts Gateway, and by extension, activates the tracking functions of the Mailbox. Use this command when Gateway is stopped.

Note: Do not use the pelmon start command that was used in earlier versions of Gateway.

Stopping

To stop Gateway, enter the command:

gatestop

This command shuts down Gateway, and by extension, stops Mailbox tracking.

Note: Do not use the pelmon stop command that was used in earlier versions of Gateway.

Starting and stopping the Navigator server

In Windows and UNIX environments, the Gateway Navigator server (GUI server) starts and stops at the same time as Gateway.

Starting and stopping the Axway MFT Navigator server

The MFT Navigator server starts and stops at the same time as Gateway.

After you start the Gateway server

After starting Gateway, check the Gateway processes.

Windows environments

After startup is completed, select Process List in the Gateway program folder to view the list of currently activated programs.

UNIX environments

Status

Use the gatestatus command to obtain the current status of Gateway, and by extension, the Mailbox.

Note: Do not use the pelmon status command that was used in earlier versions of Gateway.

For a list of possible responses, refer to About gatestatus messages.

Processes

After entering the gatestart or gatestop command, check that Gateway processes have correctly started or stopped.

Enter the command:

ps –e | grep -E " p_| q_| h_| notif| ipelapi"

When Gateway is started, the ps (or Process List) command must show a supervisor process (p_sup) and a system process (p_sys).

Other processes are launched depending on the networks, protocol resources used and product options (for example, Sentinel).

For TCP/IP networks

Use the following commands to specify the appropriate protocol for the TCP/IP network.

For SNA networks

Use the following command to specify the appropriate protocol for the SNA network.

Only the PeSIT E protocol is supported for SNA.

SNA processes are not started when you start Gateway. These processes are started when a connection occurs. For this reason, they are referred to as dynamic processes.

Multiple processes for the same protocol can be displayed if several connections occur. These processes stop when the connections are dropped.

Message queues (UNIX environments)

Gateway uses message queues. In the UNIX environment, use the ipcs command to check that the message queues are started.

ipcs –q | grep <OWNER>

After you stop the Gateway server

When you stop Gateway, you should also stop the list of processes being printed, and delete the message queues.

Checking the status of processes

Process traces can be found in the folder p_home_dir/run_time/tmp. Select the file that corresponds to your process to view messages that describe why processes are not launched.

The following table lists the types of trace file (where XX is the PID number of the process).

Related topics

About gatestatus messages