Changing the Service Manager's configuration port

You can change the configuration port used by the Host On-Demand Service Manager and the clients. The default port of 8999 can be mapped to any available port number. If you are using Host On-Demand through a firewall, the port you set to be the configuration port must be opened on the firewall.

To change the configuration port to 12345, you need to make changes to the Service Manager, the clients and the configuration servlet (if you are using it):

To change the configuration port the Service Manager listens to:

Stop the Service Manager.
Go to the private directory of the Host On-Demand server (for example, C:\Program Files\IBM\HostOnDemand\private).
Edit the NSMprop file to add
```
ConfigServerPort=12345
```
to the bottom of the file.
Restart the Service Manager.

There are other methods you can use to set ConfigServerPort for the Service Manager. Choose the easiest or most convenient method:

Go to the private directory of the Host On-Demand server (for example, C:\Program Files\IBM\HostOnDemand\private ). Edit the NSMprop file to make the second parameter of CONFIGSERVER_PARMS "12345" instead of 8999 (this method provides compatibility with previous versions of Host On-Demand).
Add /ConfigServerPort=12345 to the end of the command you use to start the Service Manger, or edit the script that is used to start the Service Manager so that the ConfigServerPort parameter is passed to it.
On Windows NT, add the ConfigServerPort parameter to the registry entry for the Service Manager (on Windows NT the Service Manager runs as service):
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMServiceManager\Parameters\AppParameters
```
On OS/400, use CFGHODSM to add the ConfigServerPort parameter.

Because there are several ways to specify a different configuration port for the Service Manager, there is a precedence that takes place based on where the parameter is set:

First is a command line parameter, such as /ConfigServerPort=12345.
Second is the ConfigServerPort entry in the NSMprop file
Third is the setting of the second parameter of CONFIGSERVER_PARMS in the NSMprop file

Next, change the port the Host On-Demand clients use:

Go to the publish directory of the Host On-Demand server (for example, C:\Program Files\IBM\HostOnDemand\private\HOD).
If necessary, create the file config.properties.
Edit config.properties to add
```
ConfigServerPort=12345
```
to the file.
Force any active Host On-Demand clients to re-read config.properties by clearing your browser's cache and reloading the Host On-Demand applet.

If you need to edit config.properties for an z/OS server, first transfer the file in binary to an ASCII based system such as Windows or Unix. Edit the file and then transfer it back to the z/OS system in binary. If you need to create a config.properties file, do so on an ASCII system and then transfer the file to the z/OS server in binary. The reason for this is that the client applets expect ASCII text in config.properties, but files created or edited on z/OS are stored in EBCDIC.

When any parameter is set in a config.properties file, all clients will use that parameter. However, each client can be configured individually by adding parameters to the client HTML. You can use the Deployment Planning Wizard to build customized HTML client pages. The wizard sets applet parameters in the HTML it creates based on your input, so you don't have to learn the syntax and valid parameter values. It is recommended that you use the Deployment Planning Wizard to build client pages. The wizard can't be used to edit HTML pages you create manually. It also can't be used to edit HTML pages that are created with the wizard, but are later edited manually. If you find you need to manually modify the HTML, use the param tag inside the applet tag to set the ConfigServerPort. For example, you can add

<PARAM_NAME=ConfigServerPort VALUE=12345>.

to the applet tag in HTML file.

Because there are several ways to specify a different configuration port for the clients, there is a precedence that takes place based on where the parameter is set:

First is the ConfigServerPort parameter set in the client HTML.
Second is the ConfigServerPort set in the config.properties file.

If you are using the configuration servlet and you change the Service Manager port, you will need to set the ConfigServerPort parameter for the configuration servlet. For example, if you change the Service Manager port to 12345 you need to pass the ConfigServerPort=12345 parameter to the configuration servlet so it can communicate with the Service Manager. Check your web server or servlet engine documentation for information about how to pass parameters to servlets.