Release 9.2.0.3
Part Number B11000-02
 Contents |
 Index |
| Oracle9i Warehouse Builder Installation and Configuration Guide Release 9.2.0.3 Part Number B11000-02 |
|
This chapter provides instructions for installing Warehouse Builder client and server components. Unlike the high-level instructions in Section 1.1, "Quick Steps for Installing Oracle9i Warehouse Builder", this chapter contains a step-by-step procedure for the entire installation.
|
Note: If you are upgrading to Oracle9i Warehouse Builder Release 9.2.0.3, read Chapter 3, "Upgrading to Release 9.2.0.3 and Migrating Data" before following the installation instructions in this chapter. |
This chapter includes the following topics:
This section introduces high-level information about the Oracle9i Warehouse Builder components and installation.
The Warehouse Builder architecture consists of the components shown in Figure 2-1. This figure illustrates the following:
The Oracle Universal Installer for Warehouse Builder includes three options: OWB Design Time Install, OWB Server Side Install, and Custom Install. Typically, the OWB Design Time Install and the OWB Server Side Install are installed on separate machines. However, if you choose to install both components on the same machine, you must install them into separate ORACLE_HOMEs.
The OWB Design Time Install includes:
Repository Assistant: enables you to create the Design Repository (denoted by "B" in Figure 2-1)
Browser Assistant (optional): enables you to integrate the Design Browser with Oracle9iAS (denoted by "C2" in Figure 2-1). Refer to Section 2.8.1, "Why Integrate the Design and Runtime Audit Browsers with Oracle9iAS?" for information on the advantages of integration.
After you complete the client installation discussed in this section, you can launch the following Warehouse Builder components:
Enables you to configure the Warehouse Builder Design Browser to view your metadata, run web reports, and perform lineage and impact analysis on your metadata.
ORACLE_HOME/owb/bin/unix and execute browserasst.sh.
Provides the graphical interface used to define sources and design your targets and ETL processes.
ORACLE_HOME/owb/bin/unix and execute owbclient.sh.
Enables you to launch the Warehouse Builder Design Browser client, where you can to view your metadata, run web reports, and perform lineage and impact analysis on your metadata.
ORACLE_HOME/owb/bin/unix and execute openDB.sh.
Enables you to upgrade your metadata from a previous version of Warehouse Builder to Oracle9i Warehouse Builder.
ORACLE_HOME/owb/bin/unix and execute mdlconvertui.sh.
Enables you to launch the Oracle Metabase (OMB) Plus scripting utility.
ORACLE_HOME/owb/bin/unix and execute OMBPlus.sh.
Enables you to create a Warehouse Builder repository in your database to store the metadata definitions that describe your data warehouse.
ORACLE_HOME/owb/bin/unix and execute reposinst.sh.
Enables you to create the Runtime Repository and Target Schema to store and maintain the deployment and runtime audit/error information.
ORACLE_HOME/owb/bin/unix and execute runtimeinst.sh.
Enables you to launch the Warehouse Builder Runtime Audit Browser, where you can run reports on the audit and error information captured when you run jobs to load and refresh your ETL targets.
ORACLE_HOME/owb/bin/unix and execute openRAB.sh.
Enables you to start a local Runtime Platform Service, denoted by '4' in Figure 2-1, on your desktop. The Runtime Platform Service should be ideally installed on the server machine so that it is managed by the Database. In the rare situations that you do not have access to the server machine you can use this command to make it execute on your desktop machine.
ORACLE_HOME/owb/bin/unix and execute local_service_login.sh -startup ORACLE_HOME
Enables you to startup the server for the Design Browser client and the Runtime Audit Browser client.
ORACLE_HOME/owb/bin/unix and execute startOwbbInst.sh.
Enables you to stop a local Runtime Platform Service, denoted by '4' in Figure 2-1, that is executing on your desktop machine.
ORACLE_HOME/owb/bin/unix and execute local_service_login.sh -closedown ORACLE_HOME
Enables you to stop the server for the Design Browser client and the Runtime Audit Browser client.
ORACLE_HOME/owb/bin/unix and execute stopOWBBInst.sh.
The Server Side Install includes:
The Custom Install allows you to select the components you wish to install from those listed in the two preceding sections.
Before you begin, you need access to a user with SYSDBA privileges because Oracle9i Warehouse Builder Assistants require you to provide SYSDBA credentials when installing the Oracle9i Warehouse Builder Design Repository or Runtime Repository components.
For more information on setting your Oracle9i parameters for Oracle9i Warehouse Builder, refer to Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" and to Oracle9i Database Server documentation. If you have problems accessing a user with SYSDBA privileges, refer to Appendix D, "Diagnostics and Debugging".
In this step, you are installing the Warehouse Builder Design Client, denoted by "A" in Figure 2-1.
To install the Design Time components:
For Windows: The default base directory is C:\Program Files\Oracle\Inventory. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., C:\Program Files\Oracle\Inventory\Components.
For UNIX: Enter the location for the base directory, e.g., /private1. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., /private1/Components.
Click OK to continue.
Verify your group name by entering this command from the UNIX prompt from which the installer was launched: prompt> id
Click Next.
orainstRoot.sh file. (You may need to execute the shell script by typing "./" before orainstRoot.sh). The Root.sh installation screen shows the location of the orainstRoot.sh file. The script creates pointers to the components as the installer installs them in the system so that they can be identified later in the installation procedure. It produces the /var/opt/oracle/oraInst.loc file, which provides a pointer to the oraInventory directory.
Following execution of the Bourne shell script, continue with the installation process. OUI displays the File Locations page.
Source: If you are installing from the Warehouse Builder installation CD, accept the default. Otherwise, browse your system for the source of your installation files.
Destination Name: Type the name of the ORACLE_HOME where you are installing Warehouse Builder. You may use the default name provided or select another name.
Destination Path: Click Browse to locate the full path of your ORACLE_HOME for Warehouse Builder. Note that the ORACLE_HOME path must be a real, absolute path. It cannot contain environment variable names or spaces. You may use the default path provided or select another path. For more information, refer to Section 1.7, "Coexistence: ORACLE_HOME Considerations" and Section 1.8.3, "Setting Environment Variables (UNIX Only)".
Click Next.
You can also choose Custom if you want to separately install these Warehouse Builder components.
Click Next.
JRE.
Accept the defaults and click Next.
Click Install to perform a typical Warehouse Builder installation. To view a log of the installation information, refer to Section 1.9.1, "Inventory Directory".
After copying the required files, the installer prompts you to run the root.sh script. The root.sh script detects:
ORACLE_OWNER, ORACLE_HOME, and ORACLE_SID environment variables.
Refer to Section 1.8.3, "Setting Environment Variables (UNIX Only)" for more information on ORACLE_HOME.
root.sh script in the ORACLE_HOME directory by typing prompt> $ORACLE_HOME/root.sh.
In this step, you install the Warehouse Builder Design Repository, denoted by "B" in Figure 2-1. To log in to your Warehouse Builder client, you need to create a new Warehouse Builder repository within a schema in your database. The Warehouse Builder repository stores metadata definitions for all the objects created to populate your data warehouse. You use the Warehouse Builder Repository Assistant to create a new repository.
This installation automatically grants the Create Public Database Link privilege to the repository owner.
You can create the new repository in a new or existing schema. You can also use the assistant to drop an existing Warehouse Builder repository.
To install the Warehouse Builder Design Repository:
User Name: A user name with SYSDBA privileges. You must use the SYS account or any account with SYSDBA privileges in order to access or create the Warehouse Builder Repository schema. The Warehouse Builder Repository user requires access to certain v_$ tables and these grants are made by the SYSDBA account when you create the repository. The V$PWFILE_USERS view lists all the users who have SYSDBA privileges. For more information on setting Oracle9i parameters, refer to the Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" and Appendix D, "Diagnostics and Debugging".
Password: The password that corresponds to the SYSDBA user.
Host Name: The name of the system running the database that hosts or will host the Design Repository.
Port Number: The port number through which Oracle Warehouse Builder can access the database on the host system. Default:1521.
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection.
Click Next.
Click Next.
Click Next.
In this step, you are creating the schema for the Design Repository owner, as opposed to additional users, which you can create using the Oracle9i Warehouse Builder Security feature. For more information on creating additional users with this feature, refer to the Oracle9i Warehouse Builder User's Guide.
Click Next.
Click OK to continue.
Stop the installation and refer to Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" for more information on recommended parameters.
Perform the installation after having prepared your database.
Select the tablespace for data. The tablespace for data stores the tables, views, sequences, and PL/SQL packages that Warehouse Builder creates in order to store the client's metadata. If you plan to run lineage impact analysis reports on your design metadata, do not select a tablespace that is locally managed and whose Segment Management Clause is set to AUTO. Default: USERS. (Recommendation: >50MB.)
Select the tablespace for indexes. The default tablespace for indexes stores the indexes that Warehouse Builder creates on top of its relational structures to facilitate performance. Default: INDX. (Recommendation: >50MB.)
Select the tablespace for temporary data. The Temporary tablespace provides a workspace on the disc that stores temporary segments required to perform large sorts or temporary tables or indexes that are created during the processing of a structured query language (SQL) statement. Default: TEMP.
Select the default tablespace for snapshots. The default tablespace for snapshots stores metadata snapshots that you can create in order to perform metadata change management. Metadata snapshots capture information about select objects in your design repository at the time of snapshot creation, and vary in size according to the kinds of information they capture. (Recommendation: >5MB if you do not plan to use the snapshot feature; otherwise, > 60MB.) For more information on metadata snapshots, see the Oracle9i Warehouse Builder User's Guide.
Click Next.
For information on the international standard ID for each language, consult Table 2-1.
Choose MLS Base Language: The base language of your database.
Choose MLS Other Languages: Languages in which you want to edit and display the logical names and descriptions of objects created in Warehouse Builder. To select the MLS languages, choose a language from the Available Language Choices field. Click the arrows to move your choice to the Selected Languages field.You can choose multiple languages at the same time by holding down the Ctrl or Shift key while making your selection.
Click Next.
Table 2-1 lists the international standard IDs for each language.
To enable the Warehouse Builder Design Browser client, denoted by "C1" in Figure 2-1, add a Database Access Descriptor pointing to the Warehouse Builder Repository. This Database Access Descriptor should have the same name as the Repository. You can only perform this step after you have installed a repository using the Repository Assistant. If you have multiple repositories, you will need to create multiple Database Access Descriptors.
On the same host as the Warehouse Builder Repository, ensure that the Oracle HTTP server that was installed with the database is started:
ORACLE_HOME/Apache/Apache/bin, run apachectl start. (To stop, run apachectl stop.)
http://hostname:port/
For port, 7777 is the default on UNIX platforms; 80 is the default on Windows platforms, or as specified during installation. If you have multiple installations of Oracle HTTP Server on the same host, the port number is typically increased by one for each additional installation. Refer to the Oracle HTTP Server documentation for more information.
HOST:PORT:SID to point to Warehouse Builder Repository instance.
If your database instance does not support SID, use the full TNS connection string in this format: (HOST=your_host)(PORT=1521)(CONNECT_DATA=(SERVICE_NAME=your_oracle_service_name).
Install the OWB Server Side components on the machine where your Oracle Database Server is installed.
When you performed the OWB Design Time installation, you also installed the runtime components. Therefore, if you are performing the OWB Server Side install on the same machine as the OWB Design Time install, you are installing the runtime components twice. If you decide to go forward with this configuration, make sure to specify a separate ORACLE_HOME for each install.
The Server Side Install includes:
ORACLE_HOME\owb\rtp\sql directory. You can use these scripts to perform operations on the Runtime Platform Service. The templates show how jobs can be defined as OEM jobs, or invoked from SQL*Plus. These templates use the WB_RT_API_EXEC package to access the execution service that the Runtime Platform Service provides.
For Windows: The default base directory is C:\Program Files\Oracle\Inventory. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., C:\Program Files\Oracle\Inventory\Components.
For UNIX: Enter the location for the base directory, e.g., /private1. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., /private1/Components.
Click OK.
Enter a UNIX group name for those who have permission to configure the Oracle9i Warehouse Builder install. This is the same UNIX group name you created in Section 1.8.4, "Creating UNIX Accounts and Groups (UNIX Only)".
Verify your group name by entering this command from the UNIX prompt the installer was launched from: prompt> id.
Click Next.
orainstRoot.sh file. (You may need to execute the shell script by typing "./" before orainstRoot.sh). The Root.sh installation screen shows the location of the orainstRoot.sh file. The script creates pointers to the components as the installer installs them in the system so that they can be identified later in the installation procedure. It produces the /var/opt/oracle/oraInst.loc file, which provides a pointer to the oraInventory directory.
Following execution of the Bourne shell script, continue with the installation process.
Source: If you are installing from the Warehouse Builder installation CD, accept the default. Otherwise, browse your system for the source of your installation files.
Destination Name: Type the name of the ORACLE_HOME where you are installing Warehouse Builder. You may use the default name provided or select another name.
Destination Path: Click Browse to locate the full path of your ORACLE_HOME for Warehouse Builder. Note that the ORACLE_HOME path must be a real, absolute path. It cannot contain environment variable names or spaces. You may use the default path provided or select another path. For more information, refer to Section 1.7, "Coexistence: ORACLE_HOME Considerations" and Section 1.8.3, "Setting Environment Variables (UNIX Only)".
Click Next.
You can also choose Custom if you want to separately install these Warehouse Builder components.
Click Next.
JRE.
Accept the defaults and click Next.
Click Install to perform a typical Warehouse Builder installation.
To view a log of the installation information, refer to Section 1.9.1, "Inventory Directory".
After copying the required files, the installer prompts you to run the root.sh script. The root.sh script detects:
ORACLE_OWNER, ORACLE_HOME, and ORACLE_SID environment variables.
root.sh script in the ORACLE_HOME directory. Refer to Section 1.8.3, "Setting Environment Variables (UNIX Only)" for more information on ORACLE_HOME.
prompt> $ORACLE_HOME/root.sh
Once you see "Finished running generic part of the root.sh script" and "Now product-specific root actions will be performed", exit root user and return to the Install screen.
The Configuration Tools page automatically launches the Warehouse Builder Runtime Assistant. You can either complete the installation of the runtime objects, or cancel the wizard and choose to run the Runtime Assistant from your desktop later.
Before you can deploy your warehouse objects and execute your warehouse jobs in your target instance, you need to set up runtime objects. You must run the Warehouse Builder Runtime Assistant to create runtime objects for each of your target warehouse schemas. Run the Runtime Assistant immediately after performing the OWB Server Side Install, and on the same machine where you performed the OWB Server Side Install.
In this step, you first use the Runtime Assistant to install the Runtime Repository Schema (denoted by "2" in Figure 2-1) and the Runtime Access User (denoted by "1" in Figure 2-1). You then use the Runtime Assistant to install the Target Schema (denoted by "3" in Figure 2-1).
The Warehouse Builder Runtime Assistant installs the following components:
owbrt_sys: This user contains the Runtime software and Runtime Platform Service location on the database. If you are installing into a Real Application Cluster (RAC) environment, this user contains the Runtime Platform Service location for each instance in the cluster.
Note that the first time that you run the Runtime Assistant, you cannot do it remotely because it searches for Java code whose location is not yet registered in the Runtime Repository. In general, Oracle does not recommend that run the Runtime Assistant remotely.
In this step, you use the Runtime Assistant to install the Runtime Repository Schema (denoted by "2" in Figure 2-1) and the Runtime Access User (denoted by "1" in Figure 2-1).
The Runtime Repository Schema requires many (almost all) DBA privileges. To shield this user from abuse, you create a separate user (the Runtime Access User) that has no privileges, but that allows users to use the Runtime Repository. In the context of Warehouse Builder, the Runtime Access user can deploy and execute objects and ETL processes, but from SQL*Plus, the Runtime Access User cannot see objects that do not belong to it. The Runtime Access User is therefore a security measure. It receives the generated code from the Deployment manager and accesses services in the Runtime Repository Schema.
The Runtime Repository Schema owns the audit tables and audit/service packages that are accessed by the Target Schema. The Runtime Repository Schema is the central user within your system that manages connections to the various targets in the Target Schema. The Runtime Audit Browser client, which you install in Section 2.2, also communicates with the Runtime Repository Schema to enable runtime reporting.
The Warehouse Builder Runtime Assistant creates a new schema, or uses an existing one, within the target instance and initializes it with the Warehouse Builder runtime objects. Warehouse Builder runtime components use these objects for deployment of warehouse objects in your target instance, or to log audit and error information captured when you run jobs to load and refresh the target instance. The audit and error information can be viewed using the Warehouse Builder Runtime Audit Browser. For details, see the Oracle9i Warehouse Builder User's Guide.
If you are installing the Warehouse Builder runtime into a Real Application Cluster (RAC) environment, you must perform this installation on any node in the cluster where you want the Runtime Platform Service to execute. You can enable such a node for a Runtime Repository.
To install a Warehouse Builder Runtime Repository and Runtime Access User:
User Name: A user name with SYSDBA privileges. You must use the SYS account or any account with SYSDBA privileges in order to access or create the Warehouse Builder Repository schema. The Warehouse Builder Repository user requires access to certain v_$ tables and these grants are made by the SYSDBA account when you create the repository. The V$PWFILE_USERS view lists all the users who have SYSDBA privileges. For more information on setting Oracle9i parameters, refer to the Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" and Appendix D, "Diagnostics and Debugging".
Password: The password that corresponds to the SYSDBA user.
Host Name: The name of the system running the database that hosts or will host the Runtime Repository. If you are installing a Runtime Repository for the first time on a target instance, the Host Name must be the localhost from which you are running the Runtime Assistant.
Port Number: The port number through which Oracle Warehouse Builder can access the database on the host system. Default:1521.
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection. If you are installing in a Real Application Cluster (RAC) environment, you must install the software on each node of the cluster and Register the RAC instance in the Choose Option page.
When installing on a node in the Real Application Cluster, the host should be the node's host-value, and the Oracle Service Name should be its unique instance name. The Host, Port, and Service Name are recorded for each instance-node and can be managed using the Service Node Report in the Runtime Audit Browser. For example, this may be necessary if its instance-number or instance-name is changed after the installation.
Click Next.
If you are installing in a Real Application Cluster (RAC) environment, select Runtime Repository for the first node in the cluster. When you install on all subsequent nodes, select Register RAC Instance. This option shortcuts the creation of a Runtime Repository, but records that the node has the Runtime Platform software installed on it. Such a node becomes the candidate for supporting the Runtime Platform Service, and can be enabled for supporting a Runtime Repository using the Service Node report in the Runtime Audit Browser.
Click Next.
Click Next.
Otherwise, choose whether you want to create a new schema or install the repository into an existing user schema. Note that if the existing schema already contains Warehouse Builder runtime repository objects, the installation will fail. You must first drop the existing repository using the Runtime Assistant, and then proceed with the installation.
Click Next.
You use this information to login to your Warehouse Builder Runtime Repository. Note that you can install new runtime repository objects within an existing schema only if the schema contains no previous repository objects.
Based on the user name you specify, the Runtime Assistant will create the following four roles to control access to the Runtime Repository: WB_D_* with Developer privileges, WB_R_* with Runtime privileges, WB_A_* with Admin privileges, and WB_U_* with User privileges.
Click Next.
Select the tablespace for data: The tablespace for data stores the tables, views, sequences, and PL/SQL packages that Warehouse Builder creates in order to store your runtime deployment and audit data. Default: USERS.
Select the tablespace for indexes: The default tablespace for indexes stores the indexes that Warehouse Builder creates on top of its relational structures to facilitate performance. Default: INDX.
Select the tablespace for temporary data: The Temporary tablespace provides a workspace on the disc that stores temporary segments required to perform large sorts or temporary tables or indexes that are created during the processing of a structured query language (SQL) statement. Default: TEMP.
Click Next.
The Runtime Access User is denoted by "1" in Figure 2-1. Instead of connecting directly to the Runtime Repository user, you use a Runtime Access user as an intermediate connection. This schema accesses services in the Runtime Repository user. The Runtime Assistant creates one default user. You can create additional users later.
If this is not your first installation, choose between creating a new Runtime Access schema and installing into an existing one.
Click Next.
Click Next.
Click Next.
Click Yes and follow the instructions in the next procedure.
In this step, you use the Runtime Assistant to install the Target Schema. The Target Schema stores your warehouse objects and is where your warehouse jobs run; it is denoted by "3" in Figure 2-1. You can perform the target installation locally on the server, or remotely if you have run the Runtime Assistant before.
The Target Schema contains packages to execute the ETL processes that access the audit/service packages in the Runtime Repository Schema. The Target Schema is the actual target, and contains the target data and data objects, such as cubes, dimensions, views, and mappings. You can have multiple targets associated with one Runtime Repository. All the information pertaining to a target, such as execution and deployment information, is stored in the Runtime Repository.
When you install a Target Schema, the Runtime Assistant implicitly creates the Create Any Directory and Drop Any Directory privileges. This enables you to create or drop Connectors that are realized as directories in Warehouse Builder, without having to explicitly create those privileges yourself.
To create a Target Schema:
User Name: A user name with SYSDBA privileges. You must use the SYS account or any account with SYSDBA privileges in order to access or create the Warehouse Builder Repository schema. The Warehouse Builder Repository user requires access to certain v_$ tables and these grants are made by the SYSDBA account when you create the repository. The V$PWFILE_USERS view lists all the users who have SYSDBA privileges. For more information on setting Oracle9i parameters, refer to the Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" and Appendix D, "Diagnostics and Debugging".
Password: The password that corresponds to the SYSDBA user.
Host Name: The name of the system running the database that hosts or will host the Runtime Repository. If you are installing a Runtime Repository for the first time on a target instance, the Host Name must be the localhost from which you are running the Runtime Assistant.
Port Number: The port number through which Oracle Warehouse Builder can access the database on the host system. Default:1521.
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection.
Click Next.
Click Next.
Click Next.
If you created a runtime repository in the same installation session, its information appears as a default.
Click Next.
Otherwise, choose whether you want to create a new target schema or designate an existing user schema as the target schema.
Click Next.
Click Next.
Stop the installation and refer to Appendix A, "Preparing an Oracle 8.1.7 or 9i Database" to ensure that your database parameters are set properly.
Then run the installation again.
Select the tablespace for data: This tablespace stores the warehouse objects deployed to the Target Schema and the objects used to run warehouse jobs. Default: USERS.
Select the tablespace for indexes: The default tablespace for indexes stores the indexes that Warehouse Builder creates on top of its relational structures to facilitate performance. These indexes are for the warehouse objects deployed to the Target Schema and the objects used to run warehouse jobs. Default: INDX.
Select the tablespace for temporary data: The Temporary tablespace provides a workspace on the disc that stores temporary segments required to perform large sorts or temporary tables or indexes that are created during the processing of a structured query language (SQL) statement. This temporary data is for the warehouse objects deployed to the Target Schema and the objects used to run warehouse jobs. Default: TEMP.
Click Next.
If you ran this assistant from Oracle Universal Installer, then the End of Installation page displays when the installation is complete.
You can set up multiple Target Schemas. To do so, you must run this Runtime Assistant once for each Target Schema you want to create.
In this step, you configure your Web browser settings to enable the Design and Runtime Audit Browsers.
Prior to beginning this procedure, you must add "localhost" to your Netscape or Microsoft Internet Explorer proxy server bypass list.
To add "localhost" to your Internet Explorer proxy server bypass list:
You must set the cache management on your Web browser for any client you use to access the Design and Runtime Audit Browsers.
To configure the cache management in Internet Explorer:
Adding a Net Service Name enables you to use the Net Service Name option on the Runtime Audit Browser Login screen. You can add the Net Service Name in Net Manager, or you can add it manually by editing the tnsnames.ora file.
For Windows: Select Start, then Programs, OWB Group, then Configuration and Migration Tools, and Net Manager.
For UNIX: Start OWB_HOME/bin/netmgr.
To add a Net Service Name manually:
OWB_HOME/network/admin/tnsnames.ora and add a new entry. For example, add:
DWSUN42 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dwsun42)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = dev920.us.oracle.com) ) )
If you are using Netscape on a UNIX machine, perform this step to enable the Design Browser from Warehouse Builder client:
Set the permission for $ORACLE_HOME/owb/bin/unix/displayURL.sh to 555.
Because Warehouse Builder provides a client version of both the Design Browser and the Runtime Audit Browser, integrating these browsers with Oracle9i Application Server (Oracle9iAS) is optional. The integration includes two steps: running the Warehouse Builder Browser Assistant, and configuring the Browser. This option is illustrated at the bottom of the diagram in Figure 2-1.
The following are advantages of integrating the Design Browser and the Runtime Audit Browser with Oracle9iAS:
The Warehouse Builder Browser Assistant guides you through the installation of the Warehouse Builder Browser. You can use the Warehouse Builder Browser to view your metadata, run web reports, and perform lineage and impact analysis on your metadata. For more information on using the Warehouse Builder Browser, refer to the Oracle9i Warehouse Builder User's Guide.
When you install Warehouse Builder Browser, make sure you have a working Oracle 9iAS installation with Oracle Portal and, if you want to integrate the Runtime Audit Browser, with Oracle Container for J2EE (OC4J) as well.
If you want to drop existing Warehouse Builder Browser objects from your schema, refer to Chapter 4, "Deinstalling Warehouse Builder Components" in this guide.
To install the Warehouse Builder Browser:
If you are dropping existing Warehouse Builder Browser objects, select Uninstall the Warehouse Builder Browser and skip to Chapter 4, "Deinstalling Warehouse Builder Components" to follow the instructions.
Click Next.
Host Name: Name of the host machine where the Oracle9iAS database is installed. (For example, server8)
Port Number: TNS port number of the machine where the Oracle9iAS database is installed. (For example, 1521)
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection.
Click Next.
SYS User Name: Name of the SYS user.
SYS Password: Password for the SYS user.
Oracle Portal Schema Name: Oracle Portal user name set during the Oracle9iAS installation. This is the schema where you installed Oracle Portal. (Default: portal)
Click Next.
Default tablespace for browser data: Default tablespace that stores your browser data.
Temporary tablespace: Stores temporary segments required to perform large sorts on browser data.
Enter the Warehouse Builder Design Browser Schema Name and Password.
Click Next.
Click Next.
You can choose to skip it and enter it later, directly in the Warehouse Builder Browser Administration window. If you want to enter the Design Browser information now, click Yes and provide the following information that corresponds to "C1" in Figure 2-1. Otherwise, click No.
OWB Design Repository User: User name to log in to your Warehouse Builder Repository.
OWB Design Repository Password: Password to login to your Warehouse Builder Repository.
Host Name: Name of the computer where your Warehouse Builder Repository is located.
Port Number: Number of the TNS listener port of the database in which the Warehouse Builder Repository is located.
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection.
Click Next.
You can choose to skip it and enter it later, directly in the Warehouse Builder Browser Administration window.
If you want to enter the Runtime Audit Browser information now, click Yes and provide the following information that corresponds to "D1" in Figure 2-1. Otherwise, click No.
OWB Runtime Repository User: User name to log in to your Warehouse Builder Repository.
OWB Runtime Repository Password: Password to login to your Warehouse Builder Repository.
Host Name: Name of the computer where your Warehouse Builder Repository is located.
Port Number: Number of the TNS listener port of the database in which the Warehouse Builder Repository is located.
Oracle Service Name: A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection.
Click Next.
For information on configuring Warehouse Builder Browser, see "Configure the Warehouse Builder Runtime Audit Browser".
To use the Warehouse Builder Browser, follow these configuration steps:
For example, type: http://server:7778/pls/portal/
Where server is the Web server host name, 7778 is the Web server port number, and portal is the DAD name.
The Welcome to Oracle Portal page displays.
The Single Sign-On page displays.
Name: Name used by the Portal Provider. No spaces are allowed. For example, sso_username_owb_browser
Display Name: For example, Warehouse Builder Portal.
Timeout: Enter at least 100 seconds.
Timeout Message: For example, `The provider has timed out'.
Implementation Style: Database.
Owning Schema: Provide the Warehouse Builder schema name.
Package Name: wmp_provider
For all other fields, accept the default values.
Click OK to create the provider.
The Warehouse Builder Browser portlet displays in the show portlet mode. You can now view the Warehouse Builder Repository and assign roles to your SSO users.
The procedure to configure the Runtime Audit Browser in Oracle9iAS Portal consists of four general tasks, discussed in the following sections.
General steps to configure the Warehouse Builder Runtime Audit Browser:
Begin the configuration of the Warehouse Builder Runtime Audit Browser by creating the Oracle Container for Java (OC4J) instance.
To create the OC4J instance:
The default port number for EM is 1810.
The default EM administrator user is ias_admin.
The typical password is welcome1.
The first page displays two standalone instances. One was created when you installed IAS infrastructure; the other was created when you installed Application Server.
The page displays all the existing OC4J instances.
Click Create OC4J Instance.
owbb.
Click Create.
After the OC4J instance is created, you can see it under the System components of your Application Server Instance page. Note that the OC4J instance status is down. You will start it after you deploy your EAR file later in this procedure.
Click Default.
Click General.
../../../jlib/uix2.jar
../../../jlib/share.jar
After you create the OC4J instance, deploy the Runtime Audit Browser application. Deploy the Runtime Audit Browser application to a different port than the Oracle HTTP Server port.
To deploy the Runtime Audit Browser Application:Click Deploy EAR File.
$oracle_home/browserasst/ directory:
owbb.ear
In the Application Name field, enter the application name you want to give to your Warehouse Builder Browser; for example, My OWBB.
In the Parent Application field, leave the value default.
Click Next.
/owbb. This means your browser can be accessed by the URL: http://hostname:port/owbb/.
Note that Warehouse Builder reserves the use of owbb. If you have multiple OC4J instances of the Warehouse Builder Runtime Audit Browser, only one instance can be active an any given time.
Click Finish.
owbb.ear is deployed, return to the OC4J instance page and click on the application name you just deployed.
After you deploy the Runtime Audit Browser application, you must bind it to the schema.
To bind the application to the schema for Oracle9iAS Release 2 (9.0.2):Click Data Sources.
Note that the only values you can change are: Name, Description, Schema, Username, and Password.
Name: Enter a name; for example, owbb_demo.
Description: Enter a description; for example, My Oracle Warehouse Builder Browser demo.
Data Source Class: Enter com.evermind.sql.OrionCMTDataSource. You can also enter com.evermind.sql.DriverManagerDataSource, but this alternative does not work for Linux.
Schema: The schema into which you installed the Browser; for example, owbb_demo.
Username: The user name you created after running the Browser Assistant; it is usually the Schema name; for example, owbb_demo.
Password: Password for your Warehouse Builder Browser schema; for example, owbb_demo.
JDBC URL: Enter jdbc:oracle:thin:@host_name_of_the_database_into_which_you_put_your_owbb_schema:database_port_number:database_SID.
For example, jdbc:oracle:thin:@dwsun21.us.oracle.com:1521:iasdb.
For a JDBC URL pointing to an Oracle Service Name instead of an SID, use the following format:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=your_host)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=your_oracle_service_name)))
JDBC Driver: Enter oracle.jdbc.driver.OracleDriver
Location: Enter jdbc/owbb
Transctional(XA) Location: Enter jdbc/owbb
EJB Location: Enter jdbc/owbb
Click Create.
Click Yes.
Your OC4J instance restarts.
After your OC4J instance restarts, you make the Runtime Audit Browser accessible from Oracle9iAS Portal.
To make the Runtime Audit Browser visible through Portal:
Name: Enter any name, but do not use spaces; for example, owb_runtime_audit_viewer.
Display Name: Enter any name that you want displayed; for example, OWB Runtime Audit Browser.
Timeout: Set this value to a large number in seconds; for example, 10000 seconds.
Timeout Message: A typical timeout message is "RAB portlet provider has timed out".
Implementation Style: Accept the default (web).
Enter your Provider URL. The Provider URL is depends on the value you entered for the URL mapping in Step 4. For example, if in Step 4, your URL binding is /owbb, then your provider URL will be: http://hostname:port/owbb/providers/
Check the Web provider in same cookie domain as the portal option under the URL input box.
Select The user has the same identity in the Web providers application as in the Single Sign-On identity.
For User/Session Information, select User and set Login Frequency to Once per user Session.
Select Require portal user specific session information.
Click Next.
Click Finish.
If you have integrated the Runtime Audit Browser with Oracle9iAS, following these steps enables you to use the Net Service Name option on the Runtime Audit Browser Create Database Link page. You must add the Net Service Names first, and then start an Oracle9iAS OPMN process on the middle tier.
To add a Service Name in Net Manager:First, navigate to the infrastructure ORACLE_HOME and follow the remaining steps.
Then, navigate to the middle tier ORACLE_HOME and repeat the remaining steps.
For Windows: Select Start, then Programs, then iAS Group, then Configuration and Migration Tools, and then Net Manager.
For UNIX: Start ORACLE_HOME/bin/netmgr.
To add a Service Name manually:
ORACLE_HOME/network/admin/tnsnames.ora and add a new entry. For example,
DWSUN42 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dwsun42)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = dev920.us.oracle.com) ) )
If you have Oracle9iAS Release 2 (9.0.2), perform the following procedure to restart the OC4J instance on the middle tier host only.
To restart the OC4J instance on the middle tier host:$ORACLE_HOME/opmn/bin/opmnctl stopall.
$ORACLE_HOME/opmn/conf/opmn.xml to pass the default OC4J library path to the OWBB instance.
<ias-instance xmlns="http://www.oracle.com/ias-instance"> ...... <process-manager> ...... <oc4j maxRetry="3" instanceName="home" numProcs="1"> ...... </oc4j> ...... </oc4j> <oc4j instanceName="owbb" gid="owbb"> <config-file path="/usr/iasv2_portal/j2ee/owbb/config/server.xml"/> <oc4j-option value="-properties"/> <port ajp="3001-3100" rmi="3101-3200" jms="3201-3300"/> <environment><prop name="%LIB_PATH_ENV%" value="%LIB_PATH_VALUE%"/><prop name="LD_LIBRARY_PATH" value="/usr/iasv2_portal/lib"/></environment> </oc4j> <log-file path="/usr/iasv2_portal/opmn/logs/ipm.log" level="3"/> </process-manager> </ias-instance>
In this example, the highlighted text is added to opmn.xml. It is created by OC4J after a Warehouse Builder instance is created.
In this example, /usr/iasv2_portal is the middle tier ORACLE_HOME.
ORACLE_HOME/opmn/config/opmn.xml file:
<environment> <prop name="%LIB_PATH_ENV%" value="%LIB_PATH_VALUE%"/> <prop name="PATH" value="<path to oracle home>/bin"/> </environment>
$ORACLE_HOME/opmn/bin/opmnctl startall.
Oracle9i 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 Section 1.6, "Certified Software". If you are an Oracle9i Warehouse Builder Release 9.0.3 or 9.0.4 customer upgrading to Oracle9i Warehouse Builder Release 9.2.0.3, please refer to the Oracle9i Warehouse Builder Release Notes for Release 9.2.0.3.
To take advantage of name and address cleansing:
|
 Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
|