Skip Headers
Oracle® Warehouse Builder Installation and Administration Guide
11g Release 2 (11.2)

E17130-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

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

1 Overview of Installation and Configuration Architecture

This section discusses the architecture and components of Oracle Warehouse Builder and provides installation and configuration procedures.

This section includes the following topics:

Choosing an Appropriate Installation Configuration

Depending on the business needs of your organization, you may be implementing different types of Oracle Warehouse Builder installations:

  • The primary installation of Oracle Warehouse Builder, which includes the installation and configuration of the main design repository.

  • Optional installations on client computers where developers and administrators run Oracle Warehouse Builder client software, which do not contain a repository.

  • Optional installations on hosts that run the Control Center Agent service, but do not contain a repository.

  • Optional installations on database server hosts, where ETL jobs run and where the repository stores only run-time data.

Architecture and Components of Oracle Warehouse Builder

This section describes some common installation configurations, and shows how the various components interact. The primary Oracle Warehouse Builder components include:

  • Oracle Warehouse Builder Client, which includes the Design Center and the Control Center Manager

  • Oracle Warehouse Builder Browser

  • Oracle Warehouse Builder Repository

  • Workspaces

  • Control Center Service

  • Control Center Agent

  • Target Schemas

See Also:

Oracle Warehouse Builder Concepts for conceptual information about Oracle Warehouse Builder components.

Depending on your business needs, there are many possible installation configurations. The five most common topologies, that are illustrated in this section, are:

Note:

In any of these topologies, it is typical to have multiple design clients. For example, each Oracle Warehouse Builder developer or administrator usually has a corresponding, installed Oracle Warehouse Builder client, also called a design client.

Single Computer Topology

When everything is running on the same computer, the database home for Oracle Database 11g Release 2 contains all the components needed to run Oracle Warehouse Builder, as illustrated in Figure 1-1.

Figure 1-1 Single Computer Topology for Oracle Database 11g Release 2

Description of Figure 1-1 follows
Description of "Figure 1-1 Single Computer Topology for Oracle Database 11g Release 2"

Separate Client and Database Server Topology

If separate computers are being used to run the client and to host the repository, then all computers must have Oracle Warehouse Builder software installed, as illustrated in Figure 1-2. For the database server installation, Oracle Database 11g Release 2 includes the necessary components. For the client, you must install the Oracle Warehouse Builder software from the standalone installation image.

Figure 1-2 Two Computer Topology; Separate Client and Database Server Installations

Description of Figure 1-2 follows
Description of "Figure 1-2 Two Computer Topology; Separate Client and Database Server Installations"

See Also:

"Working with Oracle Warehouse Builder Standalone Installation Package" for Oracle Warehouse Builder client installation procedures.

Multiple Database Topology

If a database on a separate computer is being used to run mappings designed on another database, then all computers must have the Oracle Warehouse Builder software installed, as illustrated in Figure 1-3. For the database servers, the installation for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone installation image.

You must prepare Oracle Warehouse Builder repository on all database server computers. As illustrated in Figure 1-3, one acts as the design repository (Server1). The additional servers where mappings run, each have their own repository (shown as Server2), which in this case functions as a run-time repository. The Control Center Service on the execution database server deploys and runs the code.

Figure 1-3 Multiple Database Topology

Description of Figure 1-3 follows
Description of "Figure 1-3 Multiple Database Topology"

Separate Client, Control Center Service, and Database Server Topology

If Oracle Warehouse Builder client, the Control Center Service, and the repository run on different computers, then all these computers must have Oracle Warehouse Builder software installed, as illustrated in Figure 1-4. For the database server, the installation media for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone installation image. For the Control Center Service, you can use either type of installation. However, Oracle recommends that you use the standalone image because it installs only the components that Oracle Warehouse Builder requires.

Figure 1-4 Separate Client, Control Service Center, and Database Server Topology

Description of Figure 1-4 follows
Description of "Figure 1-4 Separate Client, Control Service Center, and Database Server Topology"

Control Center Agent Topology

If separate computers are used to run client, the Control Center Agent service (CCA), and the repository, then all computers used to deploy or run Oracle Warehouse Builder code must have installed Oracle Warehouse Builder software, as illustrated in Figure 1-5. For the database server, the installation for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone installation image. For the Control Center Agent service, you can use either install. However, because the standalone image only installs Oracle Warehouse Builder-required components, Oracle recommends this option.

In some deployments, a Control Center Service is required on a host that does not have an Oracle Database installed. For example, if you use code template-based ETL mappings where part of the mapping executes on a non-Oracle database, then you can run a Control Center Agent on that non-Oracle database host. In such a case, you can install Oracle Warehouse Builder software on the non-Oracle database host.

Also note that:

  • On the non-Oracle database host, the only component of Oracle Warehouse Builder software that is used is the Control Center Agent. The rest of the software is present but not used.

  • The CCA may be located with Oracle Warehouse Builder client or Server1, in which case no additional installation would be necessary.

  • In Figure 1-5, the Map1 has three execution units (a, b, c). The first two are Load Code Templates (LCTs) and the other one is an Oracle Target Code Template.

Figure 1-5 Control Center Agent Topology

Description of Figure 1-5 follows
Description of "Figure 1-5 Control Center Agent Topology"

About the Check for Updates Wizard for Oracle Warehouse Builder

Oracle Warehouse Builder provides the Check for Updates wizard within Design Center to simplify locating and downloading new resources for Oracle Warehouse Builder as follows:

  • Links to updated release notes, white papers, sample code, and other information resources.

  • New code templates, platform definitions and, drivers to extend Oracle Warehouse Builder for new sources and targets.

  • New experts, scripts, and other utilities that enhance Oracle Warehouse Builder or help address specific use cases.

Resources delivered through the Check for Updates wizard may consist of links to My Oracle Support, downloadable documents, or zip archives. Installation instructions are included for client-side and server-side components with each resource as needed.

See Also:

Note:

Oracle Warehouse Builder Repository Assistant can be started from OWB_HOME/owb/bin/unix/reposinst.sh on Linux or OWB_HOME\owb\bin\windows\reposinst.bat on Windows.