Oracle® Fusion Applications Customer Relationship Management Enterprise Deployment Guide 11g Release 1 (11.1.4) Part Number E16684-11 |
|
|
PDF · Mobi · ePub |
Configuration of Oracle Business Intelligence Applications is an extension of the existing Oracle Business Intelligence domain. This chapter describes how the different components of Oracle BI Applications can be installed and configured for high availability.
This chapter includes the following topics:
Section 18.2, "Preparing for an Oracle BI Applications Installation"
Section 18.4, "Configuring Oracle HTTP Server for the Managed Server"
Section 18.5, "Performing Additional Data Warehouse Administration Console Tasks"
Section 18.6, "Validating Oracle BI Applications Components URLs"
Oracle Fusion Customer Relationship Management is seamlessly integrated with Oracle Business Intelligence Suite to address the full range of analytical requirements. The suite consists of two products, Oracle Transactional Business Intelligence and Oracle Business Intelligence Applications (Oracle BI Applications).
Oracle Transactional Business Intelligence delivers up-to-the minute analysis of a wide range of Oracle Fusion Customer Relationship Management subject areas, whereas Oracle BI Applications provides a more comprehensive historical perspective for Oracle Fusion Customer Relationship Management that is suited to deeper analytical assessments. The product suite is meant to work together to provide customers with the ability to adapt to the rapidly changing and diverse analytical needs required by the business. For example, a customer could use the Transactional Business Intelligence CRM Sales analysis area to view up to the minute pipeline analysis near key forecasting time periods; the projected forecast could then be further validated leveraging the CRM analysis area in Oracle BI Applications to see how this compares vs. previous time periods, sales people, customers, industries, etc. enabling sales management to make adjustments that deliver a more accurate overall forecast.
Oracle Transactional Business Intelligence is an integrated product of Oracle Fusion Applications. Oracle BI Applications is an optional product that you may choose to deploy. The ETL tier of Oracle BI Applications consists of the following components:
a Data Warehouse database
Informatica ETL suite
Data Warehouse Administration Console (DAC)
The following sections provide more details about implementing these components of Oracle BI Applications for Oracle Fusion Applications.
Figure 18-1 shows the topology that represents Oracle BI Applications implementation in the Oracle Fusion Applications environment.
This section describes the following high-level tasks that are required to install Oracle BI Applications:
Create the Data Warehouse database.
Run the Repository Creation Utility (RCU) to create the Oracle BI Applications schemas for the Data Warehouse.
Install and configure Informatica PowerCenter.
For more information, see "Installing and Setting Up Informatica PowerCenter" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
Extend the Oracle Business Intelligence domain by deploying Oracle BI Applications Configuration Manager, Oracle Fusion Functional Setup Manager, and Oracle Business Intelligence Data Warehouse Administration Console (DAC).
Perform any necessary post-installation steps to complete the Oracle BI Applications setup.
Before you install Oracle BI Applications, the Data Warehouse Administration Console (DAC), and Informatica PowerCenter, create an Oracle RAC database on BIDWHOST1
and BIDWHOST2
to hold the following:
DAC Repository
Informatica Domain Configuration Database
Informatica Repository
Oracle Business Analytics Warehouse
For information, see the following:
"Pre-installation and Pre-deployment Requirements for Oracle BI Applications" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
You must run the Oracle BI Applications Repository Creation Utility (RCU) to create the following Oracle BI Applications schemas:
Oracle Data Warehouse Administration Console
Oracle Business Analytics Warehouse
Note:
Before running Oracle BI Applications RCU, you must copy the export dump files from the RCU_HOME
/rcu/integration/biapps/schema
directory to the BIDWHOST1
and BIDWHOST2
Oracle RAC database nodes. These dump files will be required when entering values in the Custom Variables screen (Figure 18-5). The directory should have read/write access since logs are written to it during the import.
For more information, see "Create the Oracle BI Applications Schemas Using RCU" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
To run the Oracle BI Applications RCU:
Unzip the ORACLE_BASE
/repository/installers/biapps_rcu/linux/rcuHomeBIApps.zip
file in the RCU home directory, and then start RCU from the bin directory in the RCU home directory:
cd RCU_HOME/bin
./rcu
In the Welcome screen (if displayed), click Next.
In the Create Repository screen, shown in Figure 18-2, select Create to load component schemas into a database. Click Next.
In the Database Connection Details screen, shown in Figure 18-3, enter connect information for your database:
Database Type: Select Oracle Database from the dropdown list
Host Name: Specify the name of the node on which the database resides. For the Oracle RAC database, specify the VIP name or one of the node names as the host name: BIDWHOST1-VIP
Port: Specify the listen port number for the database
Service Name: Specify the service name of the database (bidw.mycompany.com
).
Username: Specify the name of the user with DBA or SYSDBA privileges: SYS
.
Password: Enter the password for the SYS user.
Role: Select the database user's role from the dropdown list: SYSDBA
(required by the SYS user).
Click Next.
In the Select Components screen, shown in Figure 18-4, do the following:
Select Create a new Prefix, and enter a prefix to use for the database schemas, for example DEV
or PROD
. You can specify up to six characters as a prefix. Prefixes are used to create logical groupings of multiple repositories in a database. For more information, see Oracle Fusion Middleware Repository Creation Utility User's Guide.
Tip:
Note the name of the schema because the upcoming steps require this information.
First select Oracle Application Components and then select the following:
- Oracle BI Applications Schemas
- Oracle Data Warehouse Administration Console
- Oracle Business Analytics Warehouse
Click Next.
In the Schema Passwords screen, enter passwords for the main and additional (auxiliary) schema users, and click Next.
Tip:
Note the name of the schema because the upcoming steps require this information.
In the Custom Variables screen, shown in Figure 18-5, enter the required values.
In the Map Tablespaces screen, choose the tablespaces for the selected components, and click Next.
In the Summary screen, click Create.
In the Completion Summary screen, click Close.
Informatica is a third-party component that is required for Oracle BI Applications implementation. INFA_HOME
, which refers to the user-specified Informatica installation directory on the machine that hosts Informatica PowerCenter Services, must be on shared storage that is accessible from CRMHOST1
/ and CRMHOST2
/ where DAC Server will be configured.
Download the Informatica PowerCenter software. For information about how to do so, see "Installing and Setting Up Informatica PowerCenter" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications. During installation of Informatica PowerCenter, use the Oracle RAC database installed in Section 18.2.1, "Creating Databases for Oracle Business Intelligence Applications Components" when prompted.
This section includes the following topics:
How to Configure DAC, Oracle BI Applications Configuration Manager, and Functional Setup Manager
Configuring Data Warehouse Administration Console for High Availability
Note:
The DAC, Oracle BI Applications Configuration Manager, and Oracle Fusion Functional Setup Manager, configurations are an extension of the existing Oracle Business Intelligence domain. These procedures assume that Oracle Business Intelligence has been installed and configured during the Oracle Fusion Applications Provisioning process.
The DAC, Oracle BI Applications Configuration Manager, and Functional Setup Manager configuration is an extension of the existing Oracle Business Intelligence domain. In this extension, the Oracle BI Applications Configuration Manager, and Functional Setup Manager components are administration components and are targeted to the Administration Server. DAC will be targeted to the Oracle Business Intelligence Managed Server.
To extend the domain:
Run the WebLogic Scripting Tool (WLST) script, ORACLE_BASE
/products/fusionapps/bi/dwtools/scripts/install_dwtools.py
from CRMHOST1
/. A sample script is shown in Example 18-1.
Example 18-1 Running the WLST Script
ORACLE_BASE/products/fusionapps/bi/common/bin/wlst.sh install_dwtools.py 'DOMAIN_HOME' 'INFORMATICA_SERVER_HOME' 'INFORMATICA_DOMAIN_FILE' 'DW_DB_URL' 'DW_DB_SCHEMA' 'MDS_DB_URL' 'MDS_DB_SCHEMA' 'DAC_DB_URL' 'DAC_SCHEMA' 'DAC_TARGET'
where:
DOMAIN_HOME
is the path to the Administration Server Domain Home
INFORMATICA_SERVER_HOME
is the path to the Informatica Server Home
INFORMATICA DOMAIN FILE
is the path to the Informatica domains.infa
file location
DW_DB_URL
is the string; for example,
'jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST=(LOAD_BALANCE=on) (ADDRESS=(PROTOCOL=TCP) (HOST=BIDWHOST1)(PORT=1521))(ADDRESS= (PROTOCOL=TCP)(HOST=BIDWHOST2) (PORT=1521)))(CONNECT_DATA= (SERVICE_NAME=bidw.mycompany.com)))'
DW_DB_SCHEMA
is the Data Warehouse schema; for example, prefix
_DW
MDS_DB_URL
is the string; for example,
'jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST=(LOAD_BALANCE=on) (ADDRESS=(PROTOCOL=TCP) (HOST=FUSIONDBHOST1)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP) (HOST=FUSIONDBHOST2)(PORT=1521))) (CONNECT_DATA= (SERVICE_NAME=crm.mycompany.com)))'
MDS_DB_SCHEMA
is the MDS schema; for example, prefix
_MDS
DAC_DB_URL
is the string; for example,
'jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST=(LOAD_BALANCE=on) (ADDRESS=(PROTOCOL=TCP) (HOST=BIDWHOST1)(PORT=1521))(ADDRESS= (PROTOCOL=TCP)(HOST=BIDWHOST2) (PORT=1521)))(CONNECT_DATA= (SERVICE_NAME=bidw.mycompany.com)))'
DAC_SCHEMA
is the DAC schema; for example, prefix
_DAC
Note:
When prompted, enter the password for each of the following schemas:
prefix
_DW
prefix
_MDS
prefix
_DAC
DAC_TARGET
should be set to the Managed Server name (bi_server1
) for an enterprise installation or AdminServer
for a simple installation.
Note:
You must restart the Administration Server for this configuration to take effect.
Run the following Oracle WebLogic Scripting Tool (WLST) script from CRMHOST1
:
ORACLE_BASE/products/fusionapps/bi/dac/scripts/copyDACDomainFiles.py
For example:
ORACLE_BASE/products/fusionapps/bi/common/bin/wlst.sh copyDACDomainFiles.py 'ORACLE_HOME' 'DOMAIN_HOME'
where
ORACLE_HOME
is the path to Oracle home. For example, ORACLE_BASE
/products/fusionapps/bi
.
DOMAIN_HOME
is the path to the Managed Server domain home. For example, /u02/local/oracle/config/domains/
CRMHOST1
/BIDomain
.
Restart the Administrative Server and all Managed Servers.
Run the following WLST script on CRMHOST1
:
ORACLE_BASE/products/fusionapps/bi/dwtools/scripts/configure_dwtools.py
For example:
ORACLE_BASE/products/fusionapps/bi/common/bin/wlst.sh configure_dwtools.py 'WEBLOGIC_ADMINISTRATOR' 'WEBLOGIC_ADMIN_SERVER_HOST' 'WEBLOGIC_ADMIN_SERVER_PORT'
You will be prompted for the WebLogic Administrator password.
Run the following WLST script on CRMHOST1
:
ORACLE_BASE/products/fusionapps/bi/dwtools/scripts/configure_rpd.py
For example:
$ cd ORACLE_BASE/products/fusionapps/bi/dwtools/scripts/ $ ORACLE_BASE/products/fusionapps/bi/common/bin/wlst.sh configure_rpd.py 'DOMAIN_HOME' 'DW_DB_URL' 'DW_DB_SCHEMA' 'MASTER_BI_INSTANCE_HOME' 'WEBLOGIC_ADMIN_SERVER_HOST' 'WEBLOGIC_ADMIN_SERVER_PORT' 'WEBLOGIC_ADMINISTRATOR'
where
DOMAIN_HOME
is the path to the Managed Server domain home. For example, /u02/local/oracle/config/domains/
CRMHOST1
/BIDomain
.
DW_DB_URL
is the string. For example,
'jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST=(LOAD_BALANCE=on) (ADDRESS=(PROTOCOL=TCP) (HOST=BIDWHOST1)(PORT=1521))(ADDRESS= (PROTOCOL=TCP)(HOST=BIDWHOST2) (PORT=1521)))(CONNECT_DATA= (SERVICE_NAME=bidw.mycompany.com)))'
DW_DB_SCHEMA
is the Data Warehouse schema. For example, prefix_DW
.
MASTER_BI_INSTANCE_HOME
is the path to the Master BI Server Instance home. For example, /u02/local/oracle/config/BIInstance
.
WEBLOGIC_ADMIN_SERVER_HOST
is the Oracle WebLogic Server Administration host. For example, CRMHOST1
.
WEBLOGIC_ADMIN_SERVER_PORT is the Oracle WebLogic Server Administration Console Port. For example, 10201.
WEBLOGIC_ADMINISTRATOR
is the Oracle WebLogic Server Administrator.
On all nodes where DAC Server can run, update the /u02/local/oracle/config/domains/
CRMHOST1
/BIDomain/bin/setDomainEnv.sh
script to include the following:
# Set Informatica Environment for DAC Server . ${DOMAIN_HOME}/config/dac/dac_env.sh
For the changes to take effect, restart the Managed Servers and the System Components:
On the Summary of Servers page, select the Control tab.
Select bi_server1 and bi_server2 in the table and then click Shutdown.
After the servers have shut down, select bi_server1 and bi_server2 in the table and then click Start.
Run the following commands to restart the Oracle Business Intelligence system components:
$ cd /u02/local/oracle/config/BIInstancen/bin
$ ./opmnctl stopall
$ ./opmnctl startall
Validate the Oracle BI Applications components:
Log in to the Administration Server console (http://biinternal.mycompany.com:7777/console
) and check the health and status of the Data Warehouse Administration Console Server (DACServer).
Validate the following DAC URL: http://BIVH1:10217/DACServer
.
Check to ensure that the following files have been created:
ORACLE_BASE/config/domains/CRMHOST1/BIDomain/dac/conf-shared/ server.properties ORACLE_BASE/config/domains/CRMHOST1/BIDomain/dac/ conf-shared/security/repository/cwallet.sso
Log in to the database with the DAC schema user name and password and type the following SQL query:
SELECT * FROM W_ETL_REPOS WHERE ROW_WID='DACServerURL';
Check the VALUE
column of the result.
The default value before configuration is http://
CRMHOST1
:10217/DACServer
. The hostname and port will be updated in Step 1 in Section 18.2.4.2.
The Data Warehouse Administration Console (DAC) Server is a singleton: only one active Oracle DAC Server is used at any given time. The Oracle WebLogic Server Migration feature is used to protect Oracle DAC server from failures. The Oracle WebLogic Managed Server in which Oracle DAC server runs is listening on a virtual IP that gets migrated to another node when the failure occurs.For more information on server-migration features, see Chapter 17, "Setting Up Server Migration for an Enterprise Deployment."
Run the following WLST script to move the DAC configuration files to a new shared location:
ORACLE_BASE/products/fusionapps/bi/dac/scripts/moveDACConfigLocation.py
For example:
ORACLE_BASE/products/fusionapps/bi/common/bin/wlst.sh moveDACConfigLocation.py 'DOMAIN_HOME' 'DAC_SHARED_LOCATION'
where
DOMAIN_HOME
is the path to the Administration Server domain home.
DAC_SHARED_LOCATION
is the DAC shared location. For example, ORACLE_BASE
/config/BIShared/dac
.
Restart the Administration Server and Managed Servers (ensure that Node Manager is up and running):
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console)
.
In the Summary of Servers screen, select the Control tab.
Select AdminServer, bi_server1 and bi_server2 in the table and then click Shutdown.
Restart the AdminServer
, bi_server1
, and bi_server2
Managed Servers.
Restart the Oracle Business Intelligence system components:
$ cd /u02/local/oracle/config/BIInstancen/bin
$ ./opmnctl stopall
$ ./opmnctl startall
For more information, see the following sections in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications:
To enable Oracle HTTP Server to route to the Data Warehouse Component Managed Server, you must set the WebLogicHost parameter.
To set the WebLogicHost parameter:
Add the following line to the Oracle HTTP Server's /u01/oracle/config/CommonDomain_webtier
n
/config/OHS/ohs1/moduleconf/FusionVirtualHost_bi.conf
file on WEBHOST1
and WEBHOST2
:
RedirectMatch 301 ^/DACServer$ /DACServer/ RedirectMatch 301 ^/biacm$ /biacm/ # DAC Server <LocationMatch ^/DACServer/> SetHandler weblogic-handler WebLogicHost BIVH1 WebLogicPort 10217 </LocationMatch> ## Context roots for application biacm <LocationMatch ^/biacm/> SetHandler weblogic-handler WebLogicCluster BIADMINVH:10201 </LocationMatch> ## Context roots for application fsm <LocationMatch /setup > SetHandler weblogic-handler WebLogicCluster BIADMINVH:10201 </LocationMatch>
Restart Oracle HTTP Server on both WEBHOST1
and WEBHOST2
:
WEBHOST1> ORACLE_BASE/config/CommonDomain_webtier/bin/opmnctl restartproc ias-component=ohs1 WEBHOST2> ORACLE_BASE/config/CommonDomain_webtier1/bin/opmnctl restartproc ias-component=ohs1
Perform the following additional tasks:
Set the correct DACServer URL in DAC Repository using the SQL statement shown in Example 18-2.
The DACServerURL should be set to point to the load balancer virtual server.
From the ORACLE_BASE
/config/domains/
CRMHOST1
/BIDomain/dac
directory, start the DAC Client using startclient.sh
and try to configure a new connection to validate the DAC Server setup. For more information, see "Logging into DAC for the First Time as an Administrator" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
To validate, access the following URLs:
http://biinternal.mycompany.com:7777/biacm
to verify the status BI Applications Configuration Manager
http://biinternal.mycompany.com:7777/setup/faces/TaskListManagerTop
to verify the status of Oracle Fusion Functional Setup Manager
Also, ensure that clicking on the "Perform Functional Configurations" link from Oracle BI Applications Configuration Manager launches Functional Setup Manager.
http://biinternal.mycompany.com:7777/DACServer
to verify the status of the DAC Server
Verify URLs to ensure that appropriate routing is working from the HTTP Server to the DAC Server.
To verify, access http://WEBHOST1:10621/DACServer
and verify the appropriate functionality.