Configure the Servers for Database Instances (UNIX and Linux)

Configuring the Broker and Server › Broker and Server Communication › Broker Setup for Multiple Server Instances › Configure the Servers for Database Instances (UNIX, Linux, and zLinux)

Configure the Servers for Database Instances (UNIX, Linux, and zLinux)

Note: The instances of Linux in this section refer to both the Linux and zLinux operating environments.

You can configure CA Harvest SCM servers to connect with distinct database instances. The server must be installed prior to performing this step.

Follow these steps:

For each database instance, create a CAI/PT ODBC datasource connection to the database instance.
In the $ODBC_HOME/bin directory, run the configdsn utility to define an ODBC datasource name (DSN).
Select option 1 to add a new datasource.
Enter a name to identify the datasource. For example, enter CA Harvest SCM to indicate a datasource to be used with the product.
Note: Make note of the datasource name, as it will be used later in the installation. In addition, datasource names for CAI/PT ODBC cannot include an underscore character '_'.
Select an existing driver definition by number. Enter the number corresponding to the appropriate CAI/PT DBMS driver.
Follow the DMBS-specific questions:

ORACLE
1. (Optional) Enter a description).
2. Enter the Oracle Net*8 global alias name that identifies the database instance.
3. Enter the following semicolon separated arguments to properly configure the SQLDriverConnect string at the SQLDriverConnect format prompt:
```
EnableScrollableCursors=1;ApplicationUsingThreads=1
```
4. (Optional) Enter the server type.
  “ServerType” refers to the class of Net server accessing the database server installation. If the database server installation is being accessed through an Enterprise Access or EDBC server, specify the gateway server. Valid definitions are:
  - Advantage EDBC-DCOM (Datacom), IDMS, DB2, IMS, VSAM
  - Advantage Enterprise Access-RDB, RMS, ORACLE, INFORMIX, SYBASE, MSSQL and DB2UDB
5. Enter the “BlankDate” Value (optional).
  1. Valid settings are Y (default) or N. N causes the ODBC driver to return the date value of 9999-12-31 23:59:59 for empty date values. Most applications prefer to receive a more meaningful NULL value when displaying an empty string date.
  2. Enter an optional semicolon-separated list of other records (optional).
The product does not require a list of additional arguments to this prompt.
Select option number 6 to exit the program.
Create a version directory in the $CA_SCM_HOME for each server version. The default server version uses the $CA_SCM_HOME location. A server version directory is needed only for a nondefault server.
For example, suppose you are using the default server and two server versions named version1 and version2. Create two version directories in the $CA_SCM_HOME location: $CA_SCM_HOME/version1 and $CA_SCM_HOME/version2.
In each server version directory, create a log directory. For this example, create $CA_SCM_HOME/version1/log and $CA_SCM_HOME/version2/log.
Copy the HServer.arg file in the $CA_SCM_HOME directory into each server version directory.
Edit each HServer.arg file. Change the datasource name to a datasource created in Step 1. The datasource name follows the ‑datasource= flag in the HServer.arg file.
Modify the HBroker.arg file found in the $CA_SCM_HOME directory to specify the startup parameters for the server versions. The parameters are:

-dirserver[_version]=dir

Specifies the directory containing the server process. Replace dir with the full path to the $CA_SCM_HOME/bin directory.

-minserver[_<version>]=<int>

Specifies the minimum number of server processes to be started.

-maxserver[_<version>]=<int>

Specifies the maximum number of server processes to be started.

-homeserver[_<version>]=<home >

Specifies the directory containing the server process argument file, HServer.arg. The default is the CA_SCM_HOME location.

-queuesize[_<version>]=<int>

Specifies the number of requests allowed in queue before the broker starts a temporary server.

The following is a sample HBroker.arg file based on the previous example.
```
//Default Version: Broker
-dirserver=/home/ca scm-d/bin
-minserver=5
-maxserver=50 
-queuesize=2
```
```
// Version: Broker/version1
-dirserver_version1=/home/ca scm-d/bin
-minserver_version1=3
-maxserver_version1=10
-queuesize_version1=10
-homeserver_version1=/home/ca scm-d/version1
// Version: Broker/version2
-dirserver_version2=/home/ca scm-d/bin
-minserver_version2=3
-maxserver_version2=10
-queuesize_version2=10
-homeserver_version2=/home/ca scm-d/version2
```
When the broker is started, five default servers, three servers of version1, and three servers of version2 are also started. When no version tag is appended to a parameter name, the default value is used. In the homeserver directory, an HServer.arg must exist that specifies the configuration for that pool of server processes such as their distinct (nondefault) database information. The default location of homeserver is the $CA_SCM_HOME directory.
Store and encrypt the database username and password using the svrenc utility in the $CA_SCM_HOME/bin directory. For instructions to use svrenc, enter the following command from the $CA_SCM_HOME/bin directory:
```
./svrenc -h
```
This utility creates a hidden file that stores the encrypted database username and password for the product server. For example, to create an encrypted file for the server version1 using a database user named admin, execute the following command:
```
./svrenc -s -usr admin -pw admin -dir /home/ca SCM/version1
```
Note: This utility has already been run for the “default” server during installation.
Start the broker from the $CA_SCM_HOME/bin directory by entering the following command:
```
./bkrd
```
To connect to a particular version of the product, enter brokercomputer/versionname into the Broker field for the GUI or command line argument. To connect to server version1 using broker computer cascmcm, specify the broker name as cascmcm/version1.

More information:

Install the Server (Typical Installation)