B
Installing Oracle Enterprise Manager and Oracle Workflow

Oracle Enterprise Manager (OEM) is a scheduling tool included in the Oracle9i database CD pack. You can configure Enterprise Manager with Warehouse Builder to manually schedule jobs that load or refresh data in your data warehouse. You can manage dependencies for jobs that reside in the Enterprise Manager Job Library using Oracle Workflow.

This appendix provides instructions for enabling Enterprise Manager and Workflow on your server and client systems.

This appendix includes the following topics:

• Configuring Oracle Enterprise Manager

• Installing Oracle Workflow

Note that this Configuration Guide outlines only the important installation steps. For detailed installation instructions, see the Oracle Enterprise Manager Installation Guide and the Workflow Server Installation Guide.

B.1 Configuring Oracle Enterprise Manager

Configure the Enterprise Manager client and server software, installed with Oracle9i, using the following guidelines:

B.1.1 Step 1: Create the Enterprise Manager Repository

To create the Enterprise Manager Repository:

1. From your Enterprise Manager Console host system, start the Enterprise Manager Configuration Assistant. This wizard helps you create the Enterprise Manager repository in the Warehouse Builder repository instance.

2. From the Configuration Operation page, select Create a New Repository.

3. On the Select Database for Repository page, provide the following information:

   User Name: system

   Password: manager <or appropriate system password>

   Service: oemrepos

4. On the Repository Login Information page, provide the following information:

   User Name: Schema where the Enterprise Manager Repository will be installed.

   Password: Password of the schema where the Enterprise Manager Repository will be installed.

5. From the Select Repository User Tablespace page, you can choose to create a new tablespace or accept the default. Click Next.

6. Click Finish to complete this process.

7. After the installation is complete, start the OMS:

   For Windows: Click Start, then Control Panel, and then Services.

   For UNIX: Access the $ORACLE_HOME/bin directory and type the command: oemctl start oms.

8. On the database where you installed the Warehouse Builder runtime, start the Oracle Agent service.

9. On the computer where you installed the Warehouse Builder Client, start the Enterprise Manager Console.

   To store generated scripts in the Job Library, Warehouse Builder must log on to the Oracle Management Server (OMS). This server manages the job library.

10. After configuring Enterprise Manager, you must establish a new Enterprise Management Server by clicking Add Management Server.

    If you are newly configuring the service, the Add Management Server dialog box appears. Type the host name of the Warehouse Builder repository server.

    On the Management Servers page, click OK.

    On the Oracle Enterprise Manager Login page, provide the following information:

    Administrator: sysman (initial Enterprise Manager Console login user name)

    Password: oem_temp (initial Enterprise Manager Console password)

    On the Security Warning screen, provide the following information:

    Password: sysman

    Confirm Password: sysman

11. Select Nodes from the navigation tree. Right-click and select Discover Nodes from the pop-up menu.

12. In the Discover Wizard Specify Nodes page, type the name of the computer on which the Warehouse Builder target warehouse resides and click Next to view the results.

    B.1.2 Step 2: Create a Windows User

    To create a Windows NT user with the permissions Enterprise Manager requires, run the NT User Manager on the Warehouse Builder runtime database instance host.

    Note: Skip this step if the node that hosts the Warehouse Builder runtime schema is a UNIX system. The UNIX ORACLE user should have enough permissions to perform any job requested through the job system.

    If the Windows user is accessed through OEM Agent 9.2, then the user must be added to the local Administrators group.

    To create a Windows user:
    1. From the Start menu, select Administrative Tools, and then User Manager.

    2. In the User Manager window, from the User menu, select New User.

    3. In the New User window, provide the following information:

       User Name: OEM

       Full Name: OEM Administrator

       Description: Run as batch job...

       Password: Enter a password.

       Confirm Password: Enter the password again.

       Select: Password never expires.

       Click OK. Windows inserts the new user name into the list of user names.

    4. For Windows NT, from the User Manager Console, select the new user name, then Policies, and then User Rights. The User Rights panel displays.

       For Windows 2000 and XP, from the Administrative Tools folder, launch the Local Security Settings applet.

    5. For Windows NT:

       In the User Rights Policy panel, check the Show Advanced User Rights box.

       Select the Logon as a Batch Job option from the drop-down list in the Right field.

       Click Add. Windows NT displays the Add Users and Groups panel.

       For Windows 2000 and XP:

       Navigate to Local Policies, then User Rights Assignment.

       Add the user to the Logon as a batch job right.

    6. Select the domain for the user from the List Names From drop-down list.

    7. Click Show Users and select the name of the new Enterprise Manager user you just created.

    8. Click Add and select OK to add rights.

    B.1.3 Step 3: Configure Preferred Credentials

    Enterprise Manager schedules jobs on the system that hosts the Warehouse Builder runtime schema. For Enterprise Manager to schedule jobs, you must configure two sets of user names and passwords:

    • A set for the host: OEM/Password

    • A set for the corresponding database: system/manager

    To initialize these credentials:

    1. Start the Enterprise Manager Console.

    2. From the System menu, select Preferences.

       Enterprise Manager displays the Edit Administrator Preferences window.

    3. Select the Preferred Credentials tab.

       Enterprise Manager displays a panel that lists Service Names and Types. Each resource node has three service types: Node, Database, and Listener.

    4. Select the Service Name that hosts the runtime schema (Service Type is Node).

       Enterprise Manager displays a User Name and Password panel.

    5. Provide a user name and password that provides access to the Enterprise Manager host.

       If you are running a Windows NT host system, then this is the user name you created for the Windows NT host in the previous section.

       If you are running a UNIX host system, then this is the UNIX ORACLE user you identified in Step 2.

    6. Select the Service Name of the runtime schema (Service Type is Database). This is the service name Enterprise Manager assigned to the database.

    7. Provide a user name and password that provides access to that database.

    8. Click OK to commit the information.

    Enterprise Manager is now configured to run Warehouse Builder. Before you register the load jobs (Tcl scripts) or schedule jobs with Enterprise Manager, you must start all necessary services on the machine that hosts Enterprise Manager and the system that hosts the target warehouse.

    On the host for Enterprise Manager, you must start:

    • Enterprise Manager Server

    • Oracle Agent

    On the host for your target warehouse, you must start:

    • Oracle Agent

    Continue the installation with the next section, Installing Oracle Workflow.

    B.1.4 Enterprise Manager Intelligent Agent Database Compatibility Matrix

    Table B-1 lists the Oracle Enterprise Manager Intelligent Agent compatibility matrix.

    Table B-1 Enterprise Manager Intelligent Agent Compatibility Matrix  

    Enterprise Manager Release	Supports Creation of Repository in Database Releases	Supported by Intelligent Agent Releases	Manages Database Releases
    9.2	9.2 9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x	9.2 9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x	9.2 9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x
    9.0.1	9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x	9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x	9.0.1.x 8.1.7.x 8.1.6.x 8.0.6.x

    The following notes apply to Table B-1:

    • An Intelligent Agent monitors and manages databases of the same release or earlier. For example, Intelligent Agent Release 8.1.7 monitors and manages database release 8.1.7 and earlier. If a newer release of the Intelligent Agent is used to manage an older release of the database, the Intelligent Agent must be installed in its own ORACLE_HOME, or in an ORACLE_HOME whose version is consistent with the Intelligent Agent's version.

    • In this table, Database Releases implies all editions of the database (Enterprise, Standard, Workgroup, and Personal Edition). The Personal Edition does not include support for Enterprise Manager jobs and events, or an Intelligent Agent.

    B.1.5 Configuring OEM for Oracle9i Internet Developer Suite Release 1

    You can run your ETL processes in the Runtime platform without using OEM, even if you are using Oracle Workflow. However, if you do plan to run PL/SQL ETL processes using OEM, Warehouse Builder provides a SQL script for Oracle Internet Developer Suite which configures it for using OEM jobs.

    The script is located at: </HOME>/owb/rtp/sql/set_oem_home.sql. After installing Warehouse Builder, connect directly to the Runtime Repository and run this script once as a configuration task. You can run it again subsequently if you need to reconfigure your system after installing a new OEM repository.

    The script has the following parameters:

    • P1: the Oracle Enterprise Manager Release to be configured, either 9.2 or 9.1.

    • P2: the operating system which contains the runtime server-side install, either NT or UNIX (use NT for any supported Windows system, UNIX for any supported UNIX system).

    • P3: the runtime server-side home directory.

    • P4: the database home directory containing the OEM jars. This directory must be on the same machine as the runtime server-side home so that it is valid as an Oracle directory; that is, it cannot be a mapped drive.

    For example, to configure the runtime at "D:\MyRuntimeHome" to use the Oracle Enterprise Manager Release 9.2 jars at "D:\My92DBHome" on a Windows system, type:

    @set_oem_home.sql 9.2 NT D:\MyRuntimeHome D:\My92DBHome
    
    

    For any given runtime repository, you can configure once for Oracle Enterprise Manager Release 9.0 and once for Release 9.2.

    B.2 Installing Oracle Workflow

    To ensure the integration of Oracle Workflow with Warehouse Builder, follow these installation steps:

    • Install the Oracle Workflow Server

    • Install the Workflow Client (Optional)

    B.2.1 Install the Oracle Workflow Server

    Carefully follow the Oracle Workflow Option Server Installation Notes for your operating system. These notes include the manual steps you need to follow to set up the Workflow Monitor. Ensure that the Workflow Monitor is operational before proceeding to the next steps.

    Note: To allow the Oracle Workflow server to invoke activities through the Warehouse Builder Runtime service, you must grant the EXECUTE ANY PROCEDURE system privilege to the Oracle Workflow repository user.

    B.2.2 Install the Workflow Client (Optional)

    The installation of Oracle Workflow Client is optional in Oracle9i Warehouse Builder because the functionality has been replaced by the Warehouse Builder Process Flow Editor. However, you can install Oracle Workflow Client if you want to be able to view the deployed Warehouse Builder processes in Oracle Workflow.

    On the computer where you installed Warehouse Builder client, install the Oracle Workflow Client from the CD for Oracle Workflow Client Release 2.6.2 for Microsoft Windows NT. Follow the installation steps in the Oracle Workflow Client Installation Guide.