| Oracle® Fusion Middleware Reference Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1) Part Number E16816-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Reference Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1) Part Number E16816-03 |
|
|
PDF · Mobi · ePub |
This chapter provides information about moving Oracle BI Applications from one environment to another.
This chapter contains the following sections:
Section 5.2, "Moving Oracle BI Applications Using the Full-Movement Scenario"
Section 5.3, "Moving Oracle BI Applications Using the Incremental-Movement Scenario"
You can move Oracle BI Applications components from one environment to another using different movement scenarios. This chapter focuses on the following scenarios:
Full-movement scenario
In this scenario, the target Oracle BI Applications environment, such as a production environment, does not exist. First, the source environment (development or test ) is created, configured, customized, and tested. Then, the target environment is created by moving all the components along with their configurations from the source environment.
For example, suppose you deployed Oracle BI Applications along with Oracle Fusion Applications in a development or test environment. You could move the components and configurations of the deployment into production using the full-movement scenario.
For instructions on moving Oracle BI Applications using the full-movement scenario, see Section 5.2, "Moving Oracle BI Applications Using the Full-Movement Scenario".
Incremental-movement scenario
In this scenario, a target (production) environment exists but Oracle BI Applications has not been deployed.
For example, suppose you deployed Oracle Fusion Applications, including Oracle Transactional Business Intelligence (which requires an Oracle BI metadata repository and presentation catalog) in a production environment, but you did not deploy Oracle BI Applications. You can deploy Oracle BI Applications in an Oracle Fusion Applications production environment at a later time by using the incremental-movement scenario.
For instructions on deploying Oracle BI Applications into an existing environment, see Section 5.3, "Moving Oracle BI Applications Using the Incremental-Movement Scenario".
When performing a full movement of Oracle BI Applications, you create a target (production) environment by moving all the components and configurations of the source (development or test) environment using movement scripts.
If you are replicating an Oracle BI Applications environment that is part of an Oracle Fusion Applications deployment, you will use the Oracle Fusion Applications movement scripts to move the components and configurations of both Oracle Fusion Applications and Oracle BI Applications at the same time.
For instructions on moving an Oracle BI Applications environment along with an Oracle Fusion Applications environment, see the chapter "Moving Components for Oracle Fusion Applications Across Environments" in Oracle Fusion Applications Administrator's Guide.
After completing the Oracle Fusion Applications movement process, additional tasks are required to complete the Oracle BI Applications move. For instructions on completing the required tasks, see the following sections:
Section 5.2.1, "Preconditions for Moving an Oracle BI Applications Environment"
Section 5.2.3, "Moving Oracle BI Applications Configuration Manager Components"
The following preconditions must be met before moving an Oracle BI Applications environment.
Oracle BI Enterprise Edition is available in the target environment.
The RCU for Oracle BI Enterprise Edition was run, as described in the section "Loading the Oracle Business Intelligence Schemas in the Oracle RAC Database" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.
The RCU for Oracle BI Applications was run, as described in the section "Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
A database has been created in the target environment for the Informatica Repository, and this database platform is of the same type as that in the source environment.
Informatica PowerCenter Client and Services have been installed and set up in the target environment.
Note: Make sure you have installed and set up Informatica PowerCenter Client and Services in the target environment according to the instructions in the section "Install and Set Up Informatica PowerCenter" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications. The high-level set up requirements include the following:
Install and configure database connectivity software on the computers that host the Informatica Integration Services and Repository Service.Create the Informatica Repository Service and point it to the Informatica Repository database for the production environment.
Create the Informatica Integration Services.
On the computer that hosts the Integration Services, configure the database client connectivity to the data warehouse and the ODBC DSN to the BI Server.
Make sure the code page of the Repository Service in the target environment is the same as the code page of the Repository Service in the source environment
Copy the source files from the Oracle BI Applications installation directory to the Informatica directory on the Informatica PowerCenter Services computer.
Configure Integration Services for relaxed code page validation.
Set the Integration Services overrideMpltVarWithMapVar custom property.
Create the Informatica Repository user in the native security domain.
Configure Informatica relational connections.
Register the Integration Services in DAC.
This section contains instructions for moving the Informatica Repository from one environment to another.
If you are moving Oracle BI Applications in the context of an Oracle Fusion Applications movement, you must perform this additional procedure for moving the Informatica Repository after you perform the steps for moving Oracle Fusion Applications, as described in the chapter "Moving Components for Oracle Fusion Applications Across Environments" in Oracle Fusion Applications Administrator's Guide.
Use the Informatica Backup and Restore functionality to move the Informatica Repository if the Informatica domain in the source and target environments is different from one another. See Section 5.2.2.1 for instructions.
Use the Informatica Copy Repository functionality to move the Informatica Repository if the Informatica domain in the source and target environments is the same. See Section 5.2.2.2 for instructions.
When you back up a repository, the Repository Service saves the repository in a binary file (.rep), including the repository objects, connection information, and code page information. You can restore metadata from a repository binary backup file. When you restore a repository, you must have a database available for the repository. You can restore the repository in a database that has a compatible code page with the original database.
Before you back up a repository and restore a repository into a different domain, verify that users and groups with privileges for the source Repository Service exist in the target domain. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database. During synchronization, users and groups that do not exist in the target domain are deleted from the repository. You can use infacmd to export users and groups from the source domain and import them into the target domain.
To back up and restore the Informatica Repository:
Back up the source repository:
In the source environment, log into the Informatica Administration Console.
In the navigator, select the Repository Service for the Informatica Repository.
In the Actions list, select Back Up Contents.
Enter the user name and password. (The Security Domain field appears when the PowerCenter domain contains an LDAP security domain. If necessary, enter the Security Domain.)
Enter a file name and description for the repository backup file.
Choose to skip or back up workflow and session logs, deployment group history, and MX data. You might want to skip these operations to increase performance when you restore the repository.
Click OK. The results of the backup operation appear in the activity log
Restore the repository in the target environment:
In the target environment, log into the Informatica Administration Console.
In the navigator, select the Repository Service.
In the Actions list, select Restore Contents. The Restore Contents options appear.
Select the appropriate backup file to restore.
Select whether or not to restore the repository as new. When you restore a repository as new, the Repository Service restores the repository with a new repository ID and deletes the log event files.
Optionally, choose to skip workflow and session logs, deployment group history, and MX data. Skipping the data improves performance.
Click OK. The activity log indicates whether the restore operation succeeded or failed
You can use the Informatica Copy functionality to copy content into a repository when no content exists for the repository and you want to use the content from a different repository. Copying repository content provides a quick way to copy the metadata that you want to use as a basis for a new repository. To copy repository content, you must create the Repository Service for the target repository. When you create the Repository Service, set the creation mode to create the Repository Service without content. If a repository exists in the target database, the copy operation fails. You must back up the existing repository and delete it from the target database before copying the repository content.
To copy the Informatica Repository:
Log into the Informatica Administration Console. (Since the Informatica domain is the same for both source and target environments, there is just one Informatica Administration Console.)
In the navigator, select the Repository Service to which you want to add copied content.
You cannot copy content to a repository that already contains content.
In the Actions list, select Copy Contents From.
The page displays the options for the Copy Contents From operation.
Select the name of the Repository Service.
The source Repository Service and the Repository Service to which you want to add copied content (target) must be in the same domain and must be of the same service version.
Enter the user name and password. (The Security Domain field appears when the PowerCenter domain contains an LDAP security domain. If necessary, enter the Security Domain.)
To skip workflow and session logs, deployment group history, and MX data, select the check boxes in the advanced options. Skipping this data can increase performance
Click OK.
The activity log displays the results of the copy operation.
This section contains instructions for moving Oracle BI Applications Configuration Manager components from one environment to another.
If you are moving Oracle BI Applications in the context of an Oracle Fusion Applications movement, you must perform this additional procedure for moving Configuration Manager components after you perform the steps for moving Oracle Fusion Applications, as described in the chapter "Moving Components for Oracle Fusion Applications Across Environments" in Oracle Fusion Applications Administrator's Guide.
To move Oracle BI Applications Configuration Manager components:
Register the source system with the same data source number using Oracle BI Applications Configuration Manager, as described in the section "Registering Source Systems" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
Run the Domains ETL, as described in the section "Run Domains ETL" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
Migrate the setup data using Oracle BI Applications Configuration Manager export and import functionality, as described in the section "About Migrating Setup Data" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
Perform setup steps in Functional Setup Manager:
Configure the offerings and modules to deploy, and select Feature Choices, as described in the section "How to Enable Offerings and Select Feature Choices" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
Create an implementation project and select an offering and one or more modules, as described in the section "How to Create an Implementation Project and Select Offerings" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
The Oracle BI Applications incremental-movement scenario is meant for situations in which you have already deployed a source system, such as Oracle Fusion Applications, in a development, test, or production environment, and you want to later deploy Oracle BI Applications.
This section provides information about first deploying Oracle BI Applications in a pre-production environment, such as a development or test environment, and then moving this deployment to a production environment.
This section contains the following topics:
Section 5.3.1, "Deploying Oracle BI Applications Into an Existing Pre-Production Environment"
Section 5.3.2, "Moving Oracle BI Applications Into an Existing Production Environment"
This section provides information about deploying Oracle BI Applications into an existing pre-production source system environment, such as a development or test environment, for example, if you have an existing Oracle Fusion Applications development environment and you want to deploy Oracle BI Applications.
After you create, configure, customize, and test the Oracle BI Applications deployment in a pre-production environment, you can then move it into a production environment by following the instructions in Section 5.3.2, "Moving Oracle BI Applications Into an Existing Production Environment".
For Oracle Fusion Applications deployments, the Oracle Fusion Applications installation and provisioning process installs the Oracle BI Applications software components in the Business Intelligence Oracle Home but does no further setup. You can deploy Oracle BI Applications at any time. To do so, you must follow the instructions in the chapter "Setting Up Oracle Business Intelligence Applications" in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
After you complete setting up Oracle BI Applications, you then need to perform the functional configuration, using Oracle BI Applications Configuration Manager and Functional Setup Manager. For instructions, see "Functional Configuration for Oracle Business Intelligence Applications" in Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
After functional configuration is complete, your environment is then ready for loading data into the Oracle Business Analytics Warehouse. The Oracle BI Applications ETL process is accomplished using Oracle Business Intelligence Data Warehouse Administration Console (DAC) and Informatica PowerCenter. For more information about configuring, running, and monitoring ETL processes, see Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
In addition, after Oracle BI Applications reports and dashboards have been tested and the data validated, the Oracle BI Applications system administrator will need to inform the Fusion Applications administrator to enable the appropriate embedded reports and dashboard (ADR) regions in Fusion Applications. The ADR regions are enabled using Functional Setup Manager for Fusion Applications.
Moving Oracle BI Applications from a pre-production environment into an existing production source system environment, such as an Oracle Fusion Applications environment, involves two major processes:
Setting up the Oracle BI Applications binary components in the production environment.
For an Oracle Fusion Applications deployment, the move plan process that would have been carried out when Oracle Fusion Applications was moved from a pre-production environment into the production environment also would have moved the Oracle BI Applications binary component files. In this process, you set up and configure these binary components.
For instructions, see Section 5.3.2.1, "Setting Up the Oracle BI Applications Binary Components in Production".
Moving the metadata components of the pre-production Oracle BI Applications environment into production.
If you made changes to any of the metadata components, you need to migrate the customized metadata into the production environment.
In this process, you migrate the customized metadata for the following components:
Data warehouse schema
DAC Repository
Informatica Repository
Configuration Manger and Functional Setup Manager
Oracle BI Repository
Presentation Catalog
For instructions on migrating the metadata components, see Section 5.3.2.2, "Moving Oracle BI Applications Metadata Components Into Production".
Follow this procedure to set up the Oracle BI Applications binary components in a production environment when the binary components have been installed but not deployed.
Note: The process for setting up the Oracle BI Applications binary components differs based on the operating system platform. For Windows, the setup process is manual. For UNIX and Linux, the setup process is partially automated by the Warehouse Configuration Deployment Assistant (WCA).
Note: You must complete the steps in the order they are listed.
To set up the binary components in a production environment:
For all operating systems, complete the following procedures in Section 3.4, "Tasks for Setting Up Oracle BI Applications," in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications:
"Setup Step: Create Required Databases."
"Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications."
Note: When you run the RCU, deselect the Create/Upgrade Schema option. In this step you will run the Oracle BI Applications RCU in order to create Configuration Manger and Function Setup Manager tables. You will create the data warehouse schema using DAC in a later step.
"Setup Step: Install and Set Up Informatica PowerCenter."
"Setup Step: Create an ODBC DSN to the Oracle BI Server."
"Setup Step: Create a User for ETL."
"Setup Step: Grant User Access to Oracle BI Applications Components."
For UNIX and Linux platforms, perform the procedure in Section 3.4, "Setup Step: Configure Oracle BI Applications Components Using Warehouse Component Deployment Assistant (WCA)."
Note: The WCA is not supported on Windows.
For the Windows platform, complete the following procedures in Section 3.5, "Platform-Specific and Topology-Specific Setup Steps," in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications:
"Setup Step: Creating the Informatica Repository Service."
"Setup Step: Creating the Informatica Integration Service."
"Setup Step: Copying Source Files to the Informatica PowerCenter Services Machine."
"Setup Step: Setting PowerCenter Integration Services Relaxed Code Page Validation."
"Setup Step: Setting PowerCenter Integration Services Custom Properties."
"Setup Step: Creating the Repository Administrator User in the Native Security Domain."
"Setup Step: Extending the BI Domain."
"Setup Step: Configuring the Oracle BI Connection Pools."
"Setup Step: Configuring Physical Data Source Connections in DAC."
"Setup Step: Configuring Relational Connections in Informatica."
"Setup Step: Setting the SiebelUnicodeDB Property in Informatica Integration Services."
"Setup Step: Enabling User Currency Preference Settings."
"Setup Step: Registering Source Systems."
"Setup Step: Configure DAC Integration Settings."
For all operating systems, complete the following procedures in Section 3.4, "Tasks for Setting Up Oracle BI Applications," in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications:
"Setup Step: Start DAC Server."
"Setup Step: Validate the Oracle BI Applications Component Configuration."
"Setup Step: Accessing the Informatica Domain and Repository from Informatica Client Tools."
"Setup Step: Install Oracle BI Administration Tool."
"Setup Step: Configure Oracle HTTP Server."
"Setup Step: Configure SSO and Portlet Provider for Oracle BI Applications Configuration Manager and Functional Setup Manager."
"Setup Step: Enable Offerings for Deployment."
"Setup Step: Set Languages for Data Load."
"Setup Step: Editing Preferred Currency Display Names."
"Setup Step: Enable Document Currency."
"Setup Step: Install DAC Client."
Note: This step is optional. You do not have to install the DAC Client in the production environment.
This section provides instructions for moving metadata components into a production environment. Follow these procedures for any metadata component for which you made metadata changes.
If you did not change the metadata for a particular component, you do not need to perform the move procedure.
This section contains the following topics:
Section 5.3.2.2.2, "Creating the Data Warehouse Schema in a Production Environment"
Section 5.3.2.2.4, "Moving Configuration Manager and Functional Setup Manager Metadata"
Section 5.3.2.2.6, "Moving Oracle BI Presentation Catalog Metadata"
The DAC metadata is stored in a repository database and is used to configure the schema definition, index definition, ETL process names (task names), subject areas, and execution plans.
When you move the DAC metadata from one environment to another, the data in the source environment (for example, a development or test environment) is exported as serialized XML files and then imported into the target environment (for example, a production environment).
To export DAC metadata from the source environment:
Follow the instructions in the section "Exporting DAC Metadata" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
Note: The first time you migrate the DAC metadata into a production environment export only the Logical and System data categories (as indicated by check boxes in the Export dialog). For subsequent data migration moves, you should only export the Logical data category. If you export the System data category for subsequent migrations, you will overwrite the configurations.
To import DAC metadata into the target environment:
Follow the instructions in the section "Importing DAC Metadata" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
Note:
You can also use a command line to export and import DAC metadata. For instructions, see "DAC Repository Command Line Parameters" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
Note:
If you need to move a subset of DAC metadata from one environment to another, you can use the DAC patching feature, which enables you to export a subset of data as an XML file from one environment and then import the data into another environment.
For more information about the DAC patching feature, see "Working With DAC Metadata Patches" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
Data warehouse schema information for the following objects is stored in the DAC repository:
Tables
Table columns
Foreign key tables (part of the table columns definition)
Related tables (table to table relationship)
Indexes
Index columns
In a pre-production environment, typically, changes are made to the data warehouse schema in the database using database client utilities, such as SQL Developer or SQL*Plus. Schema changes made in the database should then be imported into the DAC repository. You can then use DAC functionality to create the schema in the production environment.
To use DAC to create the data warehouse schema in a production environment:
If you are using an Oracle database, follow the instructions in the section "Creating, Upgrading or Dropping an Entire Schema for Oracle Databases" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console. In the "Generate DW Table Scripts for Oracle" dialog, select the option Create New.
If you are using a non-Oracle database follow the instructions in the section "Managing Data Warehouse Schemas for Non-Oracle Databases" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console. In the "Data Warehouse Configuration Wizard" dialog, select the option Create\Upgrade Data Warehouse Tables.
For instructions on moving an Informatica Repository from one environment to another, see Section 5.2.2, "Moving the Informatica Repository".
For instructions on moving Configuration Manager and Functional Setup Manager metadata, see Section 5.2.3, "Moving Oracle BI Applications Configuration Manager Components".
This section provides instructions for applying Oracle BI repository customizations in a pre-production environment to an existing Oracle BI repository in a production environment as well as re-applying objects from the default repository that may have been trimmed.
This procedure uses the Oracle BI Administration Tool to perform a three-way merge of the following repositories:
The original, unmodified Oracle BI repository that you received with the current version of Oracle BI Applications. In the Administration Tool user interface, this repository is referred to as the "Original Master Repository."
The customized Oracle BI repository in your production environment. In the Administration Tool user interface, this repository is referred to as the "Current Repository."
The customized Oracle BI repository in your pre-production environment. In the Administration Tool user interface, this repository is referred to as the "Modified Repository."
To move the Oracle BI repository into a production environment:
Back up your current, production repository by copying the file from your runtime location to a safe location of your choosing.
Open the Oracle BI Administration Tool.
Equalize the three repositories to be merged.
For instructions, see the section "Equalizing Objects," in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
Open the production Oracle BI repository in offline mode.
From the File menu, select Merge.
In the Merge Repository Wizard, select Full Repository Merge as the Merge Type.
In the Original Master Repository field, browse for and select the original, unmodified Oracle BI repository that you received with the current version of Oracle BI Applications. Provide the password for this repository.
In the Modified Repository field, browse for and select the customized, pre-production Oracle BI repository. Provide the password for this repository.
Click Next.
The Define Merge Strategy dialog displays a list of conflicts.
For each conflict displayed, select Current. This will apply your customization in the customized, pre-production Oracle BI repository to the production Oracle BI repository.
For detailed information about merging repositories using the Oracle BI Administration Tool, see "Merging Repositories," in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
The process for moving the Oracle BI Presentation Catalog involves copying the customized objects in the source catalog and pasting them into the target catalog. For instructions, see the section titled "Copying and Pasting Objects" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
|
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
