| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
This chapter includes the following topics:
Warehouse Builder employs a design-deploy-execute model as an ETL solution. To integrate with Oracle E-Business Suite (EBS), Warehouse Builder users must import metadata from EBS before designing mappings to move and transform data. Specifically, during the design phase, Warehouse Builder users require access to metadata in the APPS schema. Later, in the execution phase, Warehouse Builder users must access the data in that schema.
Since direct access to the APPS production schema is most likely limited and restricted, you should define a user on the EBS database through which Warehouse Builder users can access only the relevant metadata and data.
To enable access to EBS data and metadata:
Create a user on the database hosting EBS. This user needs at least CONNECT and RESOURCE roles.
Grant access to the relevant metadata by running the script <oracle home>\owb\cmi\ebs\owbebs.sql.
This script grants access to the following tables in the APPS schema that contain metadata for EBS tables, views, sequences, and keys: FND_APPLICATION, FND_APPLICATION_VL, FND_TABLES,FND_VIEWS, FND_SEQUENCES, FND_COLUMNS, FND_PRIMARY_KEYS, FND_FOREIGN_KEYS,FND_PRIMARY_KEY_COLUMNS, FND_FOREIGN_KEY_COLUMNS.
The script also creates a synonym in the user schema for each of the preceding objects.
Enable a user to extract data from the EBS database.
You can create a new user or enable the same user you created in the previous steps. For each object that you want to enable data extraction, grant this user at least SELECT access to each object.
Warehouse Builder users can now import the E-Business Suite metadata as described in the importing section of the Oracle Warehouse Builder User's Guide.
The Repository Browser connects to Warehouse Builder repositories and enables you to view metadata, run Web reports, perform lineage and impact analysis on your metadata, and audit runtime executions.
When you install Warehouse Builder from the Oracle Universal Installer, the Repository Browser is also installed and available in the languages you selected in the for Product Languages in the Oracle Universal Installer.
To verify the installation, launch the Repository Browser listener and then the Repository Browser. For information on how to use the Repository Browser, refer to the Oracle Warehouse Builder User's Guide.
Making Additional Language Fonts Available
If end users need to view the Repository Browser in a language that you did not select when initially installing Warehouse Builder, you can copy the additional language fonts from the Warehouse Builder CD. From the fonts directory, copy the following fonts to the JDK directory under the OWB_ORACLE_HOME:
ALBANWTJ.TTF
ALBANWTK.TTF
ALBANWTS.TTF
ALBANWTT.TTF
ALBANYWT.TTF
Changing the Session Timeout
By default, Repository Browser sessions time out after 180 minutes, that is, 3 hours of inactivity.
To change this setting, update the session-config tag in web.xml located at <OWB_ORACLE_HOME>\owb\j2ee\owbb\WEB-INF\.
By default, the tag displays as follows:
<session-config><session-timeout>180</session-timeout></session-config>
Warehouse Builder gives you the option to perform name and address cleansing on your data with the Name and Address operator. The Name and Address operator identifies and corrects errors and inconsistencies in name and address source data. The operator identifies inconsistencies by comparing input data to data libraries supplied by the third-party name and address cleansing software vendors. Purchase the data libraries directly from these vendors.
To install data libraries, refer to the installation instructions of the name and address cleansing software vendor of your choice. For the list of certified name and address cleansing software providers, refer to Oracle Technology Network at http://otn.oracle.com/products/warehouse/htdocs/OTN_Partners.html.
If you are a Warehouse Builder customer upgrading to Warehouse Builder 10g Release 2 (10.2.0.2), please refer to the Oracle Warehouse Builder Release Notes for information on the packaging changes for data cleansing components.
To take advantage of name and address cleansing:
Purchase data libraries from one of the certified vendors listed on OracleMetaLink at http://metalink.oracle.com.
Install Warehouse Builder as instructed in this guide.
Install and access a certified vendor's data libraries and Name and Address adapter following the vendor's instructions.
If you are installing in a Real Application Cluster environment, you may be able to install the name and address adapter on many nodes to benefit from the parallelism and failover enabled by the RAC architecture. Check with your vendor to see if your purchase license allows a multiple-node installation.
You do not need to install the data libraries on multiple nodes. However, if you install all data libraries on one node, performance may suffer due to file access time latency. Follow the recommendations of your name and address cleansing software vendor.
Design a mapping using the Name and Address operator to cleanse name or address data. Refer to the Oracle Warehouse Builder User's Guide for information on designing mappings using the Name and Address operator.
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.
Note:
This chapter 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 GuideTo 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:
User Name: system
Password: manager <or appropriate system password>
Service: oemrepos
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:
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
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 systemIf 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:
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.
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: OEM/Password
A set for the corresponding database: system/manager
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 computer 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.
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.
AND
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.
Execute OWB_ORACLE_HOME/owb/rtp/sql/set_oem_home.sql.
The script requires the following parameters:
P1: The Enterprise Manager version you are configuring (9.1 or 9.2).
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 computer 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 configure Enterprise Manager 9.2.
If you plan to use Warehouse Builder process flows, install Oracle Workflow to enable deployment.
If your Oracle Database is version 10g or higher, you can also deploy Warehouse Builder schedules to Oracle Workflow. For more information, read about the schedules in the Oracle Warehouse Builder User's Guide.
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.
To enable 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.
Use Oracle Workflow 2.6.2 in conjunction with Oracle Database 9.2.
Use Oracle Workflow 2.6.3 in conjunction with Oracle Database 10gR1 or Oracle Workflow 2.6.4 in conjunction with Oracle Database versions starting with 10g Release 2 (10.2.0.2).
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 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.
Follow the installation steps in the Oracle Workflow Client Installation Guide.
|
 Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
