This section includes the following topics:
Ensure that the Database Tier is installed before installing this Tier. Most of the screens require you to input details regarding your information systems. Before performing an installation, compile a list of all required user inputs based on the procedures below.
This section describes the procedures that are needed to install a Siebel Tier instance. You have the option of adding a new instance, as well as adding a new application. For information on editing or removing an existing instance, see Editing or removing Tier instances or clusters on page 200.
On the AdminPoint Instances screen, you can add a new Tier instance.
Before adding a Tier instance, create a list of all required inputs based on the screen information below. |
To add a Tier instance
Click OK.
To install an instance in an application, you must have |
Click OK to view the next screen.
Always refresh AdminPoint after adding an instance. |
To define Siebel property settings
The preview screen signifies that the AdminPoint Tier installer has gathered enough information to begin the installation phase.
The preview screen displays the following details before installation begins:
At this screen, you can still change any of the settings displayed. Click Back to change any of the displayed settings. Click Next to continue installation. Click Cancel to stop the installation process.
This screen appears when the AdminPoint Tier installer is actually performing installation. Installation may take several minutes.
The progress screen visually displays the progress of actual installation on selected servers.
This screen appears when the AdminPoint Tier Installer has completed installation of all Tier instances.
If there are no action items, click Finish (it will be the only option available) to complete the instance installation. If there are action items, click Next (it will be the only option available).
After a Tier instance is installed, you can perform post-installation tasks as may be required. Only after completing any post-installation tasks required can you start using the Tier instances you have just installed.
Perform any tasks displayed on this screen.
Click Mark as done if you have performed the action items yourself. See Post-installation actions items on page 166 for more information.
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.
To perform Siebel Tier post-installation tasks
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.
If you have installed Interpoint for a SQL Server database, modifying the SRF consists of the following tasks:
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.
If you have installed Interpoint for an Oracle database, modifying the SRF consists of the following tasks:
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.
If you have installed Interpoint for a SQL Server database, perform the following procedures.
To create the text file
<precise_root>\products\sql-server\
instance name\etc\siebel_machines.txt
To obtain the list of Siebel servers
list servers
Each returned row represents a Siebel server.
To obtain the host machine name and network address
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.Following is an example for the content of the siebel_machines.txt
file:
sieb1 APPSRV1 00096B26E66C
sieb2 APPSRV2 00096B26E67C
For more information Siebel, see the relevant section in the Precise Interpoint for Siebel™ Installation Guide.
If you have installed Interpoint for an Oracle database, perform the following procedures.
To create the text file
<precise_root>\products\oracle\SID\etc\siebel_machines.txt
<precise_root>/products/oracle/SID/etc/siebel_machines.txt
To obtain the list of Siebel servers
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
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
For more information about using Siebel, see Precise Interpoint for Siebel.
| | | | | | | |