This task assigns a port or network address to Historical Server. It also ensures that Historical Server can connect to one or more Adaptive Server/Monitor Server pairs.
This task differs depending on whether you rely on sql.ini files or a directory service for making client/server connections:
If you are relying on sql.ini files for making client/server connections, check the server listings in the sql.ini file for the Historical Server machine. For Historical Server to run, this file must contain entries for all of the following servers:
Any Adaptive Server you want to monitor
Monitor Server paired with each Adaptive Server
Use dsedit to add entries to a sql.ini file. To add these entries, you must know the following information:
Monitor Server and Adaptive Server names to which you want Historical Server to connect.
Port numbers or network addresses assigned to these servers when they were configured.
If you need to research this information, use dsedit on the machine where a server was configured to examine the appropriate sql.ini file.
The Adaptive Server name must not be an alias name. It must be the name that Monitor Server knows it by. For example, use the value you used in the -S parameter in the Monitor Server start-up command.
If you are relying on a directory service for making client/server connections:
Make sure that the libtcl.cfg file on the machine where Historical Server was installed points to the appropriate directory service. Use ocscfg to check and update libtcl.cfg files.
Add Historical Server to the appropriate directory service, using dsedit. You need to know the Historical Server name to complete this step. The default name created by the installation process is in the format machineName_hs. For example, smith_hs.
See Open Client/Server Configuration Guide for Desktop Platforms for instructions on using ocscfg and dsedit.