| Oracle® Fusion Applications Enterprise Deployment Guide 11g Release 1 (11.1.1.5) Part Number E16684-02 |
|
|
View PDF |
| Oracle® Fusion Applications Enterprise Deployment Guide 11g Release 1 (11.1.1.5) Part Number E16684-02 |
|
|
View PDF |
This chapter describes how to scale out the Oracle Business Intelligence domain.
This chapter includes the following topics:
Section 13.1, "Overview of the Oracle Business Intelligence Domain"
Section 13.2, "Prerequisites for Scaling Out the Oracle Business Intelligence Domain"
Section 13.4, "Prerequisites for Scaling Out Oracle Business Intelligence on CRMHOST2"
Section 13.5, "Scaling Out Oracle Business Intelligence Components"
Section 13.6, "Configuring Oracle Essbase Clustering Using the Essbase Failover Automation Tool"
Oracle Fusion Customer Relationship Management Sales and Marketing offerings use following Oracle Business Intelligence components from the Oracle Business Intelligence domain:
Oracle Business Intelligence Analytics
Essbase
Oracle Real-Time Decisions
Oracle Business Intelligence Publisher
Key components of Oracle Fusion Customer Relationship Management, such as Territory (which is the core component of Oracle Fusion Customer Relationship Management), rely on Oracle Business Intelligence Analytics as the source data for planning and optimization.
Oracle Business Intelligence Analytics is the mandatory underlying component for Territory Management, Sales Predictor Engine, and Opportunity Landscape, as they are analytic-centric applications.
Figure 13-1 shows the Oracle Business Intelligence domain within the overall reference enterprise deployment topology for Oracle Fusion Applications.
Before you begin, ensure the following:
Node Manager has been started in the Secure Sockets Layer (SSL) mode by following the instructions in Chapter 6, "Configuring Node Manager"
You are starting with a clean machine if it is the first time it is being used for a scale out
The /etc/hosts file has proper entries. To verify, ping this machine with the fully qualified name of the machine
The user created on CRMHOST2 should the same as the user on CRMHOST1
The directory structure /u01/oracle is mounted to same shared file system as CRMHOST1
The directory structure /u02/local/oracle/config on CRMHOST2 has been created
The initial Oracle Fusion Customer Relationship Management deployment on CRMHOST1 has already been done and verified by provisioning
The Administration Console's Follow Configuration Changes feature has been disabled (to eliminate redirections):
Log into the Administration 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 CRMHOST2.
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 CRMHOST2.
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.
In the Domain Structure window, expand the Services node and then click the Persistent Stores node. The Summary of Persistent Stores page is displayed.
In the Change Center, click Lock & Edit.
Click BipJmsStore and enter a directory that is located in the shared storage. This shared storage is accessible from both CRMHOST1 and CRMHOST2:
ORACLE_BASE/config/domains/CRMHOST1/BIDomain/BipJmsStore
Click Save and then 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 to restart the Oracle Business Intelligence system components:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl restartproc
Make sure that you have performed the steps described in Section 14.1, "Enabling Virtual IPs on CRMHOST1 and CRMHOST2" 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 column of the table. The Setting page for bi_server1 is displayed.
Set the Listen Address to BIVH1.
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, as follows:
$ 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_servern Managed Servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:
On WEBHOST1 and WEBHOST2, update the WebLogicCluster parameter in the ORACLE_BASE/config/CommonDomain_webtiern/config/OHS/ohs1/moduleconf/FusionVirtualHost_bi.conf file to contain a cluster list of Virtual host:port entries.
For example,
<LocationMatch ^/analytics/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch>
On WEBHOST1 and WEBOST2, add the following context roots to the ORACLE_BASE/config/CommonDomain_webtiern/config/OHS/ohs1/moduleconf/FusionVirtualHost_bi.conf file:
RedirectMatch 301 ^/biofficeclient$ /biofficeclient/ RedirectMatch 301 ^/bimiddleware$ /bimiddleware/ RedirectMatch 301 ^/rtis$ /rtis/ RedirectMatch 301 ^/bisearch$ /bisearch/ <LocationMatch ^/biofficeclient/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch> <LocationMatch ^/bimiddleware/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch> <LocationMatch ^/rtis/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch> <LocationMatch ^/bisearch/> SetHandler weblogic-handler WebLogicCluster BIVH1:10217,BIVH2:10217 </LocationMatch>
Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2, as follows:
WEBHOST1> ORACLE_BASE/config/CommonDomain_webtier/bin/opmnctl restartproc ias-component=ohs1 WEBHOST2> ORACLE_BASE/config/CommonDomain_webtier1/bin/opmnctl restartproc ias-component=ohs1
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 WebLogic Server plug-in, see Oracle Fusion Middleware Using Web Server 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 CRMHOST1 and CRMHOST2, 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 Oracle Fusion Middleware Release Notes for any additional installation and deployment considerations before starting the setup process.This section includes the following topics:
Section 13.5.4, "Configuring Secondary Instances of Singleton System Components"
Section 13.5.7, "Configuring a Default Persistence Store for Transaction Recovery"
Section 13.5.8, "Starting and Validating Oracle Business Intelligence on CRMHOST2"
Section 13.5.9, "Validating Access Through Oracle HTTP Server"
Section 13.5.10, "Configuring Node Manager for the Managed Servers"
Section 13.5.11, "Configuring Server Migration for the Managed Servers"
Do the following to scale out the Oracle Business Intelligence system:
Change directory to the location of the Configuration Assistant:
CRMHOST2> ORACLE_BASE/products/fusionapps/bi/bin
Start the Oracle Business Intelligence Configuration Assistant:
CRMHOST2> ./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 or Scale out BI System screen, select Scale Out BI System and enter the following:
Host Name: CRMHOST1
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/CRMHOST1 /BIDomain
Applications Home: /u02/local/oracle/config/applications/CRMHOST1/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.
Do the following:
Shutdown the default node manager.
Start the Node Manager in SSL mode on CRMHOST2:
CRMHOST2> cd ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager/ CRMHOST2 CRMHOST2> ./startNodeManagerWrapper.sh
Update the Node Manager for the CRMHOST2 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 CRMHOST2.
In the window that opens, click the Node Manager tab and set the following attributes:
– Type - SSL
– Listen Address - <CRMHOST2>
– 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 to 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.
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 CRMHOST2 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 CRMHOST1 BIInstance Oracle instance.
Port Range To on both instances must be increased from 10214 to 10215.
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 13.5.4, "Configuring Secondary Instances of Singleton System Components."
The Oracle BI Cluster Controllers and Oracle BI Scheduler are singleton components that operate in active/passive mode. Configure a secondary instance of these components so that they are distributed for high availability.
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 Capacity Management, then click Availability.
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.
Under Potential Single Points of Failure, it should report No problems - all components have a backup.
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.
This section explains how to configure the bi_server2 Managed Server, and contains the following topics:
Section 13.5.5.1, "Setting the Listen Address for the bi_server2 Managed Server"
Section 13.5.5.2, "Configuring Custom Identity and Custom Trust for the bi_server2 Managed Server"
Section 13.5.5.3, "Disabling Host Name Verification for the bi_server2 Managed Server"
Make sure that you have performed the steps described in Section 14.1, "Enabling Virtual IPs on CRMHOST1 and CRMHOST2" 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 column of 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.
Do the following:
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 column of 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/products/fusionapps/wlserver_10.3/server/lib/CRMHOST2_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 6.2, "Creating the Identity Keystore on CRMHOST2."
Under Trust, do the following:
– Change the Custom Identity Keystore entry to point to the ORACLE_BASE/products/fusionapps/wlserver_10.3/server/lib/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 6.2, "Creating the Identity Keystore on CRMHOST2."
– 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 CRMHOST2_fusion.
– Enter and confirm the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 6.2, "Creating the Identity Keystore on CRMHOST2."
– 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/
products/fusionapps/wlserver_10.3/server/lib/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 6, "Configuring Node Manager"). 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 once the enterprise deployment topology configuration is complete as described in Chapter 6, "Configuring Node Manager."
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 column of 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.
Restart bi_server2.
Restart the BI System Components:
$ 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 13.5.6.1, "Additional Configuration Tasks for Oracle BI Scheduler"
Section 13.5.6.2, "Additional Configuration Tasks for Oracle Real-Time Decisions"
Section 13.5.6.3, "Additional Configuration Tasks for Oracle BI Publisher"
Section 13.5.6.4, "Additional Configuration Tasks for Oracle BI for Microsoft Office"
Section 13.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 .
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 CRMHOST1: /u02/local/oracle/config/BIInstance/config/OracleBISchedulerComponent/coreapplication_obisch1
On CRMHOST2: /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 CRMHOST1:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopproc ias-component=coreapplication_obisch1 $ ./opmnctl startproc ias-component=coreapplication_obisch1
On CRMHOST2:
$ 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 13.5.6.2.1, "Configuring Oracle Real-Time Decisions Clustering Properties"
Section 13.5.6.2.2, "Adding System Properties to the Server Start Tab"
Perform these steps in Fusion Middleware Control to set up cluster-specific configuration properties for 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.
Click 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 13-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.
In the Administration Console, choose Environment > Servers > bi_server<1,2> > Server Start > Arguments and then add these three properties:
-Drtd.clusterRegistryJobIntervalMs=12000 -Drtd.clusterDepartureThresholdMs=50000 -Drtd.clusterDepartureThreshold2Ms=50000
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 this is the case, do the following:
In Fusion Middleware Control, expand the WebLogic Domain node in the left pane. Then, right-click bifoundation_domain and select System MBean Browser.
Locate the BatchManager MBean, under either Application Defined MBeans > OracleRTD > Server:bi_server1 > Server or under Application Defined MBeans > OracleRTD > Server:bi_server2> Server.
It should be in one of these locations, but not both.
Locate the corresponding MBean attribute BatchManagerEnabled under SDPropertyManager > Misc. For example, if the BatchManager MBean is located in bi_server1, then select Application Defined MBeans > OracleRTD > Server:bi_server1 > SDPropertyManager > Misc : BatchManagerEnabled.
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.
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.
After the application has stopped, click Start.
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://CRMHOST1:10212/PrimaryCCS=CRMHOST1;PrimaryCCSPort=10212; SecondaryCCS=CRMHOST2;SecondaryCCSPort=10212;
Deselect Use System User and specify administrator credentials for Username and Password (for example, FAadmin).
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 CRMHOST2:
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 CRMHOST1 and CRMHOST2:
ORACLE_BASE/config/domains/CRMHOST1/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 Finish and then Activate Changes.
This section includes the following topics:
Section 13.5.6.4.1, "Configuring Oracle BI for Microsoft Office Properties"
Section 13.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 is displayed, as shown in Figure 13-2.
Go to the Oracle BI Enterprise Edition Office Server directory. For example:
/u02/local/config/domains/CRMHOST1/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.
On both CRMHOST1 and CRMHOST2, open bioffice.xml for editing and modify the BI Office properties shown in Table 13-2.
Table 13-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.
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 13-3 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 13-4.
Log in as an Administrator (for example, weblogic) and validate that you can access the Oracle BI Task Pane, as shown in Figure 13-5.
There are additional configuration tasks to perform for Oracle Financial Reporting. Do the following on CRMHOST1 and CRMHOST2:
Update the VARIABLE_VALUE_LIMIT from 30720 to 3072000 in the NQSConfig.INI file. For example,
VARIABLE_VALUE_LIMIT = 3072000;
On CRMHOST1, this file is located in /u02/local/oracle/config/BIInstance/config/OracleBIServerComponent/coreapplication_obis1.
On CRMHOST2, 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:
$ cd /u02/local/oracle/config/BIInstancen/bin
$ ./ompnctl 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 the name of the server (represented as a hyperlink) in the column of the table. The Settings page for the selected server is displayed, and defaults to the Configuration tab.
Open the Services tab.
In the Default Store section of the page, enter the path to the folder where the default persistent stores will store its data files. For example:
CRMHOST1> ORACLE_BASE/config/domains/CRMHOST1/BIDomain/tlogs
Click Save.
Click Activate Changes.
Restart 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.
Restart the bi_server1 and bi_server2 servers.
Restart the Oracle Business Intelligence system components:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./ompnctl 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. Bothbi_server1 and bi_server2 must be able to access this directory.This section includes the following topics:
Section 13.5.8.2, "Starting the Oracle Business Intelligence System Components"
Section 13.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.
Choose 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
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
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
http://WEBHOST1:10621/workspace
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 6, "Configuring Node Manager" for further details. The procedures in that chapter must be performed twice using the information provided in Table 13-3.
Server Migration is required for proper failover of the Oracle BI Publisher components in the event of failure in any of the CRMHOST1 and CRMHOST2 nodes. For more information, see Chapter 16, "Configuring Server Migration."
This section describes how to set up Essbase clustering in high-availability environments using the essfoconfig.sh failover automation tool.
Do the following before you run the failover automation tool:
Make sure the adminHost property in /u02/local/oracle/config/BIInstancen/config/OPMN/opmn/instance.properties file reflects the BIADMINVH hostname.
Create a new wallet with a self-signed certificate for setting up Oracle Process Manager and Notification Server clustering with SSL enabled:
On CRMHOST1 and CRMHOST2, rename the original wallets. For example:
For CRMHOST1:
$ mv /u02/local/oracle/config/BIInstance/config/OPMN/opmn/wallet/ /u02/ local/oracle/config/BIInstance/config/OPMN/opmn/wallet_orig
For CRMHOST2:
$ mv /u02/local/oracle/config/BIInstance1/config/OPMN/opmn/wallet/ /u02/ local/oracle/config/BIInstance1/config/OPMN/opmn/wallet_orig
Ensure that the /u02/local/oracle/config/BIInstancen/config/OPMN/opmn/opmn.xml file has ssl enabled="true" on each node.
Stop Oracle Process Manager and Notification Server:
For CRMHOST1:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopall
For CRMHOST2:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl stopall
On CRMHOST1, do the following:
– Create an Oracle wallet:
$ setenv JAVA_HOME ORACLE_BASE/products/fusionapps/jdk6 $ cd ORACLE_BASE/products/fusionapps/oracle_common/bin $ ./orapki wallet create -wallet wallet location
For example
$ ./orapki wallet create -wallet /u02/local/oracle/config/BIInstance/
config/OPMN/opmn/wallet
– Enter the wallet password.
– Add a root certificate to an Oracle wallet:
$ ./orapki wallet add -wallet wallet location -dn certificate_dn -keysize 512|1024|2048 -self_signed -validity number of days
For example:
$ ./orapki wallet add -wallet /u02/local/oracle/config/BIInstance/config/OPMN/opmn/wallet -dn 'CN=\"Self-Signed Certificate for cluster\",OU=OAS,O=ORACLE,L=REDWOODSHORES,ST=CA,C=US' -keysize 1024 -self_signed -validity 3650
– Enter the wallet password.
– Create an Oracle wallet with auto-login enabled:
$ ./orapki wallet create -wallet wallet location -auto_login
For example:
$ ./orapki wallet create -wallet /u02/local/oracle/config/BIInstance/config/OPMN/opmn/wallet -auto_login
– Enter the wallet password.
Performing the tasks listed in Step d creates two files in the wallet directory: cwallet.sso and ewallet.p12.
Copy the new wallet directory to CRMHOST2.
On each node, push the wallet to the AdminServer domain using the ./opmnctl updateinstanceregistration command:
For CRMHOST1:
Update the adminUsername entry in the /u02/local/oracle/config/BIInstance/config/OPMN/opmn/instance.properties file to correctly reflect the Weblogic Administrator. For example, update:
adminUsername=FUSION_APPS_PROV_PATCH_APPID
to
adminUsername=FAadmin
$ cd /u02/local/oracle/config/BIInstance/bin
$ ./opmnctl updateinstanceregistration
For CRMHOST2:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl updateinstanceregistration
This command will ask for an Oracle Weblogic Server Administrator password. The updateinstanceregistration command updates information registered on the Administration Server for the Oracle instances. Specifically, the updateinstanceregistration command updates the registered Oracle Process Manager and Notification Server remote port, remote host, and wallet from the current Oracle Process Manager and Notification Server settings.
Restart the Oracle Process Manager and Notification Server:
For CRMHOST1:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl startall
For CRMHOST2:
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl startall
Note:
For information on deploying Essbase in SSL mode, see "SSL for Essbase" in Oracle Enterprise Performance Management System Security Administration Guide.Create the Essbase System Component on CRMHOST2. Refer to the ORACLE_BASE/products/fusionapps/bi/bifoundation/admin/provisioning/readme.txt file for changes to the opmnctl createcomponent parameters for Essbase.
$ cd /u02/local/oracle/config/BIInstance1/bin $ ./opmnctl createcomponent -componentName essbaseserver1 -componentType Essbase -appServerDomainHomeLocation AdminServer Domain Home -epmClusterName EssbaseCluster Name -jpsConfigSetup false -epmEssbaseAgentPort 10215 -epmEssbaseServerStartPort 10301 -epmEssbaseServerEndPort 10600
Example 13-1 Sample Output
$ ./opmnctl createcomponent -componentName essbaseserver1 -componentType Essbase -appServerDomainHomeLocation ORACLE_BASE/config/domains/CRMHOST1/BIDomain -epmClusterName Essbase_HA-1 -jpsConfigSetup false -epmEssbaseAgentPort 10215 -epmEssbaseServerStartPort 10301 -epmEssbaseServerEndPort 10600 Command requires login to weblogic admin server (BIADMINVH.MYCOMPANY.COM): Creating empty component directories...Done Provisioning Essbase files for essbaseserver1 Registry essbase seeding started Cluster name: Essbase_HA-1 Getting registry instance... Registry essbase seeding complete Creating new registry file at: /u02/local/oracle/config/BIInstance1/Essbase/ essbaseserver1/bin/essbase.cfg Creating Parent directories Setting ESS_CSS_JVM_OPTION3 value to :ORACLE_BASE/instance/domains/ ORACLE_BASE/config/domains/CRMHOST1/BIDomain/config/fmwconfig/jps-config-jse.xml Setting DOMAIN_HOME value to :ORACLE_BASE/config/domains/CRMHOST1/BIDomain Setting agentPort value to :10215 Setting serverPortRange value to :10301-10600 Connecting to JMX URL: service:jmx:t3://BIADMINVH:10201/jndi/weblogic.management.mbeanservers.domainruntime Registering essbaseserver1 component Invoking opmn reload...Done Command succeeded.
Make sure to update the arborPATH property prior to running the Essbase failover automation tool. Do the following from the /u02/local/oracle/config/BIInstance/config/foundation/11.1.2.0 directory on CRMHOST1:
Run the following to determine the ID for NAME - Essbase_FA_Cluster:
CRMHOST1> $ ./epmsys_registry.sh view ESSBASE_PRODUCT
Example output is:
Child 1 NAME - Essbase_FA_Cluster ID - 4a6fdb8aff5464dbS3469229f131f91e8ef2S7ff5 TYPE - CLUSTER
Using the Essbase_FA_Cluster ID from the example in Step a, run the following to determine the ID for Name - essbaseserver1:
CRMHOST1> $ ./epmsys_registry.sh view \
#4a6fdb8aff5464dbS3469229f131f91e8ef2S7ff5
Example output is:
Child 1 NAME - essbaseserver1 ID - 4a6fdb8aff5464dbS3469229f131f91e8ef2S7fef TYPE - ESSBASE_SERVER
Using the essbaseserver1 ID from the example in Step b, run the following to view the arborPATH value:
CRMHOST1> $ ./epmsys_registry.sh view \
#4a6fdb8aff5464dbS3469229f131f91e8ef2S7fef
Example output is:
arborPath = ORACLE_BASE/config/BIShared/Essbase/essbaseserver1
Run the following to update the arborPath value to arborPath = ORACLE_BASE/config/BIShared/Essbase/essbaseserver1.bak:
CRMHOST1> $ ./epmsys_registry.sh updateproperty \#4a6fdb8aff5464dbS3469229f131f91e8ef2S7fef/@arborPath ORACLE_BASE/ config/BIShared/Essbase/essbaseserver1.bak
Run the following to view the new arborPath property value:
$ ./epmsys_registry.sh view \ #4a6fdb8aff5464dbS3469229f131f91e8ef2S7fef
Do the following to run the Essbase failover automation tool:
Grant execute on /u02/local/oracle/config/BIInstancen /bin/essbase_ha/essfoconfig.sh script on all nodes.
Update the SHARED_FOLDER (ORACLE_BASE/config/BIShared/Essbase/essbaseserver1) variable in the /u02/local/oracle/config/BIInstancen/bin/essbase_ha/essfoenv.properties file on each node.
From CRMHOST1, stop the Essbase System Component:
$ cd /u02/local/oracle/config/BIInstance/bin $ ./opmnctl stopproc ias-component=essbaseserver1
Run essfoconfig.sh with pushprp 1 on CRMHOST1 and pushprp 2 on CRMHOST2:
CRMHOST1> cd /u02/local/oracle/config/BIInstance/bin/essbase_ha/ CRMHOST1> ./essfoconfig.sh pushprp 1 CRMHOST1> ./essfoconfig.sh pushprp 1
Note:
You must run thepushprp command twice: First to copy the EssFOConfig.properties file to the SHARED_FOLDER, and second to update the EssFOConfig.properties file with CRMHOST1-specific values.CRMHOST2> cd /u02/local/oracle/config/BIInstance1/bin/essbase_ha/ CRMHOST2> ./essfoconfig.sh pushprp 2
Update the following properties in the ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/EssFOConfig.properties file:
SYSTEM_HOST=CRMHOST1 SYSTEM_NODE1=Essbase_FA_Cluster SYSTEM_HOST1=CRMHOST1 SYSTEM_HOST2=CRMHOST2 SYSTEM_USERNAME=WebLogic_Administrator
Run essfoconfig.sh with the check option on CRMHOST1:
/u02/local/oracle/config/BIInstance/bin/essbase_ha/essfoconfig.sh check
Example 13-2 Sample Output
./essfoconfig.sh check Fri Dec 10 11:23:59 PST 2010 Essbase Cluster configuration utility. Active user properties file: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/ EssFOConfig.properties Command: check Environment: ORACLE_HOME= ORACLE_BASE/products/fusionapps/bi ORACLE_INSTANCE= /u02/local/oracle/config/BIInstance JAVA_HOME= ORACLE_BASE/products/fusionapps/jdk6 SHARED_FOLDER= ORACLE_BASE/config/BIShared/Essbase REGUTIL=/u02/local/oracle/config/BIInstance/config/foundation/11.1.2.0/empsys_ registry.sh Fetch registry metadata Extract the Essbase ID from registry metadata The Essbase GUID is: 62d5513d9665ae4353f3a57412cbdf8a90f7fb1 Check if Essbase instance is running.
Run essfoconfig.sh with the create option on CRMHOST1:
/u02/local/oracle/config/BIInstance/bin/essbase_ha/essfoconfig.sh create
Example 13-3 Sample Output
$ ./essfoconfig.sh create
Fri Dec 10 11:25:50 PST 2010
Essbase Cluster configuration utility.
Active user properties file: ORACLE_BASE/config/BIShared/Essbase/
EssFOConfig.properties
Command: create
Fetch registry metadata
Extract the Essbase ID from registry metadata
The Essbase GUID is: 62d5513d9665ae4353f3a57412cbdf8a90f7fb1
Add cluster info using template
Validate the pre-existence of Cluster from registry metadata
Fetch registry metadata for a specific ESSBASE_PRODUCT
Extract the Cluster ID
The Cluster GUID is:
Replace properties in template
Replace Cluster GUID in template
The Component Hierarchy has been created.
Extract the Cluster ID from registry metadata
Fetch registry metadata for a specific ESSBASE_PRODUCT
Extract the Cluster ID
The Cluster GUID is: 62d5513d9665ae43118450de12cd1bf46588000
Fetch Cluster using GUID from registry metadata
Add cluster node1 info using template
Replace properties in template
Replace Cluster GUID in template
The Component Hierarchy has been created.
Fetch CLUSTER ID object from registry metadata
Extract Instance GUID (1) for the cluster
The Cluster Instance 1 GUID is: 62d5513d9665ae43390672fb12cd1bf7b358000
Add cluster node2 info using template
Replace properties in template
Replace Cluster GUID in template
The Component Hierarchy has been created.
Fetch CLUSTER ID object from registry metadata
Extract Instance GUID (2) for the cluster
The Cluster Instance 2 GUID is: 62d5513d9665ae431e64a4c512cd1bf9ecd8000
Essbase Cluster configuration over.
Run essfoconfig.sh with the dump option on CRMHOST1:
/u02/local/oracle/config/BIInstance/bin/essbase_ha/essfoconfig.sh dump
Example 13-4 Sample Output
$ ./essfoconfig.sh dump Fri Dec 10 11:28:13 PST 2010 Essbase Cluster configuration utility. Active user properties file: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/ EssFOConfig.properties Command: dump Important environment info: User properties file name: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/ EssFOConfig.properties On successful completion, the following registry metadata files will be created: ep.md - Contains all ESSBASE_PRODUCT registry entries. ep1.md - Contains registry entries for specific ESSBASE_PRODUCT of interest. cl.md - Contains registry entries for CLUSTER of interest. Found user properties file name: ORACLE_BASE/config/BIShared/Essbase/ essbaseserver1/EssFOConfig.properties Fetch registry metadata Extract the Essbase ID from registry metadata The Essbase GUID is: 62d5513d9665ae4353f3a57412cbdf8a90f7fb1 Extract the Cluster ID from registry metadata Fetch registry metadata for a specific ESSBASE_PRODUCT Extract the Cluster ID The Cluster GUID is: 62d5513d9665ae43118450de12cd1bf46588000 Fetch Cluster using GUID from registry metadata Fetch CLUSTER ID object from registry metadata Extract Instance GUID (1) for the cluster The Cluster Instance 1 GUID is: 62d5513d9665ae43390672fb12cd1bf7b358000 Fetch CLUSTER ID object from registry metadata Extract Instance GUID (2) for the cluster The Cluster Instance 2 GUID is: 62d5513d9665ae431e64a4c512cd1bf9ecd8000
Run essfoconfig.sh with the esscfg option on CRMHOST1:
/u02/local/oracle/config/BIInstance/bin/essbase_ha/essfoconfig.sh esscfg
Example 13-5 Sample Output
$ ./essfoconfig.sh esscfg Fri Dec 10 11:29:31 PST 2010 Essbase Cluster configuration utility. Active user properties file: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/ EssFOConfig.properties Command: esscfg Updating file: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/bin/essbase.cfg Property FailOverMode not defined in ORACLE_BASE/config/BIShared/Essbase/ essbaseserver1/bin/essbase.cfg Adding it now...
Run essfoconfig.sh with the opmn 1 option on CRMHOST1:
/u02/local/oracle/config/BIInstance/bin/essbase_ha/essfoconfig.sh opmn 1
This command generates a modified opmn.xml file, opmn_EssHA.xml, under the /u02/local/oracle/config/BIInstance/config/OPMN/opmn directory.
Example 13-6 Sample Output
$ ./essfoconfig.sh opmn 1
Fri Dec 10 11:30:31 PST 2010
Essbase Cluster configuration utility.
Active user properties file: ORACLE_BASE/config/BIShared/Essbase/essbaseserver1/
EssFOConfig.properties
Command: opmn
Buildfile: essopmn.xml
_enable-ess-opmn:
[copy] Copying 1 file to /u01/app/oracle/instances/BIInstance/bin
[xlst] Processing /u01/app/oracle/instances/BIInstance/config/OPMN/opmn/opmn_
EssHA.xml
[xslt] Loading stylesheet /u01/app/oracle/instances/BIInstance/bin/
essopmn.xslt
[xslt] : Warning!
[xslt] FOUND: Essbase ias-component with child 'Essbase'
[xslt] id:essbaseserver1
[xslt] module-id:
[xslt] Since entry exists in opmn.xml ...update it
[xslt] par-id:instance1
[xslt] ancst-id:essbaseserver1
[xslt] self-id:essbaseserver1
[xslt] child-id:essbaseserver1
[xslt] ARG:essclu1
[xslt] : Warning!
[xslt] FOUND: Essbase module with
[xslt] id:Essbase
[xslt] Since entry exists in opmn.xml ...change the name
[xslt] par-id:essbaseserver1
[xslt] child-id:Essbase
[xslt] : Warning!
[xslt] FOUND: Essbase ARBORPATH property with
[xslt] id:ARBORPATH
[xslt] value:/u02/local/oracle/config/BIInstance/Essbase/
$COMPONENT_NAME
[xslt] : Warning!
[xslt] FOUND: Essbase process-set AGENT property with
[xslt] id:AGENT
[xslt] numprocs:1
BUILD SUCCESSFUL
Total time: 1 second
Add a <topology> tag under the <notification-server> tag to the /u02/local/oracle/config/BIInstance/config/OPMN/opmn/opmn_EssHA.xml file, as shown in Example 13-7. (The lines that you must verify and add are shown in bold.)
Example 13-7 opmn_EssHA.xml File
<notification-server interface="any">
<port local="10203" remote="10204"/>
<ssl enabled="true" wallet-file="/u02/local/oracle/config/BIInstance/
config/OPMN/opmn/wallet"/>
<topology>
<nodes list="CRMHOST1:10204,CRMHOST2:10204"/>
</topology>
</notification-server>
In the nodes list, enter the primary and secondary nodes and remote port numbers.
Save the original /u02/local/oracle/config/BIInstance/config/OPMN/opmn/opmn.xml file and copy the opmn_EssHA.xml file to the /u02/local/oracle/config/BIInstance/config/OPMN/opmn/opmn.xml file.
Repeat Steps 10 through 12 on CRMHOST2, with the following command replacing the essfoconfig.sh command specified in Step 10:
/u02/local/oracle/config/BIInstance1/bin/essbase_ha/essfoconfig.sh opmn 2
Shut down all opmn components on CRMHOST1 and CRMHOST2:
/u02/local/oracle/config/BIInstancen/bin/opmnctl stopall
On CRMHOST1, n can be BIInstance, and on CRMHOST2 it can be BIInstance1.
Start all opmn components on CRMHOST1 and CRMHOST2:
/u02/local/oracle/config/BIInstancen/bin/opmnctl startall
On CRMHOST1, n can be BIInstance, and on CRMHOST2 it can be BIInstance1.
To shut down Essbase system components cluster-wide:
/u02/local/oracle/config/BIInstance/bin/opmnctl stopproc ias-component=essclu1 process-type=Essbase
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
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
http://WEBHOST1:10621/hr
http://WEBHOST1:10621/workspace
http://WEBHOST1:10621/calcmgr/index.htm
http://WEBHOST1:10621/aps/Test
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|