6 Scaling Out the Oracle Business Intelligence System

6.1.1.1 Setting the Location of the Shared Oracle BI Repository

When you specify a repository publishing directory for the Oracle BI repository, each Oracle BI Server instance loads the repository from the shared network location.

Perform the following steps in Oracle Enterprise Manager Fusion Middleware Control:

1. Log in to Fusion Middleware Control.

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

3. Click coreapplication.

4. Click Deployment, then click Repository.

5. Click Lock and Edit Configuration.

6. Select Share Repository and specify the Shared Location for the Oracle BI Repository.

   In a Windows environment, you must specify a UNC path name.

7. If you already have a repository deployed locally in your system, upload the repository again so that it gets copied to the shared location. Otherwise, you can skip this step.

8. Click Apply.

9. Click Activate Changes.

6.1.1.2 Setting the Location of the Shared Oracle BI Presentation Catalog

Each Presentation Services instance loads the Oracle BI Presentation Catalog from the catalog location specified in Fusion Middleware Control.

Perform the following steps:

1. Copy your existing (locally published) Oracle BI Presentation Catalog to the shared location. An example of a locally published catalog is:

   ORACLE_INSTANCE/bifoundation/OracleBIPresentationServicesComponent/
   coreapplication_obipsn/catalog/SampleAppLite
   

   You must perform this step before designating the Catalog Location from Fusion Middleware Control.

2. Log in to Fusion Middleware Control.

3. Expand the Business Intelligence node in the Farm_domain_name window.

4. Click coreapplication.

5. Click Deployment, then click Repository.

6. Click Lock and Edit Configuration.

7. Specify the Catalog Location for the shared Oracle BI Presentation Catalog.

   In a Windows environment, you must specify a UNC path name.

8. Click Apply.

9. Click Activate Changes.

6.1.1.3 Setting the Location of the Global Cache

The global cache resides on a shared file system storage device and stores purging events, seeding events (often generated by Agents), and result sets associated with seeding events. Note that each Oracle BI Server still maintains its own local query cache for regular queries.

Perform the following steps in Fusion Middleware Control:

1. Log in to Fusion Middleware Control.

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

3. Click coreapplication.

4. Click Capacity Management, then click Performance.

5. Click Lock and Edit Configuration.

6. In the Global Cache section, specify the shared location for storing purging and seeding cache entries in the Global cache path field. In a Windows environment, you must specify a UNC path name.

7. Enter a value for Global cache size to specify the maximum size of the global cache (for example, 250 MB).

8. Click Apply.

9. Click Activate Changes.

10. Click Restart to apply recent changes.

11. Click Restart under Manage System.

12. Click Yes in the confirmation dialog.

6.5.2.1 Configuring Oracle Real-Time Decisions Clustering Properties

Perform the following steps in Fusion Middleware Control to set up cluster-specific configuration properties for Oracle RTD.

You only need to perform these steps for the first node 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.

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

3. Click 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 SDClusterPropertyManager -> Misc MBean and set the DecisionServiceAddress attribute to http://bi.mycompany.com. Other servers automatically get updated with the value you set.

8. Click Apply.

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

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

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

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

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

6. 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, as follows:

   1. Locate the zip file for the Oracle RTD client tools in the following location:

      ORACLE_HOME/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 computer (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 preceding example.

6.5.3.1 Setting the Location of the Shared Oracle BI Publisher Configuration Folder

Follow these steps to set server configuration options for Oracle BI Publisher:

1. Copy the DOMAIN_HOME/config/bipublisher/repository/Admin directory to the shared configuration folder location.

2. On either APPHOST1 or APPHOST2, log in to BI Publisher with Administrator credentials and select the Administration tab.

3. Under System Maintenance, select Server Configuration.

4. In the Path field under Configuration Folder, enter the shared location for the Configuration Folder.

5. Apply your changes and restart your BI Publisher application, as follows:

   1. Log in to the Administration Console.

   2. Click Deployments in the Domain Structure window.

   3. Select bipublisher(11.1.1).

   4. Click Stop.

   5. After the application has stopped, click Start.

6. Because Oracle BI Publisher reads its configuration from the Administration Server central location rather than from the Managed Server's configuration directory when the Managed Servers are restarted, you must copy the XML configuration file for Oracle BI Publisher from the Managed Server to the Administration Server location.

   To do this, on APPHOST1, copy the file xmlp-server-config.xml from:

   ORACLE_BASE/admin/domain_name/mserver/domain_name/config/bipublisher
   

   to:

   ORACLE_BASE/admin/domain_name/aserver/domain_name/config/bipublisher
   

6.5.3.2 Setting Scheduler Configuration Options

Follow these steps to set Scheduler configuration options:

1. On APPHOST1, log in to BI Publisher with Administrator credentials and select the Administration tab.

2. Under System Maintenance, select Scheduler Configuration.

3. Select Quartz Clustering under the Scheduler Selection.

4. Click Apply.

6.5.3.3 Configuring Integration with Oracle BI Presentation Services

Follow these steps to configure Oracle BI Publisher integration with Oracle BI Presentation Services:

1. Log into Oracle BI Publisher with Administrator credentials and select the Administration tab.

2. Under Integration, select Oracle BI Presentation Services.

3. Update the Server and Port, as follows:

   • Server: bi.mycompany.com

   • Port: 80

4. Click Apply.

5. Restart your Oracle BI Publisher application.

6.5.3.4 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 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://APPHOST1:9706/PrimaryCCS=APPHOST1;PrimaryCCSPort=9706;
   SecondaryCCS=APPHOST2;SecondaryCCSPort=9706;
   

4. Deselect Use System User and specify administrator credentials for Username and Password (for example, weblogic).

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

6. Click Apply.

6.5.3.5 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 into the Administration 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 New, and then Create File Store.

5. Enter a name (for example, BipJmsStore2) and target BI_SERVER2. Enter a directory that is located in shared storage so that it is accessible from both APPHOST1 and APPHOST2:

   ORACLE_BASE/admin/domain_name/bi_cluster/jms
   

6. Click OK and 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. In the Change Center, 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 Activate Changes.

To validate the JMS configuration performed for Oracle BI Publisher, perform the steps in Section 6.5.3.6, "Updating the Oracle BI Publisher Scheduler Configuration."

6.5.3.6 Updating the Oracle BI Publisher Scheduler Configuration

Follow the steps in this section to update the WebLogic JNDI URL and the JMS Shared Temp Directory for the Oracle BI Publisher Scheduler. You only need to perform the steps in this section on one of the APPHOSTS (either APPHOST1 or APPHOST2).

To update the Oracle BI Publisher Scheduler configuration:

1. Log in to Oracle BI Publisher at the one of the following URLs:

   • http://APPHOST1VHN1:9704/xmlpserver

   • http://APPHOST2VHN1:9704/xmlpserver

2. Click the Administration link.

3. Click Scheduler Configuration under System Maintenance. The Scheduler Configuration screen is displayed.

4. Update the WebLogic JNDI URL under JMS Configuration, as follows:

   t3://APPHOST1VHN1:9704,APPHOST2VHN1:9704

5. Update the Shared Directory by entering a directory that is located in the shared storage. This shared storage is accessible from both APPHOST1 and APPHOST2.

6. Click Test JMS.

   You should receive a confirmation message that JMS tested successfully.

7. Click Apply.

8. Check the Scheduler status from the Scheduler Diagnostics tab.

6.5.4.1 Configuring Oracle BI for Microsoft Office Properties

Follow these steps to perform additional configuration tasks for Oracle BI for Microsoft Office:

1. Validate the Oracle BI EE Office Server setup by accessing the following URLs:

   • http://APPHOST1VHN1:9704/bioffice/about.jsp

   • http://APPHOST2VHN1:9704/bioffice/about.jsp

   The About Oracle BI EE Office Server page is displayed, as shown in Figure 6-1.

   Figure 6-1 About Oracle BI EE Office Server Page

   
   Description of "Figure 6-1 About Oracle BI EE Office Server Page"
   
   

2. Go to the Oracle BI EE Office Server directory. For example:

   DOMAIN_HOME/servers/managed_server/tmp/_WL_user/bioffice_11.1.1/cvsibb/war/WEB-INF

   If you are not sure how to locate the Oracle BI EE Office Server directory, check the LogDir parameter on the About Oracle BI EE Office Server page. The Oracle BI EE Office Server directory is the parent directory of the log directory.

3. On both APPHOST1 and APPHOST2, open bioffice.xml for editing and modify the properties shown in Table 6-1.

   Table 6-1 Properties in bioffice.xml

   Property Name	Valid Value	Description
   SawBaseURL	https://bi.mydomain.com:443/analytics/saw.dll or https://bi.mydomain.com:443/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 Oracle BI for Microsoft 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	https://bi.mydomain.com:443/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 Oracle BI for Microsoft Office.

   
   

4. Restart the Oracle BI for Microsoft Office application, as follows:

   1. Log in to the Administration 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.

6.5.4.2 Validating Oracle BI for Microsoft Office Configuration

Follow these steps to validate configuration for Oracle BI for Microsoft Office:

1. Log in to Oracle BI Presentation Services at:

   https://bi.mydomain.com:443/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 Office 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 EE Office Server.

   • Application Name: Enter the Application Name that you defined for the Oracle BI EE Office Server when you deployed the Oracle BI EE Office Server application to WLS. The default name is bioffice.

   • Port: Enter the Oracle BI EE Office Server port number.

   Figure 6-2 shows the New Connection dialog.

   Figure 6-2 New Connection Dialog for Oracle BI for Microsoft Office

   
   Description of "Figure 6-2 New Connection Dialog for Oracle BI for Microsoft Office"
   
   

8. Click Test Connection to test the connection between the add-in and the Oracle BI EE Office Server.

   Successful connections receive a Test connection successful message, as shown in Figure 6-3.

   Figure 6-3 Test Connection Successful Message

   
   Description of "Figure 6-3 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 6-4.

   Figure 6-4 Oracle BI Task Pane in Microsoft Excel

   
   Description of "Figure 6-4 Oracle BI Task Pane in Microsoft Excel"