Host On-Demand Service Manager

The Host On-Demand Service Manager provides support for persistent user configuration, error logging, and the Redirector.

When you log on as the administrator, you may see the following error message:

The Host On-Demand client is using a Configuration Servlet URL: file:/servlet/HODConfig/hod and
is unable to contact the Host On-Demand Service Manager for one of the following reasons:

The Configuration Servlet is not installed, is not operational, or is not configured with the correct 
hostname and port number of the Service Manager.
The client's ConfigServerURL parameter does not point to the Configuration Servlet or is missing the /hod 
extension from the end of the URL.
A network problem has prevented the connection.
The Service Manager is not started, or is not operational.

Please contact your system administrator.   

This message indicates the service manager is not running.

• On Windows NT and Windows 2000, the service manager runs as a service. From the Start menu, open Control Panel > Services and start the service manager. Make sure that its Startup mode is Automatic so that it starts every time the operating system starts.



• On other platforms, the service manager runs as a Java application. Make sure this application starts every time the operating system starts.

Starting the service manager

In the Windows environment, the service manager starts automatically (through the Startup Folder in Windows 95 and Windows 98 and as an automatically started service in NT and 2000) after installation. It can also be started manually from the Start menu under Administration in the IBM Host On-Demand folder on Windows 95 and Windows 98, or from the Services control panel on Windows NT and 2000.

In other environments, you must manually start the service manager as a Java application. Sample command files for OS/2, NetWare, AIX, UNIX, and iSeries are provided in \hostondemand\lib\samples\CommandFiles. After customizing the file, run it to start the service manager.

Stopping and restarting the Service Manager

On a Windows NT or Windows 2000 server:

1. Click Start > Settings > Control Panel.
2. Open the Services folder.
3. Select the Host On-Demand Service Manager.
4. Click Stop.
5. When the service has stopped, click Start.

On a Windows 95 or Windows 98 client:

1. Press Ctrl+Alt+Del once to open the Close Program window.
2. Highlight the Java task and then click End Task.
3. Restart the Service Manager through Host On-Demand Administration in the Start menu.

On an OS/2 server:

Press Ctrl+C in the OS/2 window in which you started the Service Manager.

On a NetWare server:

From the console, enter java -exit to stop the java NLM.

On a UNIX server:

1. Determine the process ID of the Service Manager by entering the following command:

   ps -ef | grep NCServiceManager
   

The system responds with a line similar to the following:

root 20130 22944   0   Feb 16  pts/1  0:20 java
com.ibm.eNetwork.HODUtil.services.admin.NCServiceManager /usr/local/hostondemand

The number following root is the process ID (20130 in the example above).

2. Enter kill -9 20130 at the command prompt.
3. When the Host On-Demand service manager has stopped, restart it in the usual way.

On an iSeries server:

You will need *JOBCTL, *SPLCTL, *SERVICE and *ALLOBJ authority to use this command.

1. Logon to the iSeries with a security officer user profile, such as QSECOFR.



2. Type ENDHODSVM at the command line.

Related topics

• Configuring, starting, and stopping the Host On-Demand Service Manager on iSeries