 |
 |
 |
Deploying Siebel Application Server Solution Templates
The SiteScope Siebel Application Server Solution allows you to monitor the availability, usage statistics, and server performance statistics for Siebel Application servers installed on Windows platforms.
Usage Guidelines
This solution template will deploy a set of monitors that test the health, availability, and performance of Siebel Application Servers.
System Requirements
Before you can use the Siebel Solution, there are a number of configuration requirements involving the server environment. The following lists an overview of these requirements:
- The Siebel Server Manager client must be installed on the machine where SiteScope is running or accessible to the SiteScope machine. There are several options for how you can do this. See the documentation for the Siebel Server Manager Monitor for more information.
- You will need to know the install path for the Server Manager client to be able to setup Siebel Server Manager monitors in SiteScope. If the client is installed on the machine where SiteScope is running, this will be the path on that machine. If the client is installed on a remote machine, you need to know the fully qualified path to the client executable relative to that machine.
- You need to know the name of the Siebel application(s) that are available in your network. For example, callcenter, sales, and so forth.
- You need to install and configure an ODBC System DSN name that can be used for monitoring Siebel database tables.
- You need to know the user and password that SiteScope will use for logging into the Siebel server. This user must be granted Siebel Administrator responsibility on the Siebel server.
- You need to know a significant list of Siebel system component names and their corresponding aliases. See the section on the Settings in the Siebel Application Server Solution Form for a listing of component names and aliases.
See the sections on the Siebel Monitor and Database Query Monitor for more information on system and configuration requirements. These monitor types that are deployed as part of the Siebel Application Server Solution.
Deploying the Siebel Application Server Solution Template
You use the following steps to deploy the Siebel Application Server Solution Form.
To deploy the Siebel Application Server Solution Template:
- Create a new SiteScope monitor group into which you will deploy the Siebel Application Server Solution Template.
- Within the new monitor group, click the Solution Template link below the Monitor Detail Table. The Solution selection screen opens.
- Click the Siebel Application Server link in the table of solutions. The Solution Properties for Siebel Application Server form opens.
- Complete the properties needed for SiteScope to connect to the Siebel Application Server in the form as described in the following sections.
- Click the Show Applications button. SiteScope queries the Siebel Application Server and retrieves a list of modules that are available on the server. The module selection window opens with a reduced listing of modules.
- Select the modules and parameters that you want to monitor. See the section on Selecting Modules for Monitoring for more information on the module types.
- After selecting the desired modules, scroll down in the module selection window and click the Select Modules button. The selection window closes and the Solution Properties for Siebel Application Server form is displayed populated with a check list of the selected modules.
- If necessary, use the check boxes in the selected modules list to deselect any parameters that you do not want to monitor. Click the Submit button to continue. The Property and Syntax Check screen opens. See the section on Verifying Monitor Values for more information.
- Click the Create Solution button to initiate the deployment of the monitors.
A monitor creation screen is displayed.
As the monitors are created, the monitor type and name are displayed along with messages of any errors found. A "success" message is shown if the monitors are created successfully. The process does not run the monitor.
Note: Errors detected during the creation of monitors using a solution template are independent of the status returned when the individual monitors are run. This means that the monitors may be created successfully but that the configuration settings may be incorrect or that the system being monitored is unavailable.
- After the monitors have been created, you can select the Return link to return the group detail page to view the status of the monitors.
After deploying the monitors, you should review the Error and Warning status thresholds and adjust them according to the importance of the monitored element. You should also create alerts and associate them to the newly created monitors to provide notification when an error is detected.
Note: Solution Templates do not configure any automated alerts for the monitors created. You must create and associate one or more alert definitions to the monitors or monitor groups created by solution templates.
Settings in the Siebel Application Server Solution Form
The following describes the settings on the Siebel Application Server Solution Form:
- Server
-
Select the machine name for the server where Siebel Application Server is running.
Use the choose server
to view the server selection screen. Use the Server drop-down menu
to select the server where the Siebel Application Server is running.
- Enterprise
-
Enter the Siebel Enterprise server name.
- Gateway
-
Enter the name of the Siebel Gateway server machine.
- Server Logical Instance Name
-
Enter the Siebel server logical name.
- Username
-
Siebel Client UserName
- Password
-
Enter the password for the Siebel Client.
- Srvrmgr Script Path
-
Enter the local path to the Siebel server manager client.
For example: D:\sea703\client\bin
- Siebel Disk
-
Disk name where Siebel is installed
- Siebel Root Dir
-
Enter the path of the shared Siebel root directory. For example, the shared
root directory for a Siebel 7.5.2 server would be: sea752
- Siebel ODBC Name
-
Enter the local ODBC name that SiteScope should use
for accessing the Siebel database.
- DB Username
-
Enter the username SiteScope should use to access the Siebel database.
- DB Password
-
Enter the password for the username used to access the Siebel database.
- CG Callcenter Name
-
Enter the Siebel CallCenter component group name.
- CG Callcenter Alias
-
Enter the Siebel CallCenter component group alias.
- CG System Management Name
-
Enter the Siebel System Management component group name.
- CG System Management Alias
-
Enter the Siebel System Management component group alias.
- CP Callcenter Name
-
Enter the Siebel CallCenter component name.
- CP Callcenter Alias
-
Enter the Siebel CallCenter component alias.
- CP eService Name
-
Enter the Siebel eService component name.
- CP eService Alias
-
Enter the Siebel eService component alias.
- CP Srvr Request Broker Name
-
Enter the Siebel Server Request Broker component name
- CP Srvr Request Broker Alias
-
Enter the Siebel Server Request Broker component alias
- CP_Srvr_Request_Processor_Name
-
Enter the Siebel Server Request Processor component name
- CP Srvr Request Processor Alias
-
Enter the Siebel Server Request Processor component alias
- CP Server Manager Name
-
Enter the Siebel Server Manager component name
- CP Server Manager Alias
-
Enter the Siebel Server Manager component alias
- CP File System Manager Name
-
Enter the Siebel File System Manager component name
- CP File System Manager Alias
-
Enter the Siebel File System Manager component alias
- CP Client Administration Name
-
Enter the Siebel Client Administration component name
- CP Client Administration Alias
-
Enter the Siebel Client Administration component alias
You must enter valid connection parameters before clicking the Show Applications button. When the correct connection information is supplied, SiteScope uses this to query the server and populate a hierarchical list of the selectable modules that you may monitor. Selecting a module will cause a monitor to be deployed against it. The metrics for each monitor are automatically created according to the type of module that is being monitored.
Verifying Monitor Values
During the deployment of the Solution template, each monitor configuration is displayed in the Property and Syntax Check table. The solution type is displayed above the table. The first column shows the monitor's property name. The next column shows the value for that property. Values that contained variables are shaded with green. Values that are not affected by variables show no shading. The final column is for displaying errors that SiteScope has found while verifying the values. Errors are shaded in red. Errors should be corrected before proceeding to the next step, but SiteScope does not require it, however doing so may create monitors that do not function properly.
The following is an example section from the Property and Syntax Check page for a Siebel Application Server Solution Template.
Property and Syntax Check for Solution: Siebel Application Server
Errors were found with this Solution set. The errors should be corrected before creating these monitors otherwise invalid monitors may be created.
Monitor Type: CPUMonitor Monitor Name: CPU Utilization on \\\\servername
| Property | Value | Property or Syntax Errors |
|---|---|---|
| frequency | 600 | |
| machine | \\\\servername | |
| name | CPU Utilization on \\\\servername |
Monitor Type: SiebelLogMonitor Monitor Name: Siebel Application Server Log on \\\\servername
| Property | Value | Property or Syntax Errors |
|---|---|---|
| frequency | 600 | |
| eventType | ServerLog | |
| machine | \\\\servername | |
| logFileRegex | /seaenterprise.salessea.log/ | |
| severity | 0 | |
| name | Siebel Application Server Log on \\\\servername | |
| logPath | \\\\servername\sea752\siebsrvr\LOG |
Monitor Type: SiebelLogMonitor Monitor Name: Siebel SCCObjMgr_enu component Log on \\\\servername
| Property | Value | Property or Syntax Errors |
|---|---|---|
| frequency | 600 | |
| eventType | GenericLog | |
| machine | \\\\servername | |
| logFileRegex | /SCCObjMgr_enu.*\.log/ | |
| severity | 0 | |
| name | Siebel SCCObjMgr_enu component Log on \\\\servername | |
| logPath | \\\\servername\sea752\siebsrvr\LOG |
Monitor Type: SiebelCmdLineMonitor Monitor Name: Siebel: CallCenter component group on salessea
| Property | Value | Property or Syntax Errors |
|---|---|---|
| targetMachineName | \\servername | |
| gateway | seagws | |
| frequency | 600 | |
| path | D:\sitescope\client\bin | |
| enterprise | seaenterprise | |
| server | salessea | |
| username | sysadmin | |
| tasksAgeFilter | 60 | |
| Metric 1 | Server Stats/salessea/No. of tasks in error | |
| Metric 2 | Component Groups/Siebel Call Center/CG_RUN_STATE | |
| Metric id1 | 45 $SERVERNAME$|||salessea|||No. of tasks in error | |
| name | Siebel: CallCenter component group on salessea | |
| Metric id2 | 32 $CG$|||CallCenter|||CG_RUN_STATE |
Monitor Type: SiebelCmdLineMonitor Monitor Name: Siebel: System component group on salessea
| Property | Value | Property or Syntax Errors |
|---|---|---|
| targetMachineName | \\servername | |
| gateway | seagws | |
| frequency | 600 | |
| path | D:\sitescope\client\bin | |
| enterprise | seaenterprise | |
| server | salessea | |
| username | sysadmin | |
| tasksAgeFilter | 60 | |
| Metric 1 | Server Stats/salessea/No. of tasks in error | |
| Metric 2 | Component Groups/System Management/CG_RUN_STATE | |
| Metric id1 | 45 $SERVERNAME$|||salessea|||No. of tasks in error | |
| name | Siebel: System component group on salessea | |
| Metric id2 | 32 $CG$|||System|||CG_RUN_STATE |
Monitor Type: SiebelCmdLineMonitor Monitor Name: Siebel: SRBroker component on salessea
| Property | Value | Property or Syntax Errors |
|---|---|---|
| targetMachineName | \\servername | |
| gateway | seagws | |
| frequency | 600 | |
| path | D:\sitescope\client\bin | |
| enterprise | seaenterprise | |
| server | salessea | |
| username | sysadmin | |
| tasksAgeFilter | 60 | |
| Metric 1 | Component Objects/System Management/Server Request Broker/CP_DISP_RUN_STATE | |
| Metric 2 | Component Stats/System Management/Server Request Broker/Avg SQL Execute Time | |
| Metric 3 | Component Objects/System Management/Server Request Broker/No. of tasks in error | |
| Metric 4 | Component Stats/System Management/Server Request Broker/Tasks Exceeding Configured Cap | |
| Metric 5 | Component Objects/System Management/Server Request Broker/Max Memory Used | |
| Metric 6 | Component Objects/System Management/Server Request Broker/Max %CPU Time | |
| Metric 7 | Component Objects/System Management/Server Request Broker/No. of Running Instances | |
| Metric id1 | 51 $LISTCOMPONENT$|||SRBroker|||CP_DISP_RUN_STATE | |
| name | Siebel: SRBroker component on salessea | |
| Metric id2 | 50 $COMPONENT$|||SRBroker|||Avg SQL Execute Time | |
| Metric id3 | 55 $LISTCOMPONENT$|||SRBroker|||No. of tasks in error | |
| Metric id4 | 60 $COMPONENT$|||SRBroker|||Tasks Exceeding Configured Cap | |
| Metric id5 | 44 $LISTCOMPONENT$|||SRBroker|||Max Memory Used | |
| Metric id6 | 42 $LISTCOMPONENT$|||SRBroker|||Max %CPU Time | |
| Metric id7 | 53 $LISTCOMPONENT$|||SRBroker|||No. of Running Instances |
Monitor Type: SiebelCmdLineMonitor Monitor Name: Siebel: ClientAdmin component on salessea
| Property | Value | Property or Syntax Errors |
|---|---|---|
| targetMachineName | \\servername | |
| gateway | seagws | |
| frequency | 600 | |
| path | D:\sitescope\client\bin | |
| enterprise | seaenterprise | |
| server | salessea | |
| username | sysadmin | |
| tasksAgeFilter | 60 | |
| Metric 1 | Component Objects/System Management/Client Administration/CP_DISP_RUN_STATE | |
| Metric 2 | Component Stats/System Management/Client Administration/Avg SQL Execute Time | |
| Metric 3 | Component Objects/System Management/Client Administration/No. of tasks in error | |
| Metric 4 | Component Stats/System Management/Client Administration/Tasks Exceeding Configured Cap | |
| Metric 5 | Component Objects/System Management/Client Administration/Max Memory Used | |
| Metric 6 | Component Objects/System Management/Client Administration/Max %CPU Time | |
| Metric 7 | Component Objects/System Management/Client Administration/No. of Running Instances | |
| Metric id1 | 51 $LISTCOMPONENT$|||ClientAdmin|||CP_DISP_RUN_STATE | |
| name | Siebel: ClientAdmin component on salessea | |
| Metric id2 | 50 $COMPONENT$|||ClientAdmin|||Avg SQL Execute Time | |
| Metric id3 | 55 $LISTCOMPONENT$|||ClientAdmin|||No. of tasks in error | |
| Metric id4 | 60 $COMPONENT$|||ClientAdmin|||Tasks Exceeding Configured Cap | |
| Metric id5 | 44 $LISTCOMPONENT$|||ClientAdmin|||Max Memory Used | |
| Metric id6 | 42 $LISTCOMPONENT$|||ClientAdmin|||Max %CPU Time | |
| Metric id7 | 53 $LISTCOMPONENT$|||ClientAdmin|||No. of Running Instances |
Monitor Type: SiebelCmdLineMonitor Monitor Name: Siebel Application Server: Siebel process on \\servername
| Property | Value | Property or Syntax Errors |
|---|---|---|
| Metric id10 | 46 $PROCESS$|||siebsvc|||No. of Running Instances | |
| Metric id11 | 35 $PROCESS$|||siebsvc|||Max %CPU Time | |
| Metric id12 | 49 $PROCESS$|||siebmtsh|siebmtshmw|||Max Memory Used | |
| Metric 10 | Server Processes/Siebel Application Server Process (SIEBSVC)/No. of Running Instances | |
| Metric 11 | Server Processes/Siebel Application Server Process (SIEBSVC)/Max %CPU Time | |
| Metric 12 | Server Processes/Siebel Components (SIEBMTSH / SIEBMTSHMW)/Max Memory Used | |
| targetMachineName | \\servername | |
| gateway | seagws | |
| frequency | 600 | |
| path | D:\sitescope\client\bin | |
| enterprise | seaenterprise | |
| server | salessea | |
| username | sysadmin | |
| tasksAgeFilter | 60 | |
| Metric 1 | Server Processes/Siebel Background Tasks (SIEBPROC / SIEBSH)/Max Memory Used | |
| Metric 2 | Server Processes/Siebel Application Server Process (SIEBSVC)/Max Memory Used | |
| Metric 3 | Server Processes/Siebel SrvrMgr Session (SIEBSESS)/Max %CPU Time | |
| Metric 4 | Server Processes/Siebel Components (SIEBMTSH / SIEBMTSHMW)/No. of Running Instances | |
| Metric 5 | Server Processes/Siebel Background Tasks (SIEBPROC / SIEBSH)/No. of Running Instances | |
| Metric 6 | Server Processes/Siebel SrvrMgr Session (SIEBSESS)/No. of Running Instances | |
| Metric 7 | Server Processes/Siebel Components (SIEBMTSH / SIEBMTSHMW)/Max %CPU Time | |
| Metric 8 | Server Processes/Siebel Background Tasks (SIEBPROC / SIEBSH)/Max %CPU Time | |
| Metric 9 | Server Processes/Siebel SrvrMgr Session (SIEBSESS)/Max Memory Used | |
| Metric id1 | 45 $PROCESS$|||siebproc|siebsh|||Max Memory Used | |
| name | Siebel Application Server: Siebel process on \\servername | |
| Metric id2 | 37 $PROCESS$|||siebsvc|||Max Memory Used | |
| Metric id3 | 36 $PROCESS$|||siebsess|||Max %CPU Time | |
| Metric id4 | 58 $PROCESS$|||siebmtsh|siebmtshmw|||No. of Running Instances | |
| Metric id5 | 54 $PROCESS$|||siebproc|siebsh|||No. of Running Instances | |
| Metric id6 | 47 $PROCESS$|||siebsess|||No. of Running Instances | |
| Metric id7 | 47 $PROCESS$|||siebmtsh|siebmtshmw|||Max %CPU Time | |
| Metric id8 | 43 $PROCESS$|||siebproc|siebsh|||Max %CPU Time | |
| Metric id9 | 38 $PROCESS$|||siebsess|||Max Memory Used |
Monitor Type: DatabaseMonitor Monitor Name: Siebel Transaction Logging process (is enabled?)
| Property | Value | Property or Syntax Errors |
|---|---|---|
| driver | sun.jdbc.odbc.JdbcOdbcDriver | |
| connectTimeout | 60 | |
| database | jdbc:odbc:sun.jdbc.odbc.JdbcOdbcDriver | |
| user | seadbuser | |
| targetMachineName | \\servername | |
| frequency | 600 | |
| content | /TRUE/ | |
| query | SELECT VAL FROM siebel.S_SYS_PREF WHERE (SYS_PREF_CD LIKE 'Docking:Transaction Logging') | |
| name | Siebel Transaction Logging process (is enabled?) | |
| queryTimeout | 60 |
Copyright © 2004 Mercury Interactive Corporation.
All rights reserved.
|
|
|