2 Performing Installation and Upgrades

This chapter provides preliminary advisory information and procedures for the following topics:

Prerequisites for Setting Up Siebel in Enterprise Manager

Note the following system requirements before installing a Siebel Enterprise in Enterprise Manager:

  • The Siebel Plug-in is supported on the same platforms that support the Siebel software. Currently, the Siebel Plug-in is supported with Siebel 7.7, Siebel 7.8, and all later versions. To learn about the Siebel system requirements, refer to the Certifications tab in My Oracle Support (MOS).

  • The beacons for driving service test transactions against employee-facing (high interactivity) Siebel CRM applications must run on Microsoft Windows-based computers. These beacons rely on Microsoft Internet Explorer for driving transactions to Siebel.

  • You must use Microsoft Internet Explorer to connect to Enterprise Manager when recording or updating a service test. This is a requirement whether the test is for customer-facing (high interactivity) or employee-facing (standard interactivity) Siebel applications.

Setting Up Siebel in Enterprise Manager

Before you start monitoring Oracle Application Management Pack for Siebel in Enterprise Manger, you must perform the following tasks to install a Siebel enterprise:

  1. Install Enterprise Manager Cloud Control.

    The information required to perform these steps is available in the Enterprise Manager Cloud Control Installation Guide available at:


  2. Deploy the Siebel plug-in on OMS as follows:

    1. From the Cloud Control Setup menu, select Extensibility, then Plug-ins.

      The Plug-ins page appears.

    2. Select Oracle Siebel in the Plug-ins table.

    3. Click Deploy On, then select Management Servers.

  3. Install an Agent on each of the hosts.

    Install an Agent in each of the hosts where the Siebel Gateway Server, Siebel Web Server, Siebel Application Server, Siebel Report Server, Siebel Chart Server, Siebel Search Server, and the Siebel Database run. Also, you should install an Agent on each of the systems where you plan to deploy your Service Test Beacons if these systems differ from the Siebel server hosts.

    The information required to perform these steps is available in the Enterprise Manager Cloud Control Installation Guide.

    If you want to monitor additional software, such as LDAP and e-mail servers that you use with Siebel, and you have the proper license for monitoring these targets, install the Agent on these hosts as well.

  4. Deploy the Siebel plug-ins to each of the Management Agents installed in the previous step.

    Beacon plug-ins are to be deployed only on the Management Agents on which beacons are to be created to run service tests.

  5. Set the Preferred Credentials for all the hosts where the Management Agents are installed. This enables Enterprise Manager to execute commands on the computers hosting the Siebel Application Servers.

    To set the Preferred Credentials:

    1. From the Setup menu, select Security, and then select Preferred Credentials.

    2. On the Preferred Credentials page, select Siebel Server as the target type from the table, and click Manage Preferred Credentials.

    3. On the Host Preferred Credentials page, in the Default Preferred Credentials section, select the Credential Set from the table, and click Set.

  6. (optional) Enable automation.

    To create Enterprise manager beacons for Siebel High Interactivity applications, the Siebel components to be monitored must be configured to provide Automation support.

    Enabling Automation describes how to enable automation support.

  7. (optional) Enable SARM.

    To monitor user performance, you must manually enable Siebel Application Response Measurement (SARM). To enable SARM for specific components, access srvrmgr and execute the following commands:

    change param SARMLevel=2 for comp [component_name]
    change param SARMBufferSize=5000000 for comp [component_name]
    change param SARMFileSize=15000000 for comp [component_name]
    change param SARMPeriod=3 for comp [component_name]


    If you want to enable SARM for multiple components, you must execute this sequence of commands for each of the components.
  8. (optional) To monitor end-user performance using the Service Level Management feature, configure your environment for Siebel deployments on Microsoft Windows.

    To enable the beacon to monitor High Interactivity (HI) applications:

    1. From the Microsoft Windows Beacon system, click Start, then Control Panel.

    2. Double-click Administrative Tools, then double-click Services.

    3. Scroll down to the Enterprise Manager Agent service. Typically, this Agent is named Oracleagent12c1Agent.

    4. Double-click the service entry.

    5. On the Log On tab, select the Allow service to interact with desktop option.

    6. Click OK to save your changes.

    Also, you must configure an operating system user account on Enterprise Manager. Enterprise Manager uses this user account to grant sufficient permission to the Windows operating system user on the Beacon system. For Management Agents located on Windows-based computers, this user account needs one, special Windows permission that is not granted by default. To grant this permission:

    1. From the Microsoft Windows Beacon system, click Start, then Control Panel.

    2. Double-click Administrative Tools, then double-click Local Security Policy.

    3. Under Security Settings in the left pane, expand Local Policies, then double-click User Rights Assignment.

    4. Double-click the Log on as a batch job entry.

    5. Click the Add User or Group button, then enter the Windows operating system user name or a group containing this user.

    6. Click OK, then click Apply and OK on the next dialog box to save your changes.

  9. (optional) Enable timed statistics.

    If you want to monitor a variety of available Siebel performance metrics through Enterprise Manger, run the following srvrmgr command for each of the components:

    change param TimedStats=true for component [component_name]
  10. (optional) To monitor end-user performance using the Service Level Management feature, manually access all applications before recording a new transaction.

    Before recording a new transaction, you need to manually access all applications and manually satisfy all pop-up windows' requests. If you do not perform this task, the pop-up windows interfere and interrupt your recording session. This step must be done once on each system where a beacon is going to be deployed, and this is most applicable for HI applications.

    Additionally, while recording a new transaction, the URL must include SWECmd=AutoOn. This setting allows Enterprise Manager to interact with the Siebel test automation framework.

  11. (optional) Access HI applications from the beacon's computer.

    HI applications need to be accessed once from the beacon computer before discovering the Siebel HI Applications in Enterprise Manager.

Enabling Automation

The following sections describes how to enable options for Siebel versions 7.7, 7.8, and 8.0. This section contains the following:

Enabling Automation for Siebel Versions 7.7 and 7.8

To enable Automation support, access a server-side configuration file (for example, uagent.cfg for Call Center), search for the EnableAutomation variable, and change its value to TRUE.

  1. Access a server-side configuration file, such as uagent.cfg for Call Center.

  2. Search for the EnableAutomation variable and change its value to TRUE.

    If the variable definition does not exist, locate the [SWE] section in the configuration file and add the following line:

    EnableAutomation = TRUE
  3. Save the changed configuration file and restart the Siebel server.

Enabling Automation for Siebel Version 8.x

To enable Automation support, do the following:

  1. Execute the following srvrmgr command for all High Interactivity components you plan to monitor through Enterprise Manager beacons:

    change parameter EnableAutomation=True for server server_name comp comp_name
  2. After applying the command for all desired components, restart the Siebel server.