Starting, Stopping, and Restarting Host Integrator Components

The procedure for starting and stopping Host Integrator components varies depending on whether you are running a Windows or UNIX system.

From the Administrative WebStation

When the Administrative WebStation is in configure mode, you can restart and stop servers using the Restart and Stop buttons above the Administrative WebStation navigation tree. To do this, select the server you want to restart or stop, and then click the appropriate button.

Microsoft Windows Systems

You can start or stop AADS, Administrative WebStation, Host Emulator, Log Manager, Session Server, and Web Server from the Windows Start menu:

  1. Click Start > Programs > Attachmate Verastream > Host Integrator > Services and point to AADS, Administrative WebStation, Host Emulator, Log Manager, Session Server, or Web Server
  2. Click Start or Stop. You can also use the Restart All, Start All, and Stop All options.

About Windows Services

The following are installed as Windows services:

Windows Service Host Integrator Component
Verastream Host Integrator Admin Webstation Administrative WebStation
Verastream Host Integrator Directory Server AADS server
Verastream Host Integrator Host Emulator Host Emulator
Verastream Host Integrator Session Server Host Integrator Server
Verastream Host Integrator Log Manager Log Manager
Verastream Host Integrator Web Server Web page server for generated Web applications

Red Hat Linux, SUSE Linux, Sun Solaris, and AIX Systems

The Host Integrator installation program installs scripts for starting and stopping components into the Host Integrator bin directory. The bin directory is located under the directory the Host Integrator install directory, for example usr/local/vhi/bin. This directory, and its contents, has user-only read, write, and execute privileges. Since you must log on as root to install Host Integrator, only root has access to the bin directory.

Note: If necessary, someone without root access can start or stop components after they have been installed. See technical note 10016 on the support site, "Running Verastream Using a Root or Non-Root UserID."

Use the atstartcommand to start or stop one or all Host Integrator Servers.

The following examples start and stop all Host Integrator Servers:

atstart -start all
atstart -stop all

To check status, use

atstart -status.

Note: You can also start this from a batch file in Windows using NET START or using a command such as the following:

 "C:\Program Files\VHI\bin\atstart.exe" -start server 

Configuring Host Integrator Server to Run as a System Daemon

Run the Host Integrator Server as a system daemon to have the server start when the system starts and to restart it on demand or after a system exception.

Host Integrator includes a script for running the server as a system daemon. Instructions for installing and activating this script on Solaris, AIX, and Linux systems are listed below.

Red Hat Linux 3.0 and 4.0 ES, SUSE Linux (running on a mainframe)

To configure Host Integrator Server to run as a system daemon on supported Red Hat and SUSE Linux systems:

  1. Log on as root and change to the Host Integrator examples directory, located in the Host Integrator install directory, for example,usr/local/vhi/examples.
  2. The examples directory contains a script file called vhi. Save this script file as /etc/init.d/vhi.
  3. Make the script executable by typing the following command at the command prompt:

     chmod +x /etc/init.d/vhi
  4. Create a symbolic link by typing the following command at the command prompt:
    ln -s /etc/init.d/vhi /etc/rc.d/rc5.d/S99vhi

Note: On Linux systems, you can specify the order in which start and kill scripts are run at startup, shutdown, or when changing between run levels by appending an "Sxx" or "Kxx to the beginning the script name, where "S" stands for "start link," "K" stands for "kill" or "stop" link and "xx" specifies the script's number.

At startup or when changing between run levels, the operating system invokes all scripts appended with Sxx in ascending numerical order, and at shutdown it invokes all scripts appended with Kxx in numerical order. In this example, the S99vhi script is invoked at startup after as many as 98 other scripts. Be sure that you run the Host Integrator startup script after all processes it depends on have been started.

Sun Solaris

To configure Host Integrator components to run as system daemons on Solaris systems:

  1. Log on as root and change to the Host Integrator examples directory. The examples directory is under the directory where Host Integrator is installed, for example usr/local/vhi/examples.

  2. The examples directory contains a script file called vhi. Store this script file as /etc/init.d/vhi.

  3. Make the script executable by typing the following command at the command prompt:
    chmod +x /etc/init.d/vhi
  4. Create a symbolic link by typing the following command at the command prompt:
    ln -s /etc/init.d/vhi /etc/rc3.d/S99vhi

  5. The Host Integrator Server daemon will be started near the end of the system boot procedure.

AIX

To configure Host Integrator Server to run as a system daemon on AIX systems:

  1. Log in as root and change to the VHI/examples directory.
  2. Copy the example start up script "vhi" from the VHI examples directory on the AIX machine to the /etc directory.
  3. Save the script as rc.vhi.
  4. Make rc.vhi executable by typing the following command:
    chmod +x /etc/rc.vhi
  5. Open for edit /etc/rc.tcpip and add the following lines at the end:
    # Start up VHI
    start /etc/rc.vhi "" "start"

    This command starts AADS, the Host Integrator Server and LogManager at the end of the boot sequence. Add additional Host Integrator components to the "rc.vhi" as needed (Administrative WebStation or Host Emulator).