Sybase 12.5.1 User Manual page 31

Historical server
Table of Contents

Advertisement

User's Guide
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 must add
entries for each Adaptive Server/Monitor Server pair to which
Historical Server intends to connect.
Use
to add entries to a sql.ini file. To add these entries, you must
dsedit
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. To research this information, use
machine where a server is configured to examine the appropriate
sql.ini or interfaces file.
The Adaptive Server name cannot be an alias name. It must be
Note
the name that Monitor Server knows it by. For example, use the value
you used in the
If you edit a sql.ini file using a text editor instead of
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
to check and update libtcl.cfg files.
ocscfg
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.
2
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:
CHAPTER 2
parameter in the Monitor Server start-up command.
-S
Configuring Historical Server
dsedit
, make sure
dsedit
on the
17

Advertisement

Table of Contents
loading

Table of Contents