Deploying Siebel Gateway Server Solution Templates
The SiteScope Siebel Gateway Server Solution allows you to monitor
the availability and server statistics for
Siebel Gateway 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 Gateway Servers.
You can use this solution template to deploy monitors for server-wide resources and metrics
Deploying the Siebel Gateway Server Solution Template
You use the following steps to deploy the Siebel Application
Server Solution Form.
To deploy the Siebel Gateway Server Solution Template:
- Create a SiteScope monitor group into which you will deploy the
Siebel Gateway Server Solution Template. This should be the same group
or a subgroup associated
with the group where you deploy the other Siebel solution templates.
- Within the monitor group, click the Solution Template link below
the Monitor Detail Table to add a solution template to the group.
The Solution selection screen opens.
- Click the Siebel Gateway 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
Gateway 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 Gateway Server Solution Form
The following describes the settings on the Siebel Gateway Server Solution Form:
- Server
- Enter the name of the server where the Siebel Gateway Server is running. Do NOT enter
backslashes (\\) that indicate a UNC path as part of the name of the server.
- Siebel Disk
-
Enter the disk drive where the Siebel gateway server is running.
- Siebel Directory
-
Enter the path to the Siebel Directory. This directory should contain at
least an Admin Console installation.
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 Gateway Server Solution Template.
Property and Syntax Check for Solution:Siebel Gateway 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: DiskSpaceMonitor Monitor Name: Disk Space: C: on \\\\servername
| Property | Value | Property or Syntax Errors |
| disk | C: | |
| frequency | 600 | |
| machine | \\\\servername | |
| name | Disk Space: C: on \\\\servername | |
Monitor Type: DirectoryMonitor Monitor Name: Directory: \\\\servername\sea2000\gtwysrvr\LOG
| Property | Value | Property or Syntax Errors |
| frequency | 600 | |
| path | \\\\servername\sea2000\gtwysrvr\LOG | |
| name | Directory: \\\\servername\sea2000\gtwysrvr\LOG | |
| _path | | |
Monitor Type: ServiceMonitor Monitor Name: Service: Siebel Gateway Name Server Service on \\\\servername
| Property | Value | Property or Syntax Errors |
| frequency | 600 | |
| service | Siebel Gateway Name Server | |
| machine | \\\\servername | |
| name | Service: Siebel Gateway Name Server Service on \\\\servername | |
|