Skip Headers
Oracle® Enterprise Manager Getting Started with Application Management Pack for Siebel
11g Release 1 (11.1)

E17014-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Performing Installation and Upgrades

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

System Requirements

Note the following system requirements before proceeding:

Installing Oracle Enterprise Manager 11g Grid Control

Install Enterprise Manager 11g Grid Control on at least one host in your network. Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if the Siebel pack middle tier is installed on host1.us.oracle.com, install and configure Grid Control on a different host; that is, Oracle Management Service and Oracle Management Repository on host2.us.oracle.com.

Install the matching version of the Oracle Grid Control Management Agent on every remote host where the Siebel Enterprise's Application Servers reside. For example, if your Grid Control is version 11.1, install the 11.1 Agents on all of the Siebel Application Servers and Siebel Gateway servers.

See Also:

Oracle Enterprise Manager Basic Installation and Configuration for Oracle Enterprise Manager Grid Control 11.1 (http://www.oracle.com/technology/documentation/oem.html)

Prerequisites for Installing a Siebel Enterprise in Enterprise Manager

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

  1. Install Enterprise Manager Grid Control.

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

    http://www.oracle.com/technology/documentation/oem.html

  2. 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 Grid 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.

  3. Enable the Siebel tab under the Targets tab.

    To enable the Siebel tab:

    1. Click Preferences located at the top-right corner of the user interface.

      The Preferences page appears.

    2. Click the Target Subtabs link located on the left pane.

      The Target Subtabs page appears.

    3. Select Siebel from Available Target Subtabs and move it to Selected Target Subtabs by clicking the Move arrow.

      Your selection is moved.

    4. Click Apply.

  4. Set the Preferred Credentials for all the hosts on which Oracle Enterprise Manager is installed. This enables Enterprise Manager to execute commands on the computers hosting the Siebel Application Servers.

    To set the Preferred Credentials:

    1. Click the Preferences link located in the Enterprise Manager top-right corner.

    2. Click Preferred Credentials in the left navigation pane.

    3. In the Host Target Type row, click the Set Credentials icon.

    4. In the Target Credentials table, enter a Normal Username and Normal Password for the Siebel Server Host.

    5. Click Test, then click Apply if the test succeeds.

    6. Return to the Preferred Credentials page.

    7. In the Agent Target Type row, click the Set Credentials icon.

    8. In the Target Credentials table, enter a Host Username and Host Password for the Siebel Server Host's Agent, then click Apply.

  5. For Release 3 (10.2.0.3) Grid Control Agent environments only, enable the Enterprise Manager Agent to monitor the Siebel target.

    To monitor a Siebel Server using a 10.2.0.3 Enterprise Manager Agent, you must execute a configuration script on the 10.2.0.3 Agent system.

    • For Windows systems, you must run the following command in the command line:

      <agent_dir>\bin\siebelClasspathFix.bat <agent_dir>

      (<agent_dir> should be replaced by the installation location of the Enterprise Manager Agent).

      Here is an example for an actual command:

      C:\OracleHomes\agent10g\bin\siebelClasspathFix.batC:\OracleHomes\agent10g

    • On Unix/Linux systems, you must execute the following command on the command line:

      <agent_dir>/bin/siebelClasspathFix.sh <agent_dir>

      (<agent_dir> should replaced by the installation location of the Enterprise Manager Agent).

      Here is an example for an actual command:

      /usr/local/OracleHomes/agent10g/bin/siebelClasspathFix.sh/usr/local/OracleHomes/agent10g

    Note:

    You must execute this command for all 10.2.0.3 Enterprise Manager Agents involved in monitoring Siebel server installations.
  6. 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.

    Section 2.4, "Enabling Automation" describes how to enable automation support.

  7. 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]
    

    Note:

    If you want to enable SARM for multiple components, you must execute this sequence of commands for each of the components.
  8. 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 Oracleagent10gAgent.

    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 Enterprise Manager 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. 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. 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. 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 describe how to enable options for Siebel versions 7.7, 7.8, and 8.0:

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.