Configuration procedures on UNIX platforms

To configure Historical Server on a UNIX platform:

Set the $SYBASE environment variable to the value of the Sybase installation directory where you unloaded Historical Server.
Log on using the “sybase” account or another account that has read, write, and search (execute) permissions on the $SYBASE directory.
Set the $PATH environment variable.

The Historical Server executable resides in $SYBASE/bin. Add this path name to the $PATH environment variable for the account that will start Historical Server.
Create a script file for Historical Server start-up.

A script file ensures that correct start-up parameters are used for each Historical Server start-up. The script file contains the Historical Server start-up command, histserver, and its parameters.

To create a Historical Server script file:
1. Using any editor, create a new file. The recommended name and location for the new file is:
```
	install_dir/install/run_histServerName, 
```
  where histServerName is the name of the Historical Server.
2. Edit the new file, inserting the histserver command and supplying parameters and values appropriate to your installation. Do not use carriage returns within the command; use the UNIX continuation character (\) to continue the command on multiple lines. Spaces between a parameter and its value are optional.
  
  Table 2-1 describes the command and its parameters. The parameters marked “required” in the table must appear in the script file. The ones with default values may be omitted if the default values are acceptable.
  
  A sample script file for starting Historical Server follows:
```
	histserver -D server1HistDir -S server1Hist  \
 	-U sa -P saPasswd                            \
 	-l server1HistLog -n 15 &
```
3. Use the chmod command to give the account that will start Historical Server execute permission on the script file.
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 Historical Server connection information either to the interfaces files or to a directory service. See Open Client/Server Configuration Guide for UNIX for information on dsedit, dscp, dsedit_dce, and dscp_dce.

If you are relying on interfaces files for making client/server connections:
1. Check the server listings in the interfaces file used by Historical Server. 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
2. Use either dsedit (if your system is running X Windows) or dscp (a command-line utility) to add entries to an interfaces file. Follow the instructions in Open Client/Server Configuration Guide for UNIX. To add these entries, you must know the:
  - 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 or dscp on the machine where a server was configured to examine the appropriate interfaces 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 was installed points to the appropriate directory service. Use an editor to check and update libtcl.cfg files.
- Add Historical Server to the directory service, using dsedit_dce (if your system is running X Windows) or dscp_dce (a command-line utility). You need to know the Historical Server name to complete this step.
Configure Historical Server on 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.

See Open Client/Server Configuration Guide for UNIX for instructions on using dsedit and dscp.

If you are relying on interfaces files for making client/server connections:
1. Update all of the interfaces files used by Historical Server clients. The client interfaces files must contain entries for:
  - Historical Server
  - Any Adaptive Server that you want to monitor through Historical Server
  - Monitor Server associated with each Adaptive Server listed
2. Use dsedit (if your system is running X Windows) or dscp (a command-line utility) to add entries to an interfaces file. To add these entries, you must know the following information:
  - Historical Server name.
  - Monitor Server and Adaptive Server names that you want Historical Server to connect to.
  - Port numbers or network addresses assigned to these servers when they were configured. If you need to research this information, use dsedit or dscp on the machine where a server was configured to examine the appropriate interfaces 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 a text editor to check and update libtcl.cfg files.