Table of Contents
Advertisement
Configuring multiple instances of Historical Server
Configuring Historical Server client machines
30
•
Add Historical Server to the appropriate directory service, using
. You must know the Historical Server name to complete this
dsedit
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
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.
The configuration task differs depending on whether you are using sql.ini files
or a directory service for making client/server connections.
•
If you are using 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
to add entries to a sql.ini file. To add these entries, you must
dsedit
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
To research this information, use
configured to examine the appropriate sql.ini file.
•
If you are relying on a directory service for making client/server
connections, make sure that the libtcl.cfg file on all Historical Server client
machines points to the appropriate directory service.
Use
to check and update libtcl.cfg files.
ocscfg
and
.
ocscfg
dsedit
dsedit
on the machine where a server is
Historical Server
Advertisement
Table of Contents
