Post-installation tasks for Siebel tier collectors

When the Siebel Tier Collectors have been installed, you need to perform the following post-installation tasks:

Perform any action items show in Post-installation dialog box. See Possible Post-installation action items.
Modify the SRF (required for Interpoints). See Modifying the Siebel Repository File (SQL Server) and Modifying the Siebel Repository File (Oracle).
Set up Siebel batch process sampling (required for Interpoints) See Setting up Siebel batch process sampling.
Stop and restart all Insight Savvies installed on the respective server
See the Precise Interpoint for Siebel User Guide for additional post-installation action items.

Possible Post-installation action items

Perform any action items show in Post-installation dialog box.

To perform Siebel Tier post-installation tasks

On the Finish screen, click Next.
In the Siebel Tier - Post-Installation dialog box, follow the instructions to perform all post-installation tasks.
If you have installed the Interpoint for an Oracle database, restart the Oracle Tier Collectors on the Siebel server.
Click Finish.

Modifying the Siebel Repository File (SQL Server)

Once the Siebel Tier Collectors are installed, modify the Siebel Repository File (SRF), so that Interpoint for Siebel will be able to receive notifications of Siebel-related user events.

Part of the .srf file, is a collection of callback scripts, which are triggered by various events in a user's session. A user can view or change these scripts using the Siebel Tools.

For each targeted Siebel application, modify the .srf file on the Siebel server. Define the application name by hard coding it in the Application_PreNavigate function.
The modified SRFs need to be distributed to each of the Siebel servers

If you installed Interpoint for a SQL Server database, modifying the SRF consists of the following tasks:

Creating the Interpoint project (SQL Server)
Creating the CX_VTSSPID table (SQL Server)
Creating the business component (SQL Server)
Creating the business object (SQL Server)
Adding the Application_PreNavigate()function (SQL Server)
Replacing the table with a custom view (SQL Server)
Completing the modification (SQL Server)
Debugging the script (SQL Server)

Modifying the Siebel Repository File (Oracle)

Once the Siebel Tier Collectors are installed, modify the Siebel Repository File (SRF), so that Interpoint for Siebel will be able to receive notifications of Siebel-related user events.

Part of the .srf file, is a collection of callback scripts, which are triggered by various events in a user's session. A user can view or change these scripts using the Siebel Tools.

For each targeted Siebel application, modify the .srf file on the Siebel server. Define the application name by hard coding it in the Application_PreNavigate function.
The modified SRFs need to be distributed to each of the Siebel servers

If you have installed Interpoint for an Oracle database, modifying the SRF consists of the following tasks:

Creating the Precise Interpoint project (Oracle)
Creating the CX_PSS_SBL table (Oracle)
Creating the business component (Oracle)
Creating the business object (Oracle)
Adding the Application_PreNavigate() function (Oracle)
Replacing the table with a global temporary table (Oracle)
Completing the modification (Oracle)
Debugging the script (Oracle)

Setting up Siebel batch process sampling

For Siebel batch processes to be sampled by the Siebel tier collectors, you need to create a tab-delimited text file that contains the mapping of each Siebel server to its host machine and network address.

Each row in the file represents a physical machine. The first field in each row should represent the name of the Siebel server, the second field its corresponding host machine name, and the third its network address.

Sampling Siebel batch processes (SQL Server)

If you have installed Interpoint for a SQL Server database, perform the following procedures.

To create the text file

Log in to the database server where your Siebel tier collector is installed.
Create the following tab-delimited text file:
<precise_root>\products\sql-server\
instance name\etc\siebel_machines.txt

To obtain the list of Siebel servers

Log in to the SrvrMgr utility.
Execute the following command:
list servers
Each returned row represents a Siebel server.

To obtain the host machine name and network address

Copy the getAddress.vbs script from the Utilities\Siebel folder in the Precise download or on the DVD to the server.
Run the following command:
cscript //nologo getAddress.vbs ODBC data source Administrator user name Administrator password
where:
- ODBC data source is the name of the ODBC data source used by the Siebel server to connect to SQL Server. To determine its name, check the ConnectString value in the siebel.cfg configuration file.
- Administrator user name and Administrator password are the user name and password required to connect to the SQL Server instance.
Repeat these steps for each Siebel server.

The following example shows the content of the siebel_machines.txt file:

sieb1 APPSRV1 00096B26E66C sieb2 APPSRV2 00096B26E67C

For more information about Siebel, see the relevant section in the Precise Interpoint for Siebel Installation Guide.

Sampling Siebel batch processes (Oracle)

If you installed Interpoint for an Oracle database, perform the following procedures.

To create the text file

Log in to the database server where your Siebel Tier Collector is installed.
Create the following tab-delimited text file:
Windows
<precise_root>\products\oracle\SID\etc\siebel_machines.txt
UNIX
<precise_root>/products/oracle/SID/etc/siebel_machines.txt

To obtain the list of Siebel servers

Log in to the SrvrMgr utility.
Execute the following command:
list servers

The following is an example of the returned information:
SBLSRVR_NAME HOST_NAME AsDev1 POOL-Siebel1 AsDev2 POOL-Siebel2

Each returned row represents a Siebel server. The first column represents the name of the Siebel server, the second column the corresponding physical machine name (but not necessarily as it appears in Oracle).

To obtain the host machine names

Connect to the Siebel database.
Run the following command:
SELECT DISTINCT MACHINE FROM V$SESSION;

The following is an example of the returned information:
Machine PRECISE\POOL-Siebel1 PRECISE\POOL-Siebel2

Each returned row represents a physical machine name.

If the command does not return any machine names, use the machine names provided in the HOST_NAME column in the table of Siebel servers.

Following is an example for the content of the siebel_machines.txt file:
AsDev1 PRECISE\POOL-Siebel1 AsDev2 PRECISE\POOL-Siebel2