Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 7 (11.1.7) Part Number E27364-10 |
|
|
PDF · Mobi · ePub |
This chapter describes how to scale out the Oracle Business Intelligence domain.
This chapter includes the following topics:
Section 15.1, "Overview of the Oracle Business Intelligence Domain"
Section 15.2, "Prerequisites for Scaling Out the Oracle Business Intelligence Domain"
Section 15.4, "Prerequisites for Scaling Out Oracle Business Intelligence on FINHOST2"
Section 15.5, "Scaling Out Oracle Business Intelligence Components"
Section 15.6, "Configuring and Validating Oracle Essbase Clustering"
Oracle Fusion Financials uses Oracle Business Intelligence Foundation's common set of Oracle Business Intelligence tools and shared services that enable the Enterprise Performance Management system.
Oracle Fusion Financials uses the following Oracle Business Intelligence tools for financial reporting and analysis purposes:
Oracle Essbase
Oracle Business Intelligence Publisher (Oracle BI Publisher)
Oracle Transaction Business Intelligence
Oracle Business Intelligence Analytics
Oracle Essbase
Oracle Fusion General Ledger combines the traditional general ledger functionality with Oracle Essbase functionality, which is seamlessly embedded within the Oracle Fusion General Ledger. At the time users create their chart of accounts, the balances cube is created automatically. Later, if you make a change such as a cost center is added or a date effective hierarchy is modified, the General Ledger automatically creates or modifies the corresponding balances cube hierarchy. As transactions or journals are posted, the General Ledger automatically updates the multidimensional cube. Unlike a data warehouse, no batch programs need to be run to populate the balances cube; it is all happening in real time when a journal is posted.
Oracle Business Intelligence Publisher
Oracle BI Publisher provides the ability to create and format high quality reports across Oracle Fusion Financials applications. It applies templates, which users design in familiar desktop tools, to standard extracts and reports. For example, it is used widely used in Oracle Fusion Payments for formatting of the check payments and electronic payment files.
Oracle Transaction Business Intelligence
Oracle Transaction Business Intelligence is widely used in Oracle Fusion Financials as a reporting tool. Using Oracle Transaction Business Intelligence, users can perform adhoc queries directly from transaction tables using drag-and-drop functionality to build custom reports in real time from the various Oracle Fusion Financials applications. It helps immensely in reducing the need to build and maintain customized reports.
Oracle Business Intelligence Analytics
Oracle Business Intelligence Analytics provides day-to -day key performance indicators (KPIs) of any item in Oracle Fusion Financials. Intelligence and analytics are embedded within the context of business transactions to help users complete the transitions. For example, before users post a journal, the system will tell them the impact the journal will have on the account balances. This eliminates the need to navigate to a separate page to run a query or run a report. End users will not be distracted from the task at hand, reporting and process demand is reduced, and smarter decisions are made in the context of the transaction.
Figure 2-10 in Chapter 2, "Introduction to the Enterprise Deployment Reference Topologies," shows the topology for the Oracle Business Intelligence domain within the overall reference enterprise deployment topology.
Before you begin, ensure the following:
Node Manager has been started in the Secure Sockets Layer (SSL) mode by following the instructions in Chapter 7, "Setting Up Node Manager for an Enterprise Deployment."
The Administration Console's Follow Configuration Changes feature has been disabled (to eliminate redirections):
Log into the Administration Console (http://biinternal.mycompany.com:7777/console
) and go to Preferences > Shared Preferences.
Deselect Follow Configuration Changes and click Save.
To start the default Node Manager:
Stop any Node Manager running on FINHOST2
using one of the following methods:
Use Ctrl+C in the shell where it was started.
Use the standard process-identification and kill commands in the operating system appropriate to Oracle Fusion Financials and the Oracle Fusion Applications enterprise deployment.
Change directory to ORACLE_BASE
/products/fusionapps/wlserver_10.3/common/nodemanager
and edit the nodemanager.properties
file with the following:
SecureListener=false
Change directory to ORACLE_BASE
/products/fusionapps/oracle_common/common/bin
and run the following script:
./setNMProps.sh
Change directory to ORACLE_BASE
/products/fusionapps/wlserver_10.3/server/bin
and run the following script:
./startNodeManager.sh
Node Manager starts on FINHOST2
.
Prerequisites include the following:
You must configure the location for all persistence stores to a directory visible from both nodes. Change all persistent stores to use this shared base directory.
Log in to the Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Domain Structure window, expand the Services node.
In the Change Center, click Lock & Edit.
Click the Persistent Stores node.
The Summary of Persistent Stores page displays.
Click BipJmsStore and enter a directory that is located in the shared storage. This shared storage is accessible from both FINHOST1
and FINHOST2
:
ORACLE_BASE/config/domains/FINHOST1/BIDomain/BipJmsStore
Click Save.
Repeat Steps 4 through 6 for the JRFWSAsyncFileStore
persistence file store with the shared location ORACLE_BASE
/config/domains/
FINHOST1
/BIDomain/JRFWSAsyncFileStore
.
Click Activate Changes.
The changes will not take effect until the Managed Server is restarted.
Do the following:
Ensure that Node Manager is up and running.
On the Summary of Servers page, select the Control tab.
Select bi_server1 in the table and then click Shutdown.
After the server has shut down, select bi_server1 in the table and then click Start.
Run the following commands on FINHOST1
to restart the Oracle Business Intelligence system components:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopall $ ./opmnctl startall
Make sure that you have performed the steps described in Section 16.1, "Enabling Virtual IPs on FINHOST1 and FINHOST2" before setting the bi_server1
listen address.
To set the listen address for the Managed Server:
Log in to the Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Change Center, click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers. The Summary of Servers page is displayed.
Select bi_server1 in the table. The Settings page for bi_server1
is displayed.
Set the Listen Address to BIVH1
.
Note:
Both BIVH1
and BIVH2
are pingable.
Click Save.
Click Activate Changes.
The changes will not take effect until the bi_server1
Managed Server is restarted (ensure that Node Manager is up and running):
On the Summary of Servers page, select the Control tab.
Select bi_server1 in the table and then click Shutdown.
After the server has shut down, select bi_server1 in the table and then click Start.
Restart the Oracle Business Intelligence system components on FINHOST1
:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopall $ ./opmnctl startll
To enable Oracle HTTP Server to route to bi_cluster
, which contains the bi_server
n
Managed Servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:
Update the WebLogicCluster parameter in the FusionVirtualHost_fin.conf
file to contain a cluster list of virtual host
:port
entries. (On WEBHOST1
: ORACLE_BASE
/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf/FusionVirtualHost_bi.conf
. On WEBHOST2
: ORACLE_BASE
/config/CommonDomain_webtier1/config/OHS/ohs2/moduleconf/FusionVirtualHost_bi.conf
.)
Note:
You must update the FusionVirtualHost_bi.conf
file in two locations:
Under the internal virtual host for Oracle Business Intelligence
Under the external virtual host for Oracle Business Intelligence
For example, for the internal virtual host:
<LocationMatch ^/analytics/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch>
For the external virtual host:
<LocationMatch ^/analytics/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 WLProxySSL ON WLProxySSLPassThrough ON RewriteEngine ON RewriteOptions inherit </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=ohs2
The servers specified in the WebLogicCluster parameters are only important at startup time for the plug-in. The list must provide at least one running cluster member for the plug-in to discover other members in the cluster. The listed cluster member must be running when Oracle HTTP Server is started. Oracle WebLogic Server and the plug-in work together to update the server list automatically with new, failed, and recovered cluster members.
Sample scenarios include:
Example 1: If you have a two-node cluster and then add a third member, you do not need to update the configuration to add the third member. The third member will be discovered dynamically at run time.
Example 2: You have a three-node cluster, but only two nodes are listed in the configuration. However, if both listed nodes are down when you start Oracle HTTP Server, then the plug-in would fail to route to the cluster. You must ensure that at least one of the listed nodes is running when you start Oracle HTTP Server.
If you list all the members of the cluster, then you guarantee you can route to the cluster, assuming at least one member is running when Oracle HTTP Server is started. For more information on configuring the Oracle WebLogic Serverplug-in, see Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server.
This section describes how to scale out the Oracle Business Intelligence system using the Configuration Assistant. It is assumed that an Oracle Business Intelligence ORACLE_BASE (binaries) has already been installed and is available from FINHOST1
and FINHOST2
, and that a domain with an Administration Server has been created. This is the domain that will be extended in this chapter to support Oracle Business Intelligence components.
Important:
Oracle strongly recommends that you read the Oracle Fusion Middleware release notes for any additional installation and deployment considerations before starting the setup process.
This section includes the following topics:
Section 15.5.1, "Scaling Out the Oracle Business Intelligence System on FINHOST2"
Section 15.5.4, "Configuring Secondary Instances of Singleton System Components"
Section 15.5.7, "Configuring a Default Persistence Store for Transaction Recovery"
Section 15.5.8, "Starting and Validating Oracle Business Intelligence on FINHOST2"
Section 15.5.9, "Validating Access Through Oracle HTTP Server"
Section 15.5.10, "Configuring Node Manager for the Managed Servers"
Section 15.5.11, "Configuring Server Migration for the Managed Servers"
To scale out the Oracle Business Intelligence system:
Ensure that the bi_server1
server is running.
Change directory to the location of the Configuration Assistant:
FINHOST2> ORACLE_BASE/products/fusionapps/bi/bin
Start the Oracle Business Intelligence Configuration Assistant:
FINHOST2> ./config.sh
In the Welcome screen, click Next.
In the Prerequisite Checks screen, verify that all checks complete successfully, and then click Next.
In the Create, Scale Out or Extend BI System screen, select Scale Out BI System and enter the following:
Host Name: FINHOST1
Port: 10201
User name: WLS_Administrator
User Password: WLS_Administrator_password
Click Next.
In the Scale Out BI System Details screen, enter the following:
Middleware Home: ORACLE_BASE
/products/fusionapps
(dimmed)
Oracle Home: ORACLE_BASE
/products/fusionapps/bi
(dimmed)
WebLogic Server Home: ORACLE_BASE
/products/fusionapps/wlserver_10.3
(dimmed)
Domain Home: /u02/local/oracle/config/domains/
FINHOST1
/BIDomain
Applications Home: /u02/local/oracle/config/applications/
FINHOST1
/BIDomain
Instance Home: Defaults to /u02/local/oracle/config/BIInstance1
Instance Name: BIInstance1
(dimmed)
Click Next.
In the Configure Ports screen, select "Specify Ports using Configuration File."
Use the bi_staticports.ini
file from the ORACLE_BASE
/products/ports
directory.
Click Next.
In the Specify Security Updates screen, choose whether you want to receive security updates from Oracle support and if you do, enter your e-mail address.
Click Next.
In the Summary screen, click Configure.
In the Configuration Progress screen, verify that all the Configuration Tools have completed successfully and click Next.
In the Complete screen, click Finish.
To start Node Manager in SSL mode:
Stop the default Node Manager running on FINHOST2
using one of the following methods:
Use CTRL+C in the shell where it was started
Use the standard process-identification and kill commands in the operating system appropriate to Oracle Fusion Financials and the Oracle Fusion Applications enterprise deployment.
Start Node Manager in SSL mode on FINHOST2
:
FINHOST2> cd ORACLE_BASE/config/nodemanager/FINHOST2 FINHOST2> ./startNodeManagerWrapper.sh &
Update the Node Manager for the FINHOST2
machine using the Oracle WebLogic Server Console by doing the following:
Log in to the Administration Server: http://biinternal.mycompany.com:7777/console
.
Navigate to BIDomain> Environment > Machines.
In the left-hand pane, click Lock & Edit.
In the right-hand pane, click FINHOST2
.
In the window that opens, click the Node Manager tab and set the following attributes:
– Type - SSL
– Listen Address - <FINHOST2
>
– Listen Port - 5556
Click Save and then Activate Changes.
The changes will not take effect until the bi_server2
Managed Server is restarted.
Do the following:
Stop the Administration Server:
FINHOST1> ORACLE_BASE/config/domains/FINHOST1/BIDomain/bin/stopWebLogic.sh
Connect to the Administration Server through nmConnect
and start the Administration Server using nmstart
:
– Set the following environment variable:
export WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=
ORACLE_BASE/config/keystores/fusion_trust.jks"
– Start the Administration Server:
FINHOST1> cd ORACLE_BASE/products/fusionapps/ wlserver_10.3/common/bin FINHOST1> ./wlst.sh
– In the WLST shell, execute the following command:
wls:/offline> nmConnect (username='Admin_User',password='Admin_ Password',host='FINHOST1',port='5556', nmType='ssl', domainDir= 'ORACLE_BASE/config/domains/FINHOST1/BIDomain') wls:/nm/domain_name> nmStart ('AdminServer') wls:/nm/domain_name> exit ()
Note:
The username and password used in nmConnect
are the Node Manager credentials (username and password) specified when creating the provisioning response file. This is shown in Figure 5-2 in Chapter 5, "Using the Provisioning Process to Install Components for an Enterprise Deployment."
Restart the bi_server2
Managed Server:
– On the Summary of Servers page, select the Control tab.
– Select bi_server2 in the table and then click Shutdown.
– After the server has shut down, select bi_server2 in the table and then click Start.
To scale out the system components, do the following in Oracle Enterprise Manager Fusion Middleware Control:
Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em
).
Expand the Business Intelligence node in the Farm_BIDomain window.
Click coreapplication.
Click Capacity Management, then click Scalability.
Click Lock and Edit Configuration.
For the FINHOST2
BIInstance1 Oracle instance, increment the Oracle Business Intelligence components by 1:
BI Servers
Presentation Servers
JavaHosts
Change the Port Range From and Port Range To to be the same as the FINHOST1
BIInstance Oracle instance.
Click Apply.
Click Activate Changes.
You do not need to restart at this point, because you will perform a restart after completing the steps in Section 15.5.4, "Configuring Secondary Instances of Singleton System Components."
Oracle Business Intelligence Scheduler and Oracle Business Intelligence Cluster Controller are singleton components that operate in active/passive mode. Configure a secondary instance of these components so that they are distributed for high availability.
To configure secondary instances, do the following in Fusion Middleware Control:
Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em
).
Expand the Business Intelligence node in the Farm_BIDomain window.
Click coreapplication.
Click Availability, then click Failover.
Click Lock and Edit Configuration to activate the Primary/Secondary Configuration section of the Availability tab.
Specify the Secondary Host/Instance for BI Scheduler and BI Cluster Controller.
Click Apply.
Click Activate Changes.
Click Restart to apply recent changes.
From Manage System, click Restart.
Click Yes when prompted to confirm that you want to restart all Business Intelligence components.
Note:
Under Potential Single Points of Failure, no problem should be reported for BI Scheduler and BI Cluster Controller.
This section explains how to configure the bi_server2
Managed Server, and contains the following topics:
Section 15.5.5.1, "Setting the Listen Address for the bi_server2 Managed Server"
Section 15.5.5.2, "Configuring Custom Identity and Custom Trust for the bi_server2 Managed Server"
Section 15.5.5.3, "Disabling Host Name Verification for the bi_server2 Managed Server"
Section 15.5.5.4, "Adding bi_server2 System Properties to the Server Start Tab"
Make sure that you have performed the steps described in Section 16.1, "Enabling Virtual IPs on FINHOST1 and FINHOST2" before setting the bi_server2
listen address.
To set the listen address for the Managed Server:
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Change Center, click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers. The Summary of Servers page is displayed.
Select bi_server2 in the table. The settings page for bi_server2
is displayed.
Set the Listen Address to BIVH2
.
Click Save.
Click Activate Changes.
The changes will not take effect until the Managed Server is restarted.
Do the following:
Ensure that Node Manager is up and running.
On the Summary of Servers page, select the Control tab.
Select bi_server2 in the table and then click Shutdown.
After the server has shut down, select bi_server2 in the table and then click Start.
To configure custom identity and custom trust:
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Change Center, click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
The Summary of Servers page displays.
Select bi_server2 in the table. The Settings page for bi_server2
displays.
Click Keystores, and then do the following:
Click Change next to Demo Identity and Demo Trust.
Select Custom Identity and Custom Trust from the Keystores dropdown list and click Save.
Under Identity, do the following:
– Change the Custom Identity Keystore entry to point to the ORACLE_BASE
/config/keystores/
FINHOST2
_fusion_identity.jks
file.
– Enter and confirm the Custom Identity Keystore Passphrase. This should be the same as the keystorepassword field described in the first bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
Under Trust, do the following:
– Change the Custom Identity Keystore entry to point to the ORACLE_BASE
/config/keystores/fusion_trust.jks
file.
– Enter and confirm the Custom Trust Keystore Passphrase. This should be the same as the keystorepassword field described in the first bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
– Click Save.
Click SSL, and then do the following:
Ensure that Identity and Trust Locations is set to Keystores.
Under Identity, do the following:
– Change the Private Key Alias to FINHOST2
_fusion
.
– Enter and confirm the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
– Click Save.
Click Activate Changes.
Set the following property in ORACLE_BASE
/products/fusionapps/wlserver_10.3/common/bin/wlst.sh
:
WLST_PROPERTIES=" -Dweblogic.wlstHome='${WLST_HOME}'
-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_BASE/config/keystores/
fusion_trust.jks ${WLST_PROPERTIES}"
This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server (see Chapter 7, "Setting Up Node Manager for an Enterprise Deployment"). If you have not configured the server certificates, you will receive errors when managing the different WebLogic servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again after the enterprise deployment topology configuration is complete as described in Chapter 7, "Setting Up Node Manager for an Enterprise Deployment."
To disable host name verification:
Log in to Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
Click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers. The Summary of Servers page is displayed.
Select bi_server2 in the table. The settings page for the server is displayed.
Click the SSL tab.
Expand the Advanced section of the page.
Set Host Name Verification to None.
Click Save.
Click Activate Changes.
The change will not take effect until the bi_server2
Managed Server is restarted (make sure that Node Manager is up and running):
In the Summary of Servers screen, select the Control tab.
Select bi_server2 in the table and then click Shutdown.
Select bi_server2 in the table and then click Start.
Restart the Oracle Business Intelligence system components on FINHOST2
:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl stopall $ ./opmnctl startall
After scaling out the bi_server2
Managed Server, you must add a new system property to the Server Start tab of this Managed Server.
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
Click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
The Summary of Servers page displays.
Select bi_server2 in the table.
The settings page for the server displays.
Click Server Start.
Add the following property to the arguments:
-DJDBCProgramName=DS/BIDomain/bi_server2
Click Save and then Activate Changes.
Restart the bi_server2
Managed Server (ensure sure that Node Manager is up and running):
In the Summary of Servers screen, select the Control tab.
Select bi_server2 in the table and then click Shutdown.
Select bi_server2 in the table and then click Start.
Restart the BI System Components on FINHOST2
:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl stopall $ ./opmnctl startall
This section describes additional high availability configuration tasks for Oracle BI Enterprise Edition, Oracle Real-Time Decisions, Oracle BI Publisher, and Oracle Financial Reports. It includes the following topics:
Section 15.5.6.1, "Additional Configuration Tasks for Oracle BI Scheduler"
Section 15.5.6.2, "Additional Configuration Tasks for Oracle Real-Time Decisions"
Section 15.5.6.3, "Additional Configuration Tasks for Oracle BI Publisher"
Section 15.5.6.4, "Additional Configuration Tasks for Oracle BI for Microsoft Office"
Section 15.5.6.5, "Additional Configuration Tasks for Oracle Financial Reporting"
If you use server-side scripts with Oracle BI Scheduler, it is recommended that you configure a shared directory for the scripts so that they can be shared by all Oracle BI Scheduler components in a cluster.
Perform these steps only if you are using server-side scripts.
To share Oracle BI Scheduler scripts:
Create an ORACLE_BASE
/config/BIShared/OracleBISchedulerComponent/coreapplication_obisch1
directory.
From FINHOST1
, copy the default Oracle BI Scheduler scripts (for example, /u02/local/oracle/config/BIInstance/bifoundation/OracleBISchedulerComponent/coreapplication_obisch1/scripts/common
) and custom Oracle BI Scheduler scripts (for example, /u02/local/oracle/config/BIInstance/bifoundation/OracleBISchedulerComponent/coreapplication_obisch1/scripts/scheduler
) to the following location:
ORACLE_BASE
/config/BIShared/OracleBISchedulerComponent/coreapplication_obisch1
Update the SchedulerScriptPath and DefaultScriptPath elements of the Oracle BI Scheduler instanceconfig.xml file, as follows:
SchedulerScriptPath: Refers to the path where Oracle BI Scheduler-created job scripts are stored. Change this to the path of the shared BI Scheduler scripts location.
DefaultScriptPath: Specifies the path where user-created job scripts (not agents) are stored. Change this to the path of the shared BI Scheduler scripts location.
The instanceconfig.xml
files for Oracle BI Scheduler are in the following locations:
On FINHOST1: /u02/local/oracle/config/BIInstance/config/OracleBISchedulerComponent/coreapplication_obisch1
On FINHOST2: /u02/local/oracle/config/BIInstance1/config/OracleBISchedulerComponent/coreapplication_obisch1
You must update these files for each Oracle BI Scheduler component in the deployment.
Restart the Oracle BI Scheduler component.
On FINHOST1:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopproc ias-component=coreapplication_obisch1 $ ./opmnctl startproc ias-component=coreapplication_obisch1
On FINHOST2:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl stopproc ias-component=coreapplication_obisch1 $ ./opmnctl startproc ias-component=coreapplication_obisch1
This sections contains the following topics:
Section 15.5.6.2.1, "Configuring Oracle Real-Time Decisions Clustering Properties"
Section 15.5.6.2.2, "Adding Oracle RTD System Properties to the Server Start Tab"
Perform these steps in Fusion Middleware Control to set up cluster-specific configuration properties for Oracle Real-Time Decisions (Oracle RTD). You only need to perform the steps on one of the nodes in your deployment. You do not need to set cluster-specific configuration properties for Oracle RTD for subsequent nodes.
Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em
).
Expand the Application Deployments node in the Farm_BIDomain window.
Expand OracleRTD(11.1.1)(bi_cluster).
Click any node under it. For example, OracleRTD(11.1.1)(bi_server1).
In the right pane, click Application Deployment, and then select System MBean Browser.
In the System MBean Browser pane, expand Application Defined MBeans.
For any one of the servers under OracleRTD, navigate to the MBean and set the attribute, as shown in Table 15-1. Other servers automatically get updated with the value you set.
Click Apply.
After scaling out Oracle RTD, use the Administration Console to add three system properties to the Server Start tab of each Managed Server.
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
Click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
The Summary of Servers page displays.
Select bi_server<1,2> in the table.
The settings page for the server displays.
Click Server Start.
Add the following property to the arguments:
-Drtd.clusterRegistryJobIntervalMs=12000 -Drtd.clusterDepartureThresholdMs=50000 -Drtd.clusterDepartureThreshold2Ms=50000
Click Save and then Activate Changes.
Restart the bi_server<1,2>
Managed Server (ensure sure that Node Manager is up and running):
In the Summary of Servers screen, select the Control tab.
Select bi_server<1,2> in the table and then click Shutdown.
Select bi_server<1,2> in the table and then click Start.
Restart the BI System Components on FINHOST1
and FINHOST2
:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl stopall $ ./opmnctl startall
Performing this task enables an instance of Oracle RTD to be migrated successfully from one host to another in the event of a failure of a Managed Server.
Even after these changes, if the server migration finishes in less than 50 seconds, the Oracle RTD batch framework will be in an inconsistent state.
If the enterprise has deployed any RTD Inline Services that host Batch Job implementations, and if after a server migration the batch console command, "batch-names", or its brief name, "bn", shows no registered batch jobs, then the Oracle RTD Batch Manager service must be stopped and restarted. To do this, perform these steps:
In Fusion Middleware Control, expand the WebLogic Domain node in the left pane. Then, right-click BIDomain and select System MBean Browser.
Locate SDPropertyManager > Misc MBean under Application Defined MBeans > OracleRTD > Server:bi_servern.
Be sure to select the Misc MBean that corresponds to the local node where you are making the change. For example, if you are connecting to APPHOST1
, then make sure to update the attribute associated with bi_server1
.
Set the BatchManagerEnabled attribute to false and click Apply.
Set the BatchManagerEnabled attribute back to true and click Apply. Performing this task causes the Batch Manager to stop and be restarted.
When it restarts, it will be running on either the same server as before, or on a different server.
After restarting Batch Manager, note that the corresponding MBean does not always immediately get refreshed on the server where Batch Manager comes back up, so this is not a concern. Instead, verify that Batch Manager is now operational by using the Batch Console tool:
Locate the zip file for the Oracle RTD client tools in the following location:
ORACLE_BASE/products/fusionapps/bi/clients/rtd/rtd_client_11.1.1.zip
Because most Oracle RTD client tools do not run on UNIX, unzip this file in a location on a Windows machine (referred to here as RTD_HOME). Then, locate the batch console jar file in:
RTD_HOME/client/Batch/batch-console.jar
Change to this directory and execute the jar, passing to it the URL and port of either the Managed Server, or of the cluster proxy:
java -jar batch-console.jar -url http://SERVER:PORT
When prompted, enter the user name and password of a user who is a member of the Administrator role, BI_Adminstrator role, or some other role authorized to administer Oracle RTD batch jobs.
When prompted for a command, enter bn
:
Checking server connection... command: bn CrossSellSelectOffers command:quit
If Batch Manager has successfully restarted, then the bn
command lists the names of all batch implementations hosted by all deployed RTD Inline Services.
The commonly deployed example, CrossSell, hosts a batch implementation named CrossSellSelectOffers, shown in the preceeding example.
Perform the steps in this section on each machine where Oracle BI Publisher is configured.
This section includes the following topics:
To configure Oracle BI Publisher integration with Oracle BI Presentation Services:
Log in to Oracle BI Publisher (http://biinternal.mycompany.com:7777/xmlpserver
) with Administrator credentials and select the Administration tab.
Under Integration, select Oracle BI Presentation Services.
Verify and update the following:
Server Protocol: http
Server: biinternal.mycompany.com
Port: 7777
URL Suffix: analytics-ws/saw.dll
Click Apply.
Under System Maintenance, select Server Configuration.
In the Catalog section, change the BI Publisher Repository value to the shared location for the Configuration Folder. For example:
ORACLE_BASE/config/BIShared/BIPublisher/repository
Click Apply.
Restart your Oracle BI Publisher application:
Log in to the Administration Console (http://biinternal.mycompany.com:7777/console
).
Click Deployments in the Domain Structure window.
Select bipublisher(11.1.1).
Click Stop, and then select When Work Completes or Force Stop Now.
After the application has stopped, click Start and then Start Servicing All requests.
The Oracle BI EE Data Source must point to the clustered Oracle BI Servers through the Cluster Controllers. Perform this task in Oracle BI Publisher.
To set the Oracle BI EE data source in Oracle BI Publisher:
Log in to Oracle BI Publisher (http://biinternal.mycompany.com:7777/xmlpserver
) with Administrator credentials and select the Administration tab.
Under Data Sources, select JDBC Connection.
Update the Oracle BI EE data source setting by changing the Connection String parameter to the following:
jdbc:oraclebi://primary_cluster_controller_host:primary_cluster_controller_ port/PrimaryCCS=primary_cluster_controller_host;PrimaryCCSPort=primary_cluster_ controller_port;SecondaryCCS=secondary_cluster_controller_host; SecondaryCCSPort=secondary_cluster_controller_port;
For example:
jdbc:oraclebi://FINHOST1:10212/PrimaryCCS=FINHOST1;PrimaryCCSPort=10212; SecondaryCCS=FINHOST2;SecondaryCCSPort=10212;
Note:
Since the Cluster Controller Port may be different between FINHOST1
and FINHOST2
, you can use the following procedure to check the port being used:
Log in to the Oracle Enterprise Manager Console: http://biinternal.mycompany.com:7777/em
.
Expand Farm_Domain > Business Intelligence > coreapplication.
Navigate to Availability.
Check the port number used by the Cluster Controller on FINHOST1
and FINHOST2
.
Do one of the following:
Select Use System User.
Deselect Use System User and specify BIImpersonateUser credentials.
For more information, see "Credentials for Connecting to the Oracle BI Presentation Catalog" in Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.
Click Test Connection. You should receive a "Connection established successfully" message.
Click Apply.
You must configure the location for all persistence stores to a directory visible from both nodes. Change all persistent stores to use this shared base directory.
On FINHOST2:
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Domain Structure window, expand the Services node and then click the Persistence Stores node. The Summary of Persistence Stores page is displayed.
Click Lock & Edit.
Click New, and then Create File Store.
Enter a name (for example, BipJmsStore2
) and target (for example, bi_server2
). Enter a directory that is located in shared storage so that it is accessible from both FINHOST1
and FINHOST2
:
ORACLE_BASE
/config/domains/
FINHOST1
/BIDomain/BipJmsStore
Click OK and then Activate Changes.
In the Domain Structure window, expand the Services node and then click the Messaging > JMS Servers node. The Summary of JMS Servers page is displayed.
Click Lock & Edit.
Click New.
Enter a name (for example, BipJmsServer2
) and in the Persistence Store drop-down list, select BipJmsStore2 and click Next.
Select bi_server2 as the target.
Click Finish and Activate Changes.
In the Domain Structure window, expand the Services node and then click the Messaging > JMS Modules node. The JMS Modules page is displayed.
In the Change Center, click Lock & Edit.
Click BipJmsResource and then click the Subdeployments tab.
Select BipJmsSubDeployment under Subdeployments.
Add the new Oracle BI Publisher JMS Server (BipJmsServer2) as an additional target for the subdeployment.
Click Save and then Activate Changes.
To validate, do the following:
Log in to each Oracle BI Publisher URL.
Navigate to Administration > System Maintenance > Scheduler Diagnostics.
All statuses should be in a Passed state and both instances should be visible.
This section includes the following topics:
Section 15.5.6.4.1, "Configuring Oracle BI for Microsoft Office Properties"
Section 15.5.6.4.2, "Validating Oracle BI for Microsoft Office"
To perform additional configuration tasks for Oracle BI for Microsoft Office:
Validate the Oracle BI Enterprise Edition Office Server setup by accessing http://biinternal.mycompany.com:7777/bioffice/about.jsp
.
The About Oracle BI EE Office Server page displays.
Go to the Oracle BI Enterprise Edition Office Server directory. For example:
/u02/local/oracle/config/domains/
FINHOST1
/BIDomain/servers/bi_server1/tmp/_WL_user/bioffice_11.1.1/cvsibb/war/WEB-INF
If you are not sure how to locate the Oracle BI Enterprise Edition Office Server directory, check the LogDir parameter on the About Oracle BI EE Office Server page. The Oracle BI Enterprise Edition Office Server directory is the parent directory of the log directory.
Note:
You can determine the exact location for FINHOSTn by using the following URL: http://BIVH
n
:10217/bioffice/about.jsp
.
On both FINHOST1
and FINHOST2
, open bioffice.xml for editing and modify the BI Office properties shown in Table 15-2.
Table 15-2 BI Office Properties in bioffice.xml
Property Name | Valid Value | Description |
---|---|---|
SawBaseURL |
http://biinternal.mycompany.com:7777/analytics/saw.dll or http://biinternal.mycompany.com:7777/analytics-ws/saw.dll |
Load Balancer Virtual Server Name URL for Oracle BI Presentation Services. Important: If SSO is enabled, then enter the URL for the protected analytics servlet that you deployed when configuring BI Office to integrate with the SSO-enabled Oracle BI Server. The URL that is specified for this property is used for Web services requests between the BI Office Server and Presentation Services. |
SawUseSSO |
0 = No (Default) 1 = Yes |
Set this property to |
SawWebURLforSSO |
http://biinternal.mycompany.com:7777/analytics/saw.dll |
When SSO is enabled, use this property to enter the public URL that allows external users to access Oracle Business Intelligence using SSO from the Oracle BI Add-in for Microsoft Office. |
Restart the BI Office application:
Log in to the Administration Console (http://biinternal.mycompany.com:7777/console
).
Click Deployments in the Domain Structure window.
Select bioffice(11.1.1).
Click Stop.
After the application has stopped, click Start.
Validate that the SawBaseURL parameter has been updated on the About Oracle BI EE Office Server page.
The changes you made to the About Oracle BI EE Office Server page in the preceding steps are shown in Figure 15-1.
To validate configuration for Oracle BI for Microsoft Office:
Log in to Oracle BI Presentation Services at:
http://biinternal.mycompany.com:7777/analytics
In the lower left pane, under the Get Started heading, select Download BI Desktop Tools and then select Oracle BI for MS Office.
Install Oracle BI for Microsoft by running the Oracle BI Office InstallShield Wizard.
Open Microsoft Excel or Microsoft PowerPoint.
From the Oracle BI menu, select Preferences.
In the Connections tab, select New.
Enter values for the following fields:
Server Name: Provide a name for the connection.
BI Office Server: Provide the URL for the Oracle BI Office Server.
Application Name: Enter the Application Name that you defined for the Oracle BI Office Server when you deployed the Oracle BI Office Server application to WLS. The default name is bioffice.
Port: Enter the Oracle BI Office Server port number.
Figure 15-2 shows the New Connection dialog.
Click Test Connection to test the connection between the add-in and the Oracle BI Office Server.
Successful connections receive a "Test connection successful" message, as shown in Figure 15-3.
Log in as an Administrator (for example, weblogic
) and validate that you can access the Oracle BI Task Pane, as shown in Figure 15-4.
There are additional configuration tasks to perform for Oracle Financial Reporting. Do the following on FINHOST1
and FINHOST2
:
Update the VARIABLE_VALUE_LIMIT
from 4096 to 3072000 in the NQSConfig.INI
file. For example,
VARIABLE_VALUE_LIMIT = 3072000;
On FINHOST1
, this file is located in /u02/local/oracle/config/BIInstance/config/OracleBIServerComponent/coreapplication_obis1
.
On FINHOST2
, this file is located in /u02/local/oracle/config/BIInstance1/config/OracleBIServerComponent/coreapplication_obis1
.
Run the following commands to restart the Oracle Business Intelligence system components on FINHOST1
and FINHOST2
:
$ cd /u02/local/oracle/config/BIInstancen/bin
$ ./opmnctl stopall
$ ./opmnctl startall
Each server has a transaction log that stores information about committed transactions that are coordinated by the server that may not have been completed. The WebLogic Server uses this transaction log for recovery from system crashes or network failures. To leverage the migration capability of the Transaction Recovery Service for the servers within a cluster, store the transaction log in a location accessible to a server and its backup servers.
Note:
Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network (SAN).
To set the location for the default persistence store:
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
In the Change Center, click Lock & Edit.
In the Domain Structure window, expand the Environment node and then click the Servers node. The Summary of Servers page is displayed.
Click bi_server1 in the table. The Settings page for the selected server is displayed, and defaults to the Configuration tab.
Navigate to Configuration > Services.
Create a tlogs
directory on FINHOST1
:
FINHOST1> mkdir ORACLE_BASE/config/domains/FINHOST1/BIDomain/tlogs
Enter the newly created tlogs
path in the Directory section of the Default Store. For example:
FINHOST1> ORACLE_BASE/config/domains/FINHOST1/BIDomain/tlogs
Click Save.
Click Activate Changes.
Start the Managed Servers to activate the changes (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 bi_server1 and bi_server2 in the table and then click Shutdown.
Start the bi_server1
and bi_server2
servers.
Restart the Oracle Business Intelligence system components on FINHOST1
and FINHOST2
:
$ cd /u02/local/oracle/config/BIInstancen/bin
$ ./opmnctl stopall
$ ./opmnctl startall
Note:
To enable migration of the Transaction Recovery service, specify a location on a persistent storage solution that is available to other servers in the cluster. Both bi_server1
and bi_server2
must be able to access this directory.
This section includes the following topics:
Section 15.5.8.2, "Starting the Oracle Business Intelligence System Components"
Section 15.5.8.3, "Validating Oracle Business Intelligence URLs"
To start the bi_server2
Managed Server:
Start the bi_server2
Managed Server using the Oracle WebLogic Server Administration Console, as follows:
Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console
).
Expand the Environment node in the Domain Structure window.
Select Servers. The Summary of Servers page is displayed.
Click the Control tab.
Select bi_server2 and then click Start.
Verify that the server status is reported as "Running" in the Administration Console. If the server is shown as "Starting" or "Resuming," wait for the server status to change to "Started." If another status is reported (such as "Admin" or "Failed"), check the server output log files for errors.
You can control Oracle Business Intelligence system components using opmnctl
commands.
To start the Oracle Business Intelligence system components using the opmnctl
command-line tool:
Go to the directory that contains the Oracle Process Manager and Notification Server command-line tool, located in /u02/local/oracle/config/BIInstance1/bin
.
Run the opmnctl
command to start the Oracle Business Intelligence system components:
./opmnctl startall
: Starts Oracle Process Manager and Notification Server and all Oracle Business Intelligence system components
./opmnctl start
: Starts Oracle Process Manager and Notification Server only
./opmnctl startproc ias-component=
component_name
: Starts a particular system component. For example, where coreapplication_obips1
is the Presentation Services component:
./opmnctl startproc ias-component=coreapplication_obips1
Check the status of the Oracle Business Intelligence system components:
./opmnctl status
Access the following URLs:
Access http://BIVH2:10217/analytics
to verify the status of bi_server2
.
Access http://BIVH2:10217/wsm-pm
to verify the status of Web Services Manager. Click Validate Policy Manager. A list of policies and assertion templates available in the data is displayed.
Note: The configuration is incorrect if no policies or assertion templates appear.
Access http://BIVH2:10217/xmlpserver
to verify the status of the Oracle BI Publisher application.
Access http://BIVH2:10217/ui
to verify the status of the Oracle Real-Time Decisions application.
Access http://BIVH2:10217/mapviewer
to verify the status of the map view functionality in Oracle BI EE.
Access http://BIVH2:10217/hr
to verify Financial Reporting.
Access http://BIVH2:10217/calcmgr/index.htm
to verify Calculation Manager.
Access http://BIVH2:10217/aps/Test
to verify APS.
Access http://BIVH2:10217/workspace
to verify workspace.
You should verify URLs to ensure that the appropriate routing and failover is working from Oracle HTTP Server to bi_cluster. Perform these steps to verify the URLs:
While bi_server2
is running, stop bi_server1
using the Oracle WebLogic Server Administration Console.
Access the following URLs to verify that routing and failover is functioning properly:
http://WEBHOST1:10621/analytics
http://WEBHOST1:10621/xmlpserver
http://WEBHOST1:10621/ui
(access only available on Microsoft Internet Explorer 7 or 8)
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
http://WEBHOST1:10621/workspace
Start bi_server1
from the Oracle WebLogic Server Administration Console.
Stop bi_server2
from the Oracle WebLogic Server Administration Console.
Access the following URLs to verify that routing and failover is functioning properly:
http://WEBHOST1:10621/analytics
http://WEBHOST1:10621/xmlpserver
http://WEBHOST1:10621/ui
(access only available on Microsoft Internet Explorer 7 or 8)
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
http://WEBHOST1:10621/workspace
Start bi_server2
from the Oracle WebLogic ServerAdministration Console.
Oracle recommends using host name verification for the communication between Node Manager and the servers in the domain. This requires the use of certificates for the different addresses communicating with the Administration Server and other servers. See Chapter 7, "Setting Up Node Manager for an Enterprise Deployment" for further details. The procedures in that chapter must be performed twice using the information provided in Table 15-3.
Table 15-3 Details for Host Name Verification for Node Manager and Servers
Run | Host Name (Host) | Server Name (WLS_SERVER) |
---|---|---|
Run1: |
|
|
Run2: |
|
|
Note:
If you configured Node Manager for the Managed Servers earlier, you do not need to configure it again.
Server Migration is required for proper failover of the Oracle BI Publisher components in the event of failure in any of the FINHOST1
and FINHOST2
nodes. For more information, see Chapter 18, "Setting Up Server Migration for an Enterprise Deployment."
This section describes how to configure and validate secondary instances of Oracle Essbase Agent so that they are distributed for high availability.
Note:
In Oracle Fusion Applications, Oracle Essbase can only connect to and work with the primary server instance of an Oracle Real Application Clusters (Oracle RAC) database. If, for any reason, there is an Oracle RAC database failover to a secondary server instance, Oracle Essbase will not work.
Perform the following steps in Fusion Middleware Control to scale out the secondary Oracle Essbase Agent:
Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em
).
Expand the Business Intelligence node in the Farm_BIDomain window.
Click coreapplication.
Click Availability, then click Failover.
Click Lock and Edit Configuration to activate the Primary/Secondary Configuration section of the Availability tab.
Specify the Secondary Host/Instance for Essbase Agent.
Ensure the Shared Folder Path is set to ORACLE_BASE
/config/BIShared/Essbase/essbaseserver1
and click Apply.
Click Activate Changes.
Under Manage System, click Restart.
Click Yes in the confirmation dialog.
Note:
Under Potential Single Points of Failure, no problems should be reported for Essbase Agent.
To validate Essbase clustering:
Check the APS (Hyperion Provider Services) test URL:
http://biinternal.mycompany.com:7777/aps/Essbase?Clustername=Essbase_FA_Cluster
The message "Hyperion Provider Services: Hello!" should display.
Run the following command on FINHOST1
:
/u02/local/oracle/config/BIInstance/bin/opmnctl stopproc ias-component=essbaseserver1
Ensure that Essbase starts on FINHOST2
:
/u02/local/oracle/config/BIInstance1/bin/opmnctl status
The status should be init
then Alive
.
Check the APS test URL again:
http://biinternal.mycompany.com:7777/aps/Essbase?Clustername=Essbase_FA_Cluster
You should verify URLs to ensure that the appropriate routing and failover is working from Oracle HTTP Server to bi_cluster
. Perform these steps to verify the URLs:
While bi_server2
is running, stop bi_server1
using the Oracle WebLogic Server Administration Console.
Access the following URLs to verify that routing and failover is functioning properly:
http://WEBHOST1:10621/analytics
http://WEBHOST1:10621/xmlpserver
http://WEBHOST1:10621/ui
(access only available on Microsoft Internet Explorer 7 or 8)
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/workspace
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
Start bi_server1
from the Oracle WebLogic Server Administration Console.
Stop bi_server2
from the Oracle WebLogic Server Administration Console.
Access the following URLs to verify that routing and failover is functioning properly:
http://WEBHOST1:10621/analytics
http://WEBHOST1:10621/xmlpserver
http://WEBHOST1:10621/ui
(access only available on Microsoft Internet Explorer 7 or 8)
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/workspace
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
Start bi_server1
from the Oracle WebLogic ServerAdministration Console.