3 Configuring Siebel Enterprise Targets
This chapter provides information on the following topics:
Prerequisites for Adding a Siebel Enterprise or Target
Ensure the following prerequisites are met before adding a Siebel enterprise or a Siebel target:
-
The Management Agent should be installed in the Gateway target host, and it's status should be “up" and running.
-
The Management Agent user should have read access to the siebel files,
siebns.dat,
andsiebenv.sh.
-
In case the gateway install location will not be provided as an input during discovery, the Management Agent should have read access to
vpd.properties
file. -
The Management Agent user should have execute permission to the
srvrmgr
utility (to validate that the providedsrvrmgr
credentials are correct). -
For complex networks, wherein the Siebel host name is different when compared to the host name discovered in Enterprise Manager, the user has to add mapping entries in the
siebelserverconfig.xml
file. This file is located in<agentinstalldir>/siebelserverconfig
directory of the gateway host.
Adding a Siebel Enterprise
Siebel Enterprise enables administrators to logically organize distributed targets for efficient and effective management and monitoring.
To add a Siebel Enterprise to Cloud Control for monitoring, perform the following steps:
Figure 3-1 Add Siebel Enterprise Page

Discovery Process of the Siebel Enterprise in Enterprise Manager
This section explains how the Siebel Enterprise is discovered by Enterprise Manager. The steps below show the process followed for the discovery.
-
The user enters information on the Discovery screen.
-
OMS connects to the agent running on the gateway host which internally calls the perl file (
siebelDiscovery.pl
) located in empa discovery plug-in. -
The
siebelDiscovery.pl
file executes a Java command to populate the list of targets. -
The Java code parses the Siebel files and generates the target list.
-
The list of targets are sent to the OMS.
-
The OMS parses the list of targets and performs a set of validations.
-
The targets are created in the OMS repository.
-
These targets are sent to the Management Agent for monitoring.
Note:
The discovery will fail if there is a mismatch in the host name of the Siebel server and the host name discovered in Enterprise Manager (EM).
There is a possibility of a mismatch in complex Siebel network configurations such as virtual host or cluster Siebel servers/gateways, where the Siebel host mentioned in Siebel configuration does not match with the host monitored in EM. In such cases, the siebelserverconfig.xml
file provides mapping between these hosts.
The siebelserverconfig.xml
file should be used to add mapping host entries for discovery. The file can be found in <agent_inst>/sieblserverconfig
directory. The siebelserverconfig
directory is not available in a fresh plug-in deployment. It will be created after the first siebel target discovery. Thereby, Siebel servers with mismatched hosts will not be discovered in the first discovery attempt.
Updating the Siebel Enterprise
After you add or remove Siebel servers or server components from your Siebel Enterprise, you must update the Enterprise, and check the relations between the Siebel Enterprise and Enterprise Manager targets.
Perform the following steps to update the Enterprise:
Figure 3-2 Siebel Enterprise Home Page

Updating the Siebel Servers
To synchronize the topology for Siebel Servers, perform the following steps:
Figure 3-3 Siebel Server Home Page

Siebel Compliance Standards
To associate Siebel Compliance Standards, follow these steps:
-
From the Siebel Enterprise Home page, select Siebel Enterprise, then select Compliance, and select Standard Associations.
-
On the Standard Associations page, click Edit Association Settings.
-
On the Target Compliance Standard Association page, click Add.
-
On the Compliance Standards window, select the compliance standard to be associated, and click OK.
To check the rules associated, follow these steps:
- From the Siebel Enterprise Home page, select Siebel Enterprise, then select Compliance, and select Results.
- On the Compliance Results page, check the rules associated under the compliance standards.
Adding Non-Siebel Targets to an Existing Siebel Enterprise Target
To add Siebel targets to a Siebel Enterprise target, you can use the Update Now functionality available on the Siebel Enterprise home page.
To add a non-Siebel target to a Siebel Enterprise target:
- Go to Oracle Software Downloads:
https://www.oracle.com/downloads/
. - Download the appropriate third party plug-in, and create the respective target in Enterprise Manager.
- From the Targets menu of the Cloud Control console, select Siebel.
- In the Enterprises tab, click the name of the Siebel Enterprise target to which you want to add the non-Siebel target.
- Select the Extended Infrastructure Targets tab, then click Add.
- Search for and select the required non-Siebel target, then click Select.
Defining Manually Added Non-Siebel Targets as Critical Targets for a Service
After manually adding non-Siebel targets to an enterprise, if you want to make these targets available to the Root Cause Analysis functionality available in Enterprise Manager, you need to tag these targets as Key Components.
Perform the following steps to make your non-Siebel target a critical target for any Siebel application service:
Removing Servers or Components From an Existing Enterprise
After creating a Siebel Enterprise target, you can manually remove individual servers or components from the enterprise. However, this deletes the respective target information from the Enterprise Manager repository.
After this entry is deleted, Enterprise Manager does not monitor this target anymore. If you perform a manual resynchronization for this enterprise, Enterprise Manager includes the component in the new system topology.
The two possible paths for manually removing components from an existing enterprise are:
-
From the All Targets page, move your mouse over the server or component you want to delete, right-click, select Target Setup from the menu, then Remove Target.
-
From the Siebel home page, select the Enterprise tab, and then select the enterprise you want to remove. Select the radio button next to the enterprise name, then click the Remove button.
This option removes the Siebel server, targets, and all the enterprise components.
Patching Siebel Targets
This section describes how to patch Siebel targets in Cloud Control using patch plans. It consists of the following sections:
Note:
Only Siebel Server and Siebel Gateway Server targets are supported for patching in Cloud Control.
Prerequisites for Patching Siebel Targets
Ensure that you meet the following prerequisites:
-
The Siebel Server and the Siebel Gateway Server targets that you want to patch are discovered in Cloud Control.
-
You must have the 13.2.1.0 Enterprise Manager for Oracle Siebel plug-in deployed in your system.
For information on how to deploy a new plug-in or upgrade an existing plug-in, see Managing Plug-Ins in Oracle Enterprise Manager Cloud Control Administrator's Guide.
Procedure for Patching Siebel Targets
Follow these steps to patch your Siebel Server and Siebel Gateway Server targets:
- Create a patch plan and add the patches that you want to apply on your Siebel Server and Siebel Gateway Server targets.
- Analyze and deploy the patch plan that you created.
User Roles and Privileges
The recommended privileges for the Agent user on the Siebel hosts are:
-
Read permissions for the following files:
-
all the Siebel files
-
vpd.properties
-
siebenv.sh (in non windows env)
-
siebns.dat
-
-
Should be a part of the Siebel group
-
Execute permissions for the following:
-
The server manager command. For example:
/bin/sh -c “. $siebel_location/siebenv.sh; exec $siebel_location/bin/srvrmgr -g <gateway_name> -e <enterprise_name> -s <server_name> -u <user_id> –p <password>"
-
The
odbcsql
command from the server host. For example:/bin/sh -c “. $siebel_location/siebenv.sh; exec $siebel_location/bin/odbcsql /s <server_name> /u <user_id> /p <password>"
-
To understand the roles and privileges for an OEM user, see Oracle Enterprise Manager Cloud Control Security Guide.
The out-of-the-box Enterprise Manager roles to manage plug-ins are:
-
EM_PLUGIN_OMS_ADMIN: Enables you to manage the lifecycle of plug-ins on Management Server instances.
-
EM_PLUGIN_AGENT_ADMIN: Enables you to manage the lifecycle of plug-ins on Management Agents.
-
EM_PLUGIN_USER: Enables you to view the plug-in lifecycle console.