Skip Headers
Oracle® Fusion Applications Customer Relationship Management Enterprise Deployment Guide
11g Release 1 (11.1.3)
Part Number E16684-09
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

14 Scaling Out the Oracle Business Intelligence Domain

This chapter describes how to scale out the Oracle Business Intelligence domain.

This chapter includes the following topics:

14.1 Overview of the Oracle Business Intelligence Domain

Oracle Fusion Customer Relationship Management Sales and Marketing offerings use following Oracle Business Intelligence components from the Oracle Business Intelligence domain:

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.

Oracle Fusion Customer Relationship Management Sales and Marketing offerings use following Oracle Business Intelligence components from the Oracle Business Intelligence domain:

Figure 2-9 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.

14.2 Prerequisites for Scaling Out the Oracle Business Intelligence Domain

Before you begin, ensure the following:

14.3 Starting the Default Node Manager

To start the default Node Manager:

  1. Stop any Node Manager running on CRMHOST2 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 Customer Relationship Managementand the Oracle Fusion Applications enterprise deployment.

  2. Change directory to ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager and edit the nodemanager.properties file with the following:

    SecureListener=false

  3. Change directory to ORACLE_BASE/products/fusionapps/oracle_common/common/bin and run the following script:

    ./setNMProps.sh

  4. Change directory to ORACLE_BASE/products/fusionapps/wlserver_10.3/server/bin and run the following script:

    ./startNodeManager.sh

    Node Manager starts on CRMHOST2.

Note:

Steps 2 through 4 will enable Node Manager on CRMHOST2 and the Administrator Console to communicate on Plain Socket.

14.4 Prerequisites for Scaling Out Oracle Business Intelligence on CRMHOST2

Prerequisites include the following:

14.4.1 Configuring JMS for Oracle BI Publisher

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.

  1. Log in to the Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Domain Structure window, expand the Services node and then click the Persistent Stores node. The Summary of Persistent Stores page is displayed.

  3. In the Change Center, click Lock & Edit.

  4. 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

  5. Click Save and then click Activate Changes.

    The changes will not take effect until the Managed Server is restarted.

  6. Do the following:

    1. Ensure that Node Manager is up and running.

    2. On the Summary of Servers page, select the Control tab.

    3. Select bi_server1 in the table and then click Shutdown.

    4. After the server has shut down, select bi_server1 in the table and then click Start.

  7. Run the following commands to restart the Oracle Business Intelligence system components:

    $ cd /u02/local/oracle/config/BIInstance/bin 
$ ./opmnctl stopall
$ ./opmnctl startall

14.4.2 Setting the Listen Address for bi_server1 Managed Server

Make sure that you have performed the steps described in Section 15.1, "Enabling Virtual IPs on CRMHOST1 and CRMHOST2" before setting the bi_server1 listen address.

To set the listen address for the Managed Server:

  1. Log in to the Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Change Center, click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page is displayed.

  5. Select bi_server1 in the table. The Settings page for bi_server1 is displayed.

  6. Set the Listen Address to BIVH1.

  7. Click Save.

  8. Click Activate Changes.

  9. The changes will not take effect until the bi_server1 Managed Server is restarted (ensure that Node Manager is up and running):

    1. On the Summary of Servers page, select the Control tab.

    2. Select bi_server1 in the table and then click Shutdown.

    3. After the server has shut down, select bi_server1 in the table and then click Start.

  10. Restart the Oracle Business Intelligence system components, as follows:

    $ cd /u02/local/oracle/config/BIInstance/bin 
$ ./opmnctl stopall
$ ./opmnctl startll

14.4.3 Updating the FusionVirtualHost_bi.conf Configuration File

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:

  1. 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.

    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>

  2. On WEBHOST1 and WEBOST2, add the following context roots to the ORACLE_BASE/config/CommonDomain_webtiern/config/OHS/ohs1/moduleconf/FusionVirtualHost_bi.conf file:

    Example 14-1 # Internal Virtual Host Section

    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>

    Example 14-2 # External Virtual Host Section

    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
WLProxySSL ON
WLProxySSLPassThrough ON
RewriteEngine ON
RewriteOptions inherit
</LocationMatch>

<LocationMatch ^/bimiddleware/>
SetHandler weblogic-handler
WebLogicCluster BIVH1:10217,BIVH2:10217
WLProxySSL ON
WLProxySSLPassThrough ON
RewriteEngine ON
RewriteOptions inherit
</LocationMatch>

<LocationMatch ^/rtis/>
SetHandler weblogic-handler
WebLogicCluster BIVH1:10217,BIVH2:10217
WLProxySSL ON
WLProxySSLPassThrough ON
RewriteEngine ON
RewriteOptions inherit
</LocationMatch>

<LocationMatch ^/bisearch/>
SetHandler weblogic-handler
WebLogicCluster BIVH1:10217,BIVH2:10217
WLProxySSL ON
WLProxySSLPassThrough ON
RewriteEngine ON
RewriteOptions inherit
</LocationMatch>

  3. 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.

14.5 Scaling Out Oracle Business Intelligence Components

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 the Oracle Fusion Middleware release notes for any additional installation and deployment considerations before starting the setup process.

This section includes the following topics:

14.5.1 Scaling Out the Oracle Business Intelligence System on CRMHOST2

To scale out the Oracle Business Intelligence system:

  1. Ensure that the bi_server1 server is running.

  2. In the ORACLE_BASE/products/fusionapps/registry.xml file, change

    <component name="WebLogic Server" version="10.3.6.0"
InstallDir="ORACLE_BASE/products/fusionapps/wlserver_10.3">

    to

    <component name="WebLogic Server" version="Temporary"
InstallDir="ORACLE_BASE/products/fusionapps/wlserver_10.3">

  3. Change directory to the location of the Configuration Assistant:

    CRMHOST2> ORACLE_BASE/products/fusionapps/bi/bin

  4. Start the Oracle Business Intelligence Configuration Assistant:

    CRMHOST2> ./config.sh

  5. In the Welcome screen, click Next.

  6. In the Prerequisite Checks screen, verify that all checks complete successfully, and then click Next.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. In the Summary screen, click Configure.

  12. In the Configuration Progress screen, verify that all the Configuration Tools have completed successfully and click Next.

  13. In the Complete screen, click Finish.

14.5.2 Starting Node Manager in SSL Mode

To start Node Manager in SSL mode:

  1. Stop the default Node Manager running on CRMHOST2 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 Customer Relationship Managementand the Oracle Fusion Applications enterprise deployment.

  2. Start Node Manager in SSL mode on CRMHOST2:

    CRMHOST2> cd ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager/CRMHOST2

CRMHOST2> ./startNodeManagerWrapper.sh

  3. Update the Node Manager for the CRMHOST2 machine using the Oracle WebLogic Server Console by doing the following:

    1. Log in to the Administration Server: http://biinternal.mycompany.com:7777/console.

    2. Navigate to BIDomain> Environment > Machines.

    3. In the left-hand pane, click Lock & Edit.

    4. In the right-hand pane, click CRMHOST2.

    5. In the window that opens, click the Node Manager tab and set the following attributes:

      – Type - SSL

      – Listen Address - <CRMHOST2>

      – Listen Port - 5556

  4. Click Save and then Activate Changes.

    The changes will not take effect until the bi_server2 Managed Server is restarted.

  5. Do the following to restart the bi_server2 Managed Server:

    1. On the Summary of Servers page, select the Control tab.

    2. Select bi_server2 in the table and then click Shutdown.

    3. After the server has shut down, select bi_server2 in the table and then click Start.

14.5.3 Scaling Out the System Components

To scale out the system components, do the following in Oracle Enterprise Manager Fusion Middleware Control:

  1. Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em).

  2. Expand the Business Intelligence node in the Farm_BIDomain window.

  3. Click coreapplication.

  4. Click Capacity Management, then click Scalability.

  5. Click Lock and Edit Configuration.

  6. For the CRMHOST2 BIInstance1 Oracle instance, increment the Oracle Business Intelligence components by 1:

    • BI Servers

    • Presentation Servers

    • JavaHosts

  7. 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.

  8. Click Apply.

  9. Click Activate Changes.

You do not need to restart at this point, because you will perform a restart after completing the steps in Section 14.5.4, "Configuring Secondary Instances of Singleton System Components."

14.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:

  1. Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em).

  2. Expand the Business Intelligence node in the Farm_BIDomain window.

  3. Click coreapplication.

  4. Click Availability, then click Failover.

  5. Click Lock and Edit Configuration to activate the Primary/Secondary Configuration section of the Availability tab.

  6. Specify the Secondary Host/Instance for BI Scheduler and BI Cluster Controller.

  7. Click Apply.

    Under Potential Single Points of Failure, no problem should be reported for BI Scheduler and BI Cluster Controller.

  8. Click Activate Changes.

  9. Click Restart to apply recent changes.

  10. From Manage System, click Restart.

  11. Click Yes when prompted to confirm that you want to restart all Business Intelligence components.

14.5.5 Configuring the bi_server2 Managed Server

This section explains how to configure the bi_server2 Managed Server, and contains the following topics:

14.5.5.1 Setting the Listen Address for the bi_server2 Managed Server

Make sure that you have performed the steps described in Section 15.1, "Enabling Virtual IPs on CRMHOST1 and CRMHOST2" before setting the bi_server2 listen address.

To set the listen address for the Managed Server:

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Change Center, click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page is displayed.

  5. Select bi_server2 in the table. The settings page for bi_server2 is displayed.

  6. Set the Listen Address to BIVH2.

  7. Click Save.

  8. Click Activate Changes.

    The changes will not take effect until the Managed Server is restarted.

  9. Do the following:

    1. Ensure that Node Manager is up and running.

    2. On the Summary of Servers page, select the Control tab.

    3. Select bi_server2 in the table and then click Shutdown.

    4. After the server has shut down, select bi_server2 in the table and then click Start.

14.5.5.2 Configuring Custom Identity and Custom Trust for the bi_server2 Managed Server

To configure custom identity and custom trust:

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Change Center, click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers.

    The Summary of Servers page displays.

  5. Select bi_server2 in the table. The Settings page for bi_server2 displays.

  6. Click Keystores, and then do the following:

    1. Click Change next to Demo Identity and Demo Trust.

    2. Select Custom Identity and Custom Trust from the Keystores dropdown list and click Save.

    3. 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 7.2, "Creating the Identity Keystore on CRMHOST2."

    4. 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 7.2, "Creating the Identity Keystore on CRMHOST2."

      – Click Save.

  7. Click SSL, and then do the following:

    1. Ensure that Identity and Trust Locations is set to Keystores.

    2. 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 7.2, "Creating the Identity Keystore on CRMHOST2."

      – Click Save.

  8. Click Activate Changes.

  9. 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}"

14.5.5.3 Disabling Host Name Verification for the bi_server2 Managed Server

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 once 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:

  1. Log in to Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

  2. Click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page is displayed.

  5. Select bi_server2 in the table. The settings page for the server is displayed.

  6. Click the SSL tab.

  7. Expand the Advanced section of the page.

  8. Set Host Name Verification to None.

  9. Click Save.

  10. Click Activate Changes.

  11. The change will not take effect until the bi_server2 Managed Server is restarted (make sure that Node Manager is up and running):

    1. In the Summary of Servers screen, select the Control tab.

    2. Select bi_server2 in the table and then click Shutdown.

    3. Restart bi_server2.

  12. Restart the Oracle Business Intelligence system components:

    $ cd /u02/local/oracle/config/BIInstance1/bin
$ ./opmnctl stopall
$ ./opmnctl startall

14.5.5.4 Adding bi_server2 System Properties to the Server Start Tab

After scaling out the bi_server2 Managed Server, you must add a new system property to the Server Start tab of this Managed Server.

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console.

  2. Click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers.

    The Summary of Servers page displays.

  5. Select bi_server2 in the table.

    The settings page for the server displays.

  6. Click Server Start.

  7. Add the following propery to the arguments:

    -DJDBCProgramName=DS/BIDomain/bi_server2

  8. Click Save and then Activate Changes.

  9. Restart the bi_server2 Managed Server (ensure sure that Node Manager is up and running):

    1. In the Summary of Servers screen, select the Control tab.

    2. Select bi_server2 in the table and then click Shutdown.

    3. Restart bi_server2.

  10. Restart the BI System Components:

    $ cd /u02/local/oracle/config/BIInstance1/bin
$ ./opmnctl stopall
$ ./opmnctl startall

14.5.6 Performing Additional Configuration for Oracle Business Intelligence High Availability

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:

14.5.6.1 Additional Configuration Tasks for Oracle BI Scheduler

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:

  1. Create an ORACLE_BASE/config/BIShared/OracleBISchedulerComponent/coreapplication_obisch1 directory.

  2. From CRMHOST1,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

  3. 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.

  4. 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

14.5.6.2 Additional Configuration Tasks for Oracle Real-Time Decisions

This sections contains the following topics:

14.5.6.2.1 Configuring Oracle Real-Time Decisions Clustering Properties

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.

  1. Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em).

  2. Expand the Application Deployments node in the Farm_BIDomain window.

  3. Expand OracleRTD(11.1.1)(bi_cluster).

  4. Click any node under it. For example, OracleRTD(11.1.1)(bi_server1).

  5. In the right pane, click Application Deployment, and then select System MBean Browser.

  6. In the System MBean Browser pane, expand Application Defined MBeans.

  7. For any one of the servers under OracleRTD, navigate to the MBean and set the attribute, as shown in Table 14-1. Other servers automatically get updated with the value you set.

    Table 14-1 Oracle RTD MBean Attributes and Values for Clustering

    MBean Attribute Value

    SDClusterPropertyManager -> Misc

    DecisionServiceAddress

    http://biinternal.mycompany.com:7777

  8. Click Apply.

14.5.6.2.2 Adding Oracle RTD System Properties to the Server Start Tab

After scaling out Oracle RTD, use the Administration Console to add three system properties to the Server Start tab of each Managed Server.

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console.

  2. Click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers.

    The Summary of Servers page displays.

  5. Select bi_server<1,2> in the table.

    The settings page for the server displays.

  6. Click Server Start.

  7. Add the following propery to the arguments:

    -Drtd.clusterRegistryJobIntervalMs=12000
-Drtd.clusterDepartureThresholdMs=50000
-Drtd.clusterDepartureThreshold2Ms=50000

  8. Click Save and then Activate Changes.

  9. Restart the bi_server<1,2> Managed Server (ensure sure that Node Manager is up and running):

    1. In the Summary of Servers screen, select the Control tab.

    2. Select bi_server<1,2> in the table and then click Shutdown.

    3. Restart bi_server<1,2>.

  10. Restart the BI System Components:

    $ 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:

  1. In Fusion Middleware Control, expand the WebLogic Domain node in the left pane. Then, right-click bifoundation_domain and select System MBean Browser.

  2. 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.

  3. Set the BatchManagerEnabled attribute to false and click Apply.

  4. 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.

  5. 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:

    1. 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

    2. 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

    3. 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

    4. 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.

    5. 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.

14.5.6.3 Additional Configuration Tasks for Oracle BI Publisher

Perform the steps in this section on each machine where Oracle BI Publisher is configured.

This section includes the following topics:

14.5.6.3.1 Configuring Integration with Oracle BI Presentation Services

To configure Oracle BI Publisher integration with Oracle BI Presentation Services:

  1. Log in to Oracle BI Publisher (http://biinternal.mycompany.com:7777/xmlpserver) with Administrator credentials and select the Administration tab.

  2. Under Integration, select Oracle BI Presentation Services.

  3. Verify and update the following:

    • Server Protocol: http

    • Server: biinternal.mycompany.com

    • Port: 7777

    • URL Suffix: analytics-ws/saw.dll

  4. Click Apply.

  5. Restart your Oracle BI Publisher application:

    1. Log in to the Administration Console (http://biinternal.mycompany.com:7777/console).

    2. Click Deployments in the Domain Structure window.

    3. Select bipublisher(11.1.1).

    4. Click Stop, and then select When Work Completes or Force Stop Now.

    5. After the application has stopped, click Start and then Start Servicing All requests.

14.5.6.3.2 Setting the Oracle BI EE Data Source

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:

  1. Log in to Oracle BI Publisher (http://biinternal.mycompany.com:7777/xmlpserver) with Administrator credentials and select the Administration tab.

  2. Under Data Sources, select JDBC Connection.

  3. 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;

    Note:

    Since the Cluster Controller Port may be different between CRMHOST1 and CRMHOST2, you can use the following procedure to check the port being used:

    1. Log in to the Oracle Enterprise Manager Console: http://biinternal.mycompany.com:7777/em .

    2. Expand Farm_Domain > Business Intelligence > coreapplication.

    3. Navigate to Availability.

    4. Check the port number used by the Cluster Controller on CRMHOST1 and CRMHOST2.

  4. 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.

  5. Click Test Connection. You should receive a "Connection established successfully" message.

  6. Click Apply.

14.5.6.3.3 Configuring JMS for BI Publisher

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:

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Domain Structure window, expand the Services node and then click the Persistence Stores node. The Summary of Persistence Stores page is displayed.

  3. Click Lock & Edit.

  4. Click New, and then Create File Store.

  5. 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

  6. Click OK and then Activate Changes.

  7. 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.

  8. Click Lock & Edit.

  9. Click New.

  10. Enter a name (for example, BipJmsServer2) and in the Persistence Store drop-down list, select BipJmsStore2 and click Next.

  11. Select bi_server2 as the target.

  12. Click Finish and Activate Changes.

  13. In the Domain Structure window, expand the Services node and then click the Messaging > JMS Modules node. The JMS Modules page is displayed.

  14. In the Change Center, click Lock & Edit.

  15. Click BIPJmsResource and then click the Subdeployments tab.

  16. Select BipJmsSubDeployment under Subdeployments.

  17. Add the new Oracle BI Publisher JMS Server (BipJmsServer2) as an additional target for the subdeployment.

  18. Click Save and then Activate Changes.

To validate, do the following:

  1. Log in to each Oracle BI Publisher URL.

  2. Navigate to System Maintenance > Administration > Scheduler Diagonistics.

    All statuses should be in a Passed state and both instances should be visible.

14.5.6.4 Additional Configuration Tasks for Oracle BI for Microsoft Office

This section includes the following topics:

14.5.6.4.1 Configuring Oracle BI for Microsoft Office Properties

To perform additional configuration tasks for Oracle BI for Microsoft Office:

  1. 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 14-1.

    Figure 14-1 About Oracle BI EE Office Server Page

    About Oracle BI EE Office Server Page

  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.

    Note:

    You can determine the exact location for CRMHOSTn by using the following URL: http://BIVHn:10217/bioffice/about.jsp.

  3. On both CRMHOST1 and CRMHOST2 , open bioffice.xml for editing and modify the BI Office properties shown in Table 14-2.

    Table 14-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 1 if the Oracle Business Intelligence implementation is enabled for SSO.

    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.

  4. Restart the BI Office application:

    1. Log in to the Administration Console (http://biinternal.mycompany.com:7777/console).

    2. Click Deployments in the Domain Structure window.

    3. Select bioffice(11.1.1).

    4. Click Stop.

    5. After the application has stopped, click Start.

  5. Validate that the SawBaseURL parameter has been updated on the About Oracle BI EE Office Server page.

14.5.6.4.2 Validating Oracle BI for Microsoft Office

To validate configuration for Oracle BI for Microsoft Office:

  1. Log in to Oracle BI Presentation Services at:

    http://biinternal.mycompany.com:7777/analytics

  2. In the lower left pane, under the Get Started heading, select Download BI Desktop Tools and then select Oracle BI for MS Office.

  3. Install Oracle BI for Microsoft by running the Oracle BI Office InstallShield Wizard.

  4. Open Microsoft Excel or Microsoft PowerPoint.

  5. From the Oracle BI menu, select Preferences.

  6. In the Connections tab, select New.

  7. 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 14-2 shows the New Connection dialog.

    Figure 14-2 New Connection Dialog for Oracle BI Office

    About Oracle BI EE Office Server Page

  8. 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 14-3.

    Figure 14-3 Test Connection Successful Message

    Test Connection Successful Message

  9. Log in as an Administrator (for example, weblogic) and validate that you can access the Oracle BI Task Pane, as shown in Figure 14-4.

    Figure 14-4 Oracle BI Task Pane in Microsoft Excel

    Oracle BI Task Pane in Microsoft Excel

14.5.6.5 Additional Configuration Tasks for Oracle Financial Reporting

There are additional configuration tasks to perform for Oracle Financial Reporting. Do the following on CRMHOST1 and CRMHOST2:

  1. 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.

  2. Run the following commands to restart the Oracle Business Intelligence system components:

    $ cd /u02/local/oracle/config/BIInstancen/bin
$ ./opmnctl stopall
$ ./opmnctl startall

14.5.7 Configuring a Default Persistence Store for Transaction Recovery

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:

  1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

  2. In the Change Center, click Lock & Edit.

  3. In the Domain Structure window, expand the Environment node and then click the Servers node. The Summary of Servers page is displayed.

  4. Click bi_server1 in the table. The Settings page for the selected server is displayed, and defaults to the Configuration tab.

  5. Navigate to Configuration > Services.

  6. 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

  7. Click Save.

  8. Repeat Steps 1 through 7 for the bi_server2 Managed Server.

  9. Click Activate Changes.

  10. Start the Managed Servers to activate the changes (ensure that Node Manager is up and running):

    1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

    2. In the Summary of Servers screen, select the Control tab.

    3. Select bi_server1 and bi_server2 in the table and then click Shutdown.

    4. Start the bi_server1 and bi_server2 servers.

    5. Restart the Oracle Business Intelligence system components:

      $ 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.

14.5.8 Starting and Validating Oracle Business Intelligence on CRMHOST2

This section includes the following topics:

14.5.8.1 Starting the bi_server2 Managed Server

To start the bi_server2 Managed Server:

  1. Start the bi_server2 Managed Server using the Oracle WebLogic Server Administration Console, as follows:

    1. Log in to the Oracle WebLogic Server Administration Console (http://biinternal.mycompany.com:7777/console).

    2. Expand the Environment node in the Domain Structure window.

    3. Select Servers. The Summary of Servers page is displayed.

    4. Click the Control tab.

    5. Select bi_server2 and then click Start.

  2. 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.

14.5.8.2 Starting the Oracle Business Intelligence System Components

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:

  1. Go to the directory that contains the Oracle Process Manager and Notification Server command-line tool, located in /u02/local/oracle/config/BIInstance1/bin.

  2. 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

  3. Check the status of the Oracle Business Intelligence system components:

    ./opmnctl status

14.5.8.3 Validating Oracle Business Intelligence URLs

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.

14.5.9 Validating Access Through Oracle HTTP Server

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:

  1. While bi_server2 is running, stop bi_server1 using the Oracle WebLogic Server Administration Console.

  2. 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

  3. Start bi_server1 from the Oracle WebLogic Server Administration Console.

  4. Stop bi_server2 from the Oracle WebLogic Server Administration Console.

  5. 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

  6. Start bi_server2 from the Oracle WebLogic ServerAdministration Console.

14.5.10 Configuring Node Manager for the Managed Servers

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 14-3.

Table 14-3 Details for Host Name Verification for Node Manager and Servers

Run Host Name (Host) Server Name (WLS_SERVER)

Run1:

CRMHOST1

bi_server1

Run2:

CRMHOST2

bi_server2

Note:

If you configured Node Manager for the Managed Servers earlier, you do not need to configure it again.

14.5.11 Configuring Server Migration for the Managed Servers

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 17, "Setting Up Server Migration for an Enterprise Deployment."

14.6 Configuring Oracle Essbase Clustering

This section describes how to configure secondary instances of Oracle Essbase Agent so that they are distributed for high availability.

Prerequisite steps for configuring Oracle Essbase clustering:

  1. On CRMHOST1 or CRMHOST2, delete or rename the EssFOConfig.properties file in the Essbase shared folder under ORACLE_BASE/config/BIShared/Essbase/essbaseserver1.

  2. On CRMHOST1, update the following properties in the /u02/local/oracle/config/BIInstance/bin/essbase_ha/EssFOConfig.properties file:

    SYSTEM_HOST=CRMHOST1
SYSTEM_HOST1=CRMHOST1
SYSTEM_HOST2=CRMHOST2
 
SYSTEM_CLUSTER_NAME=essbasecluster1
SYSTEM_CLUSTER_INST1=essbasecluster1-inst1 
SYSTEM_CLUSTER_INST2=essbasecluster1-inst2 
   
SYSTEM_CLUSTER_INSTANCE1=BIInstance 
SYSTEM_CLUSTER_INSTANCE2=BIInstance1 
 
SYSTEM_AGENT_PORTNUMBER1=10215 
SYSTEM_AGENT_PORTNUMBER2=10215

Perform the following steps in Fusion Middleware Control:

  1. Log in to Fusion Middleware Control (http://biinternal.mycompany.com:7777/em).

  2. Expand the Business Intelligence node in the Farm_BIDomain window.

  3. Click coreapplication.

  4. Click Availability, then click Failover.

  5. Click Lock and Edit Configuration to activate the Primary/Secondary Configuration section of the Availability tab.

  6. Specify the Secondary Host/Instance for Oracle Essbase Agent.

  7. Ensure the shared folder is located at ORACLE_BASE/config/BIShared/Essbase/essbaseserver1 and click Apply.

    Under Potential Single Points of Failure, no problems should be reported for Oracle Essbase Agent.

  8. Click Activate Changes.

  9. Under Manage System, click Restart.

  10. Click Yes in the confirmation dialog.

14.6.1 Validating Essbase Clustering

Do the following to validate Essbase clustering:

  1. Check the APS (Hyperion Provider Services) test URL:

    http://biinternal.mycompany.com:7777/aps/Test

  2. Run the following command on CRMHOST1:

    /u02/local/oracle/config/BIInstance/bin/opmnctl stopproc 
ias-component=essbasecluster1

  3. Ensure that Essbase starts on CRMHOST2:

    /u02/local/oracle/config/BIInstance1/bin/opmnctl status

    The status should be init then Alive.

  4. Check the APS test URL again:

    http://biinternal.mycompany.com:7777/aps/Test

14.7 Validating the System

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:

  1. While bi_server2 is running, stop bi_server1 using the Oracle WebLogic Server Administration Console.

  2. 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

  3. Start bi_server1 from the Oracle WebLogic Server Administration Console.

  4. Stop bi_server2 from the Oracle WebLogic Server Administration Console.

  5. Access the following URLs to verify that routing and failover is functioning properly:

    • http://WEBHOST1:10621/analytics

    • http://WEBHOST1:10621/xmlpserver (access only available on Microsoft Internet Explorer 7 or 8)

    • http://WEBHOST1:10621/ui

    • http://WEBHOST1:10621/hr

    • http://WEBHOST1:10621/workspace

    • http://WEBHOST1:10621/calcmgr/index.htm

    • http://WEBHOST1:10621/aps/Test

  6. Start bi_server1 from the Oracle WebLogic ServerAdministration Console.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us