To complete Historical Server configuration, perform the following steps:
Add connectivity information for Historical Server.
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. Add connection information either to sql.ini files or to a directory service. See Open Client/Server Configuration Guide for Desktop Platforms for more information on any of the following procedures and on ocscfg or dsedit.
If you are relying on sql.ini files for making client/server connections, then check the server listings in the sql.ini file. For Historical Server to run, this file must contain entries for all of the following servers:
Any Adaptive Server you want to monitor.
A Monitor Server paired with each Adaptive Server.
Historical Server. Entries for Historical Server should exist, since the Sybase installation process adds them. However, since the Adaptive Server/Monitor Server pairs usually are running on a different machine from Historical Server, entries probably do not exist for them on the Historical Server machine. If this is the case, you need to add entries for each Adaptive Server/Monitor Server pair to which Historical Server intends to connect.
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 is configured to examine the appropriate sql.ini or interfaces 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 edit a sql.ini file using a text editor
instead of dsedit, make sure that a carriage
return exists at the end of the last line in the file.
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 is 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.
Configure Historical Server client machines.
This task enables clients to connect to Historical Server. Historical Server clients are users who create recording sessions or playback sessions. Each client machine must be configured appropriately.
If you are relying on sql.ini files for making client/server connections, then update all of the sql.ini files used by Historical Server clients. The client sql.ini files must contain entries for:
Historical Server.
The Monitor Server associated with each Adaptive Server listed.
Any Adaptive Server that you want Historical Server to collect data for.
Use dsedit to add entries to a sql.ini file. To add these entries, you must know the following information:
Historical Server name.
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.
If you are relying on a directory service for making client/server connections, then make sure that the libtcl.cfg file on all Historical Server client machines points to the appropriate directory service.
Use ocscfg to check and update libtcl.cfg files.
Review start-up parameters in the NT Registry.
This task ensures that the default start-up parameter values that the installation process inserted into the NT Registry are suitable for your site.
When you start Historical Server using the Control Panel Services window, the server reads its start-up parameters from the NT Registry entry. If you start the server from command-line or by means of a batch file, Historical Server uses the start-up parameters from both the registry entry and from the command. If the same parameter appears in both places, the value specified in the command takes precedence over the value in the registry entry. If you do not specify any start-up parameters in the command, by default all of the NT Registry entry parameters are used.
