1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:

   http://ADMINVHN:7001/em
   

2. Sign in to the Fusion Middleware Control using the Administration Server credentials.
3. If not already displayed, click the Target Navigation icon in the top left corner of the page to display the Target Navigation pane.
4. In the Target Navigation pane, expand the Business Intelligence folder and select biinstance.
   The Business Intelligence Overview page appears.
5. Click Availability and then Processes to display the Processes tab on the Availability page.
6. Click Stop All to stop all the system components.

1. Navigate to the following directory:

   ASERVER_HOME/bin
   

2. Use the following command to stop the Node Manager:

   ./stopNodeManager.sh 

1. Navigate to the following directory:

   MSERVER_HOME/bin
   

2. Use the following command to stop the Node Manager:

   ./stopNodeManager.sh 

For a scaled-out Publisher application, the individual instances require a common location to set certain configurations across the cluster.

1. Acquire the SSD location from Step 1 of Configuring the Singleton Data Directory (SDD):
   For example:

   ORACLE_RUNTIME/biconfig

2. Recursively copy the entire BI_ASERVER_HOME/config/fmwconfig/biconfig/bipublisher/Admin directory into the SDD sub-directory bidata/components/bipublisher/repository:
   For example:

   cp -R BI_ASERVER_HOME/config/fmwconfig/biconfig/bipublisher/Admin ORACLE_RUNTIME/biconfig/bidata/components/bipublisher/repository

3. Validate the now directory's contents:
   For example:

   ls -1 ORACLE_RUNTIME/biconfig/bidata/components/bipublisher/repository/Admin

   The results must look like the following example:

   Configuration
   DataSource
   Delivery
   Map
   Plugins
   Scheduler
   Security

4. Restart the WLS_BI1 and WLS_BI2 managed servers.

Follow these steps to update the JMS Shared Temp Directory for Oracle Analytics Publisher Scheduler. You need to perform the steps in this section on only one of the Oracle Analytics Server hosts (either BIHOST1 or BIHOST2).

1. Sign in to Oracle Analytics Publisher using one of the following URLs:
   • http://BIHOST1VHN:7003/xmlpserver
   • http://BIHOST2VHN:7003/xmlpserver
2. Click the Administration tab.
3. Click Scheduler Configuration under System Maintenance.
   The Scheduler Configuration screen is displayed.
4. Update the Shared Directory by entering a directory that is located in the shared storage. This shared storage is accessible from both BIHOST1 and BIHOST2.
5. Click Test JMS.

   You see a confirmation message that JMS tested successfully.

   Note:

   If you do not see a confirmation message for a successful test, then verify that the JNDI URL is set to the following:

   cluster:t3://bi_cluster

6. Click Apply.
7. Check the Scheduler status from the Scheduler Diagnostics tab.

1. Log into Oracle Analytics Publisher with Administrator credentials and select the Administration tab.
2. Under Integration, select Oracle BI Presentation Services.
3. Select Manual Configuration option. Then verify and update the following:

   • Server Protocol: HTTP

   • Server: biinternal.mycompany.com

   • Port: 80

   • URL Suffix: analytics-ws/saw.dll

4. Click Apply.
5. Restart the Oracle Analytics Publisher application.

The Oracle Analytics Server data source must point to the clustered Oracle Analytics Server Servers through the Cluster Controllers. You must perform this task in Oracle Analytics Publisher.

1. Sign in to Oracle Analytics Publisher using the following URL with administrator credentials.

   http://BIHOST1VHN:7003/xmlpserver

2. Select the Administration tab.
3. Under Data Sources, select JDBC Connection.
4. Update the Oracle Analytics Server 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://BIHOST1:10006/PrimaryCCS=BIHOST1;PrimaryCCSPort=10006;
   SecondaryCCS=BIHOST2;SecondaryCCSPort=10006;

   To find the cluster controller port number:
   1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:
      http://ADMINVHN:7001/em
   2. Sign in to the Fusion Middleware Control using the Administration Server credentials.
   3. If not already displayed, click the Target Navigation icon in the top left corner of the page to display the Target Navigation pane.
   4. In the Target Navigation pane, expand the Business Intelligence folder and select biinstance.
      The Business Intelligence Overview page appears.
   5. Click Availability and then Processes to display the Processes tab on the Availability page.
   6. Note the port number from the Port column.
5. Select Use System User.
6. Click Test Connection.
   The Connection established successfully message is displayed.
7. Click Apply.

To configure the BIPJMSResource JMS Module, you must modify some default values within the module as listed in this topic.

1. Sign in to the Oracle WebLogic Server Administration Console.
2. From Services, click Messaging and select JMS Modules from the left navigation pane.
3. Click BIPJMSResource on the list of JMS Modules.
4. Select dist_BIP.System.T_auto_1 on the Summary of Resources table.
5. Click General tab.
6. Click Lock & Edit from the Change Center.
7. From the Forwarding Policy menu, select Replicated.
8. Click Save.
9. Click Activate Changes.