|Oracle® Warehouse Builder Installation and Configuration Guide
10g Release 1 (10.1)
Part Number B12150-02
Oracle Enterprise Manager is a scheduling tool included in the Oracle 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:
Note that this manual outlines only the important installation steps. For detailed installation instructions, see the Oracle Enterprise Grid Control Installation and Basic Configuration and the Oracle Workflow Administration Guide.
To ensure the integration of Oracle Enterprise Manager with Warehouse Builder, follow these configuration steps:
To create the Enterprise Manager Repository:
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.
From the Configuration Operation page, select Create a New Repository.
On the Select Database for Repository page, provide the following information:
manager <or appropriate system password>
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.
From the Select Repository User Tablespace page, you can choose to create a new tablespace or accept the default. Click Next.
Click Finish to complete this process.
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.
On the database where you installed the Warehouse Builder runtime, start the Oracle Agent service.
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.
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:
sysman (initial Enterprise Manager Console login user name)
oem_temp (initial Enterprise Manager Console password)
On the Security Warning screen, provide the following information:
Select Nodes from the navigation tree. Right-click and select Discover Nodes from the pop-up menu.
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.
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 Oracle Enterprise Manager Agent 9.2, then the user must be added to the local Administrators group.
To create a Windows user:
From the Start menu, select Administrative Tools, and then User Manager.
In the User Manager window, from the User menu, select New User.
In the New User window, provide the following information:
Run as batch job...
Password: Enter a password.
Confirm Password: Enter the password again.
Password never expires.
Click OK. Windows inserts the new user name into the list of user names.
Configure the user rights.
For Windows NT:
From the User Manager Console, select the new user name, then Policies, and then User Rights. The User Rights panel displays.
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:
From the Administrative Tools folder, launch the Local Security Settings applet.
Navigate to Local Policies, then User Rights Assignment.
Add the user to the Logon as a batch job right.
Select the domain for the user from the List Names From drop-down list.
Click Show Users and select the name of the new Enterprise Manager user you just created.
Click Add and select OK to add rights.
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:
A set for the corresponding database:
To initialize these credentials:
Start the Enterprise Manager Console.
From the System menu, select Preferences.
Enterprise Manager displays the Edit Administrator Preferences window.
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.
Select the Service Name that hosts the runtime schema (Service Type is Node).
Enterprise Manager displays a User Name and Password panel.
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.
Select the Service Name of the runtime schema (Service Type is Database). This is the service name Enterprise Manager assigned to the database.
Provide a user name and password that provides access to that database.
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
On the host for your target warehouse, you must start:
Continue the installation with the next section, Installing Oracle Workflow.
Follow the instructions in this section only if both of the following are true:
You plan to run PL/SQL processes using Enterprise Manager.
Using Enterprise Manager for PL/SQL processes is optional.
You are using Oracle9i Enterprise Manager Release 1 (9.1).
If you are not using Enterprise Manager, or you are using a later release of Enterprise Manager, you can skip this step.
Warehouse Builder provides the
set_oem_home SQL script for Oracle Developer Suite. This script enables you to set configuration parameters for using Enterprise Manager jobs. You only need to run this script once, as a configuration task. You may need to run it again to reconfigure if required; for example, if you install a new Enterprise Manager repository.
To configure Enterprise Manager for the Oracle Developer Suite:
Connected to SQL*Plus as the Warehouse Builder Runtime Repository user.
The script requires the following parameters:
P1: The Enterprise Manager version you are configuring (
P2: The operating system that contains the Warehouse Builder runtime installation (
NT for any supported Windows system;
UNIX for any supported UNIX system).
P3: The Warehouse Builder runtime home directory.
P4: The Oracle Database Home directory containing the Enterprise Manager JAR files. This directory must be on the same machine as the Warehouse Builder runtime home directory in order to be valid as an Oracle directory. You cannot use a mapped drive to refer to the directory.
For example, if you are working on a Microsoft Windows system and your Warehouse Builder runtime environment is located at
D:\MyRuntimeHomeDir, and you are configuring it to use the Enterprise Manager 9.2 JAR files located at
D:\MyOracleDatabase92Home, call the script with the following parameters:
@set_oem_home.sql 9.2 NT D:\MyRuntimeHome D:\My92DBHome
For any Warehouse Builder Runtime Repository, you can run this script once to configure Enterprise Manager 9.1, and again to confirgure Enterprise Manager 9.2.
To ensure the integration of Oracle Workflow with Warehouse Builder, follow these installation steps:
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 enable the Oracle Workflow server to invoke activities through the Warehouse Builder Runtime service, you must grant the
EXECUTE ANY PROCEDUREsystem privilege to the Oracle Workflow repository user.
The installation of Oracle Workflow Client is optional in Oracle 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.3 for Microsoft Windows NT. Follow the installation steps in the Oracle Workflow Client Installation Guide.