|
|
|
How to Verify Verastream Servers are Running
Technical Note 10054
Last Reviewed 21-Jul-2006
Applies To
Verastream Host Integrator version 5.5 or higher
Summary
Technical Note 10054
Last Reviewed 21-Jul-2006
Applies To
Verastream Host Integrator version 5.5 or higher
Summary
This technical note explains how to check that the Verastream Session Server and AADS (Authentication Authorization and Directory Services) components are running on a Windows or UNIX system.
Windows Method 1
Use the following steps to verify that the Verastream servers are running on Microsoft Windows.
- Go to Control Panel > Administrative Tools > Services.
- Look for the services named "Verastream Host Integrator Directory Server" and "Verastream Host Integrator Session Server."
- Verify the Status is "Started."
Note: This view does not automatically refresh if the status changes. Refresh the view to display the current status.
Windows Method 2
Use the following alternative steps to verify that the servers are running on Windows.
- Open Windows Task Manager. (Press Ctrl+Alt+Delete.)
- Click the Processes tab.
- Verify "VhiAads.exe" and "sesssrvr.exe" are listed.
UNIX Method 1
Use the following steps to verify that the Verastream servers are running on UNIX.
- Login as root.
- At the shell command prompt, run the atstart -status command from the VHI bin directory.
- Verify that AADS and Server appear as "Started."
UNIX Method 2
Use the following alternative steps to verify that the servers are running on UNIX. This can be performed by non-administrative users.
- At the shell command prompt, run the ps command to list VHI processes, for example:
ps –aef | grep vhi- Verify "sesssrvr" and "aadsserver.jar" processes are listed.
Note: VHI processes may be listed by their atstart and java startup commands.
UNIX Method 3
Use the following steps to verify that the servers are running on a remote system and reachable over the network. This is particularly useful for testing connections through a firewall and can be performed by non-administrative users.
Note: The VHI atping utility is undocumented and available on UNIX only.
- At the shell command prompt, run the atping command from the VHI bin directory using the following syntax:
atping <component> <servername> -dwhere:
- <component> is aas or dirservice for AADS, or msession for Session Server.
- <servername> is the AADS common name, server DNS host name, or localhost for the local UNIX system.
For example:
atping msession myvhiserver.mycompany.com –d- The Return value displayed will be 0 for success, 1 for failure, or 2 for a syntax error with the command line arguments.
