Manually Starting and Stopping VHI Services

  • 7021352
  • 06-Feb-2003
  • 02-Mar-2018

Environment

Verastream Host Integrator

Situation

This technical note describes the Verastream Host Integrator (VHI) services and explains how to manually start and stop the VHI services, if necessary.

Verastream Host Integrator Services

There are several Host Integrator services. The services you have installed will depend on your product version, platform, product edition (Development Kit or Sever Kit), and options selected during installation.

Service
Description
Session Server
Runtime engine that loads deployed models, connects to host systems, and services requests from clients.
Log Manager
Captures runtime messages in log files, and handles SNMP and e-mail notification. For more information on logging, see KB 7021303.
Management Server
(Version 7.0 or higher) For more information about Management Server, see KB 7021563.
Administrative WebStation
(Version 6.6 or earlier) Enables administrators to use a web browser to view and configure session servers, security, and load balancing domains.
Web Server
Runs web projects generated by Web Builder.
Host Emulator
Simulates a host (3270 or 5250 only) for demonstration, training, or testing purposes.

For information on checking the status of services, see KB 7021540.

Automatic vs. Manual

On Windows, the services are installed to start automatically on system startup. For Linux, Solaris, or AIX, the Installation Guide describes how to configure the system to start services automatically (https://support.microfocus.com/manuals/vhi.html).

In some circumstances, such as after editing certain configuration files or changing your system network configuration, you may need to manually restart the services so changes can take effect. In version 6.6 and earlier, changes to security settings do not take effect until the session server service is restarted.

Resolution

The methods and steps to manually restart, stop, or start services depends on whether you are running version 7.0 or higher, or version 6.6 or earlier.

Version 7.0 or Higher

All of the following methods require running the tool or command as administrator on Windows, or as a super-user on Linux/UNIX. Beginning in version 7.0, the individual services can be started or stopped in any sequence order.

Windows Administrative Tools

On Windows platforms, the Verastream services can be individually started, restarted, or stopped using the standard Services or Computer Management utilities (in Control Panel > Administrative Tools).

Verastream Administrative Console

Session Server, Management Server, and Host Emulator services running on Windows and Linux/UNIX servers can be conveniently restarted or stopped within the Administrative Console application (running on Windows).

Figure 1. Right click context menu in Administrative Console
Figure 1. Right click context menu in Administrative Console
  • Session Server: In Session Server Explorer (Perspective > Host Integrator > Session Servers), right click a session server for Restart and Shut Down options.
  • Management Server: In Management Server Explorer (Perspective > Management > Servers), right click a management server for Restart and Shut Down options. Note: Restarting or stopping the management server will end your Administrative Console session.
  • Host Emulator: In Host Emulator Server Explorer (Perspective > Host Integrator > Host Emulator), right click a server for the Stop Host Emulator Server option.

Command Line Methods

The following commands or scripts can be run at a shell command prompt, called from other scripts, or run from a shortcut that you create. Note: To avoid problems on Windows, see Using the Installed Batch Files on Windows below.

Service
Action
Windows .bat file in C:\Program Files\Verastream\HostIntegrator\bin\services
Linux/UNIX command in /opt/attachmate/verastream/hostintegrator/bin
All
Restart
restartall.bat
atstart -restart all
All
Start
startall.bat
atstart -start all
All
Stop
stopall.bat
atstart -stop all
Management Server
Restart
"MgmtServer\Restart Management Server.bat"
atstart -restart mgmtserver
Management Server
Start
"MgmtServer\Start Management Server.bat"
atstart -start mgmtserver
Management Server
Stop
"MgmtServer\Stop Management Server.bat"
atstart -stop mgmtserver
Session Server
Restart
"SessionServer\Restart Session Server.bat"
atstart -restart server
Session Server
Start
"SessionServer\Start Session Server.bat"
atstart -start server
Session Server
Stop
"SessionServer\Stop Session Server.bat"
atstart -stop server
Log Manager
Restart
"LogManager\Restart Log Manager.bat"
atstart -restart logmgr
Log Manager
Start
"LogManager\Start Log Manager.bat"
atstart -start logmgr
Log Manager
Stop
"LogManager\Stop Log Manager.bat"
atstart -stop logmgr
Web Server
Restart
"WebServer\Restart Web Server.bat"
(Version 7.5+) atstart -restart webserver
Web Server
Start
"WebServer\Start Web Server.bat"
(Version 7.5+) atstart -start webserver
Web Server
Stop
"WebServer\Stop Web Server.bat"
(Version 7.5+) atstart -stop webserver
Host Emulator
Restart
"HostEmulator\Restart Host Emulator.bat"
atstart -restart hostemul
Host Emulator
Start
"HostEmulator\Start Host Emulator.bat"
atstart -start hostemul
Host Emulator
Stop
"HostEmulator\Stop Host Emulator.bat"
atstart -stop hostemul

On Windows, in version 7.0 and higher, there is no longer an atstart.exe file. The batch files above run different atstart_*.exe files.

Using the Installed Batch Files on Windows

To avoid problems, use the installed *.bat files as follows:

  • Run the .bat files as an administrator.
  • When the .bat file name contains space characters, enclose the command in double quote characters. Otherwise, you may see an error such as 'Stop' is not recognized as an internal or external command, operable program or batch file.
  • (Version 7.0 only) Edit the .bat files to insert an appropriate cd (change directory) command at the beginning. (The installed version 7.0 .bat files are only designed to run with their folder locations as the current directory. Beginning in version 7.1, the .bat files automatically change directories appropriately.) Examples:
    • In restartall.bat, startall.bat, and stopall.bat files: insert cd %VHI_ROOT%\bin\services
    • In MgmtServer .bat files: insert cd %VHI_ROOT%\bin\services\MgmtServer

Alternatively, you could open a Command Window (as administrator) and cd to the appropriate subdirectory before running the .bat file.

Note: If you create a shortcut to run a .bat file, the folder location in the shortcut properties is ignored when running as administrator on Windows 7, Windows Server 2008, or Windows Vista with User Account Control (UAC) enabled. Regardless of the shortcut properties, C:\Windows\System32 is used as the current directory. To resolve this issue, use a cd command as described above.

  • If you still have problems with service states remaining unchanged after running a .bat file, open a Command Prompt window (as administrator) to run the .bat file. This will enable errors to be visible after the script has finished. (If you open the .bat file in Windows Explorer, the window automatically closes.)
  • After running the installed restartall.bat file, the Log Manager service may be in a stopped state. To resolve this issue, modify the restartall.bat file. Change the restart command to separate stop and start commands as shown below.
CD %VHI_ROOT%\bin\services
IF EXIST ..\atstart_webserver.exe ..\atstart_webserver.exe -restart webserver

IF EXIST ..\atstart_logmngr.exe ..\atstart_logmngr.exe -stop logmgr
IF EXIST ..\atstart_logmngr.exe ..\atstart_logmngr.exe -start logmgr

IF EXIST ..\atstart_server.exe ..\atstart_server.exe -restart server

IF EXIST ..\..\..\ManagementServer\bin\wrapper-windows-x86-32.exe net stop vms
IF EXIST ..\..\..\ManagementServer\bin\wrapper-windows-x86-32.exe net start vms

IF EXIST ..\..\hostemulator\bin\wrapper-windows-x86-32.exe net stop HostEmulator
IF EXIST ..\..\hostemulator\bin\wrapper-windows-x86-32.exe net start HostEmulator

Using atstart on Linux/UNIX

When running atstart -start all or atstart -restart all, if you see the message "TCP listening port required by the requested VHI service is in use" and one of the services is not started (as indicated by atstart -status), wait 2 minutes and enter a command to start that service (such as atstart -start logmgr).

Version 6.6 or Earlier

The following information applies to Host Integrator versions 6.6 and earlier.

Starting VHI Services

In Windows:

If you need to manually start VHI 6.x services, use the installed shortcuts:

For VHI 6.5 or 6.6: click Start > Programs > Attachmate Verastream > Host Integrator > Services > Start All.

For VHI 6.0: click Start > Programs > AttachmateWRQ Verastream > Host Integrator > Services > Start All.

Note: If you start the services individually, follow the startup sequence noted below.

The shortcuts run <VHI>\bin\atstart commands. Instead of using the installed shortcuts, you can use the Windows NET START command or Services console to start services individually.

In UNIX/Linux:

VHI services must be manually started (unless the system administrator configures the UNIX/Linux system to automatically load the services on system startup).

To start all VHI services in the correct sequence (including optional services), navigate to the /usr/vhi/bin directory and enter the following command:

atstart -start all

This command starts all of the installed VHI services in the correct sequence.

The atstart command can also be used to start individual services. To view the available command options, use the following command:

atstart -help

Note: If you start services individually, follow the startup sequence noted below.

The Startup Sequence

VHI services must be started in the following order:

  1. Verastream Host Integrator Log Manager
  2. Verastream Host Integrator Directory Server (AADS)
  3. Verastream Host Integrator Session Server
  4. Any of the optional services required for the desired functionality:
- Verastream Host Integrator Web Server
- Verastream Host Integrator Administrative WebStation
- Verastream Host Integrator Host Emulator

Stopping the VHI Services

In Windows:

If you need to manually stop VHI 6.x services, use the installed shortcuts:

For VHI 6.5 or 6.6: click Start > Programs > Attachmate Verastream > Host Integrator > Services > Stop All.

For VHI 6.0: click Start > Programs > AttachmateWRQ Verastream > Host Integrator > Services > Stop All.

Note: If you manually stop the services individually, follow the shutdown sequence, noted below.

The shortcuts run <VHI>\bin\atstart commands. Instead of using the installed shortcuts, you can use the Windows NET STOP command or Services console to stop services individually.

In UNIX/Linux:

Use the following command to manually stop VHI services in the correct sequence:

atstart –stop all

Note: If you stop the services individually, follow The Shutdown Sequence noted below.

The Shutdown Sequence

VHI services must be stopped in the following order, which is the reverse of the startup sequence:

  1. Any of the optional services running:
- Verastream Host Integrator Web Server
- Verastream Host Integrator Administrative WebStation
- Verastream Host Integrator Host Emulator
  1. Verastream Host Integrator Session Server
  2. Verastream Host Integrator Directory Server (AADS)
  3. Verastream Host Integrator Log Manager

Additional Information

Legacy KB ID

This article was originally published as Attachmate Technical Note 10004.