Having defined object definitions in previous lessons, you
are now ready to use the Deployment Manager in Warehouse Builder to implement
your business intelligence system.
The Deployment Manager is the unified interface to access
the runtime environment to create the object definitions. The Deployment Manager
always runs connected to a runtime platform/runtime repository. The Runtime
Repository Connections node on the console tree identifies the runtime repositories
that are available in the Deployment Manager (for example a runtime repository
connection for the development, one for the test, QA and production environment).
This lesson teaches you how to create a runtime repository
and use Warehouse Builder's Deployment Manager to implement your business intelligence
system.
This lesson will take approximately 60 minutes to complete.
Viewing Screenshots
Move your mouse over this icon to show
all screenshots. You can also move your mouse over each individual icon to see
only the screenshot associated with it.
Overview
This lesson will teach you how to create a runtime repository
and use Deployment Manager to implement your system. You will use the OWB Runtime
Assistant to create a runtime repository including a runtime owner, runtime
access user, and target schema. You will use the OWB Deployment Manager to deploy
the objects you defined in previous lessons.
In Lesson 1, you used the OWB Repository Assistant
to create a design client user. In this Lesson, you use the OWB Runtime Assistant
to create a runtime repository environment including a runtime owner, runtime
access user, and target schema.
The Runtime Assistant wizard's Welcome screen appears. Click Next.
2.
In the Server and SYSDBA Information page, enter the User Name
as sys, Password as <name of your sys password>, Hostname
as localhost, Port Number 1521, and Oracle Service
Name as obeowb or <your database service name>.
Click Next.
3.
In the Choose Option page, select Runtime Repository. Click
Next.
4.
In the Create or Drop page, select Create a new Warehouse Builder
Runtime Repository. Click Next.
5.
In the New or Existing User page, select Create and install
into a new user schema. Click Next.
6.
In the User Name and Password (New) page, enter the User Name
as runtime_owner, Password as runtime_owner, and Reenter
Password as runtime_owner. Click Next. A database configuration
warning may appear. Click OK.
7.
In the Tablespace page, accept the defaults and click Next.
The Runtime Access page explains that you should not connect
directly to the Runtime Repository Owner. Instead, you should create an
intermediary Runtime Access user. Select Create a new Runtime Access user.
Click Next.
2.
In the Runtime Access User (New) page, enter the User Name as
connect_user, Password as connect_user, and Reenter Password
as connect_user. Click Next.
3.
In the Name and Address Port page, accept the default value
and click Next.
4.
In the Summary page, click Finish. An Installation
Progress page appears. Installation may take several minutes.
5.
An Installation Successful page appears, asking whether you
want to install a target schema. Click Yes.
In the Choose Option page, select Target Schema. Click Next.
2.
In the Create or Drop page, select Create a new Warehouse Builder
Target Schema . Click Next.
3.
In the Runtime Repository page, accept the default runtime_owner
user name and password of the Runtime Repository Owner that you created
earlier. Click Next.
4.
In the New or Existing User page, select Create and install into
an new user schema. Click Next.
5.
In the User Name and Password (New) page, enter the User Name
target_schema and Password target_schema. Click Next.
A database configuration warning may appear. Click OK.
6.
In the Tablespace page, accept the defaults and click Next.
7.
In the Summary page, click Finish. Installation may take
several minutes. When the Installation Successful page appears,
click OK. The OWB Runtime Assistant automatically closes.
8.
Subsequent lesson activities make use of time dimension scripts
that ship as part of Oracle Warehouse Builder. In order to make sure that
all objects will be valid and can be deployed, you need to run 2 scripts.
Log in to SQL*Plus as target_schema, and run the following scripts
(in this specific order):
<OWB home>\owb\misc\time\owb_time_seq.sql
<OWB home>\owb\misc\time\owb_time.sql
These scripts will first try to drop objects that likely do not yet exist.
This will cause error messages, but you can ignore these.
Now that you have created a runtime
repository including a runtime owner, runtime access user, and target schema,
you will connect to the OWB Deployment Manager to deploy the objects you defined
in previous lessons. To invoke the OWB Deployment Manager, you must first create
a runtime repository connection.
1.
Expand the OWB10g_DEMO project,
and right-click the Runtime Repository Connections node.
Select Create Runtime Repository Connection.
The New Runtime Repository Connection Wizard: Welcome
page appears. Click Next.
2.
The New Runtime Repository Connection Wizard: Name page
appears. Enter the name obe_runtime_connection. Click Next.
3.
In the wizard's Details page, enter the Host Name as localhost,
leave the Port Number as 1521, enter the Service Name as obeowb,
Connect As User as connect_user, and Runtime Repository Owner as
runtime_owner. Click Next.
4.
Click Finish. This new connection appears
under the Runtime Repository Connections node.
Now that you have created a runtime
repository connection, there are two ways you can connect to the Deployment
Manager. You can either select from a menu or double-click the connection object.
In this example, you select from a menu.
1.
From the Project menu, select Deployment
Manager.
2.
The Select Runtime Repository Connection window appears.
In the Connection field, select OBE_RUNTIME_CONNECTION. Click OK.
3.
The Connection Information dialog appears.
Most of the fields have pre-filled values, based on those you provided
to the Runtime Assistant. The Connect As User is connect_user,
Host Name is localhost, Port Number is 1521, Service Name
is obeowb, and Runtime Repository Owner is runtime_owner.
Before you can deploy objects grouped
within a location, you must register the location's physical details.
1.
Maximize the Deployment Manager window.
The Deployment Manager groups objects by physical location. The locations
on the left hand tree are the locations you defined in the design tree.
Deployment Manager is the interface to register locations in the runtime
platform. What this means is that physical details for the location are
stored in the runtime repository. This approach has a few advantages:
Users do not need to remember the exact physical details of the deployment
location each time an object is deployed. The details are stored in
the runtime platform (passwords are stored encrypted).
Users can use the exact same design and deploy it to multiple runtime
platforms (e.g. development, test, QA, production) without making any
change. The Deployment Manager keeps track of the latest deployment
as well as the complete deployment history for each of the environments.
2.
Locations have to be registered as soon as they are used
in a deployment action (that is, the first time they are used; for subsequent
deployment actions the runtime platform already knows the details for
the deployment location). You can explicitly register a location by right-clicking
the location and selecting Register.
Right-click TARGET_LOC and select Register.
.
3.
A Location Registration dialog appears. For Schema Name, enter
the warehouse target you created using Runtime Assistant: target_schema.
For Password, enter target_schema. For Service Name, enter obeowb.
For Host name, enter localhost. Click OK.
The Deployment Manager supports the
creation of objects, the deployment of objects, and the execution of executable
objects such as mappings and process flows.
1.
Expand the location TARGET_LOC
and expand the module WH.
For every deployment, the Deployment Manager will show the Details on
the right hand side, providing a History tab to view the history of deployments
for a specific object.
You can see all objects that were defined in the console and you have
access to the editors and configuration properties for the objects from
the Deployment Manager window. Just use the right mouse button or double
click the object to access these.
2.
Click the module WH in the left hand tree. Look on the right hand
side. As you would expect, none of the objects have been deployed. Their
Design Status is New and their Deploy Action is None.
3.
Click the Default Action button at the bottom of Deployment Manager.
Notice that the Deploy Action for all objects has changed from None
to Create. Click the Reset button to change the Deploy Action
for all objects back to None.
Deployment Manager provides knowledge-based deployment in the sense that
if you use the Default Action button, Deployment Manager will determine
the most appropriate deployment action for you.
4.
In the left hand tree, with both the location TARGET_LOC and the
module WH still expanded, expand the Dimensions
node and select PRODUCT. With PRODUCT still selected, hold
down the Ctrl key and select the T_TIME and WAREHOUSE dimensions.
Click the Default Action button to change the Deploy Action for
these three objects from None to Create.
5.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the code for the three chosen
objects.
You are prompted to commit or cancel changes before deploying. Click
Commit.
6.
Before the actual code generation, Warehouse Builder again validates
the definitions to make sure the code can be generated. The Pre Deployment
Generation Results window pops up showing the objects that were selected
for deployment including the Validation and Generation result.
To create the objects, click Deploy at the bottom of the Pre
Deployment Generation Results window.
By selecting individual objects you can access the scripts, save scripts
to file and even save the entire deployment specification to file (which
enables deployment elsewhere by taking the code somewhere else and executing
the deployment specification.)
During deployment, Warehouse Builder displays a progress bar.
7.
After deployment, Warehouse Builder shows the Deployment Results for
each of the objects, including Deploy Status, number of Errors and number
of Warnings.
8.
Verify the deployment results and click OK
to close the window. The Deploy Status for each object is updated based
on the latest deployment result.
9.
Now that you deployed the three dimensions, you can deploy the cube containing
foreign key references to these dimensions. In the left hand tree, with
both the location TARGET_LOC and the module WH still expanded,
expand the Cubes node and select INVENTORIES.
Click the Default Action button to change the Deploy Action from
None to Create.
10.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the code for the cube.
11.
The Pre Deployment Generation Results window pops up showing the
cube that was selected for deployment including the Validation and Generation
result.
To create the cube, click Deploy at the bottom of the Pre Deployment
Generation Results window. After deployment, Warehouse Builder shows
the Deployment Results, including Deploy Status, number of Errors and
number of Warnings. Verify the deployment results and click OK
to close the window.
So far, you have practiced generating
and deploying dimensions and a cube to the target. Now you will switch
to a mapping, and execute the mapping to load data into a target dimension.
Before you can execute a mapping,
you must generate and deploy all of the objects used in the mapping. For the
MAP_CHANNEL mapping in this example, you will first generate and deploy
the connector, source external table, and target dimension used in the mapping.
You will then deploy and execute the mapping itself.
Before executing the MAP_CHANNEL mapping,
you must first deploy several objects referenced in the mapping. You will
first deploy the connector used by the mapping. In Deployment Manager,
expand the location TARGET_LOC, expand target module
WH and expand the Connectors node and select TARGET_LOC_SRC_FILES_LOC.
Click the Default Action button to change the Deploy Action for
this connector from None to Create.
2.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the connector.
If you are prompted to commit or cancel changes before
deploying, click Commit.
You are prompted to register the SRC_FILES_LOC location. Leave
the User Name and Password fields blank. For Host Name, enter localhost.
For Root Path, enter C:\OWB-OBE\sourcefiles\ or whatever path in
which you placed the sourcefiles subdirectory. Click OK.
3.
The Pre Deployment Generation Results window pops up showing the
connector that was selected for deployment, including the Validation and
Generation result.
To deploy the connector, click Deploy at the bottom of the Pre
Deployment Generation Results window.
During deployment, Warehouse Builder displays a progress bar.
4.
After deployment, Warehouse Builder shows the Deployment Results for
the connector, including Deploy Status, number of Errors and number of
Warnings.
5.
Verify the deployment results and click OK to close the window.
Generating
and Deploying the Source External Table
1.
Before executing the MAP_CHANNEL mapping,
you will deploy the mapping's source external table. In Deployment Manager,
expand the location TARGET_LOC and expand the module
WH. Expand the External Tables node and select CHANNELS_EXT.
Click the Default Action button to change the Deploy Action for
this external table from None to Create.
2.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the external table.
If you are prompted to commit or cancel changes before
deploying, click Commit.
3.
The Pre Deployment Generation Results window pops up showing the
external table that was selected for deployment, including the Validation
and Generation result.
To deploy the external table, click Deploy at the bottom of the
Pre Deployment Generation Results window.
During deployment, Warehouse Builder displays a progress bar.
4.
After deployment, Warehouse Builder shows the Deployment Results for
the external table, including Deploy Status, number of Errors and number
of Warnings.
5.
Verify the deployment results and click OK to close the window.
Before executing the MAP_CHANNEL mapping,
you will deploy the mapping's target dimension. In Deployment Manager,
expand the location TARGET_LOC and expand the module
WH. Expand the Dimensions node and select CHANNEL.
Click the Default Action button to change the Deploy Action for
this dimension from None to Create.
2.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the dimension.
If you are prompted to commit or cancel changes before
deploying, click Commit.
3.
The Pre Deployment Generation Results window pops up showing the
dimension that was selected for deployment, including the Validation and
Generation result.
To deploy the dimension, click Deploy at the bottom of the Pre
Deployment Generation Results window.
During deployment, Warehouse Builder displays a progress bar.
4.
After deployment, Warehouse Builder shows the Deployment Results for
the dimension, including Deploy Status, number of Errors and number of
Warnings.
5.
Verify the deployment results and click OK to close the window.
Now that you have deployed the mapping's source
external table, the target dimension, and the connector, you can deploy
the mapping itself. In Deployment Manager, expand the Mappings
node and select MAP_CHANNEL.
Click the Default Action button to change the Deploy Action for
this mapping from None to Create.
2.
Click the Generate/Deploy button on the toolbar (or from the File
menu, select Generate/Deploy), to generate the code for the mapping.
You are prompted to commit or cancel changes before
deploying. Click Commit.
3.
The Pre Deployment Generation Results window pops up showing the
mapping that was selected for deployment including the Validation and
Generation result. You can ignore the warning that "Column length
of CHANNEL_CLASS is longer than the target column length."
To deploy the code for the mapping, click Deploy at the bottom
of the Pre Deployment Generation Results window.
During deployment, Warehouse Builder displays a progress bar. After deployment,
Warehouse Builder shows the Deployment Results, including Deploy Status,
number of Errors and number of Warnings.
4.
After deployment, Warehouse Builder shows the Deployment Results, including
Deploy Status, number of Errors and number of Warnings.
Verify the deployment results and click OK to close the window.
5.
Click the Execute button on the toolbar (or from the File menu,
select Execute), to run this mapping that populates the CHANNELS dimension.
Deployment Manager presents an Execution Parameters dialog box to customize
the execution.
Accept all of the default values and click Execute. A progress
bar appears while the execution is in progress.
6.
When execution finishes, an Execution Results window appears. It shows
audit data about the number of records inserted, updated, deleted, and
merged. A message log is also shown.
All audit details are also stored in the runtime repository accessible
through the Runtime Audit Browser, which is covered in the next topic.
Now that you have deployed a dimension
and populated it by executing a mapping, you can monitor the results of object
deployments and mapping executions by using OWB Runtime Audit Browser. Before
invoking OWB Runtime Audit Browser, you must start an OC4J instance.
A browser window appears, and eventually presents a login window with
the local address:
http://127.0.0.1:8999/owbb/RABLogin.uix
If the browser does not take you automatically to the login window after
about one minute, then enter the above address manually.
5.
The browser window asks for run-time connection information. Enter the
following information:
Select Role: Warehouse Engineer
Runtime Repository: runtime_owner
Password: runtime_owner
Host Address: localhost
Host Port Number: 1521
Host Service Name: obeowb
Click View Deployment Report.
6.
The Runtime Audit Browser shows a Deployment Schedule report listing
all past deployments.
Expand each deployment instance, and you should see deployments of your
connector, your external table, your dimension, and your mapping.
7.
Near the upper left corner of the report window, note that the Deployment
Schedule tab is highlighted. Click the Object Summary tab. This
report lists all deployments sorted by object type.
Click the MAP_CHANNEL deployment.
8.
Near the upper right corner of the report window, note that the Deployment
tab is highlighted.
Click the Execution tab. Examine the details of the mapping’s execution.
How many records were merged?
9.
In the View Execution Report column at
the right, click the eyeglass icon to view the detailed execution report.
Scroll through the report. What was the elapsed time of the mapping execution?
10.
Spend a few minutes navigating through some
other reports. Then, click Log Out in the upper right corner, and close
the browser.
The Deployment Manager provides the unified interface to deploy
code to target platforms. The user-friendly interface provides knowledge-based
deployment as well as full of deployment actions per runtime platform. Managing
deployment and execution is made easy by using the Deployment Manager.
In this module you should have learned how to:
Create a runtime repository including runtime
owner, connect user, and target
Use Deployment Manager to instantiate your data warehouse
target
Use Runtime Audit Browser to check your execution results
Move your mouse over this icon to hide all screenshots
Bookmark
