6-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
Figure 6–4 Oracle BI Task Pane in Microsoft Excel
6.6 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.
Perform these steps for each Managed Server to set the location for the default persistence store:
1.
Log in to the Administration 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 the name of the server represented as a hyperlink in the Names column of the table. The Settings page for the selected server is displayed, and defaults to the
Configuration tab.
5. Open the Services tab.
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. The directory structure of the path
is as follows:
ORACLE_BASEadmindomain_namebi_cluster_nametlogs
Note: Preferably, this location should be a dual-ported SCSI disk or
on a Storage Area Network SAN.
Scaling Out the Oracle Business Intelligence System 6-17
Use the same path for each Managed Server. When the Managed Servers are restarted, subdirectories are created for each one.
7. Click Save and Activate Changes.
6.7 Starting and Validating Oracle Business Intelligence on APPHOST2
This section contains the following topics:
■
Section 6.7.1, Starting the bi_server2 Managed Server
■
Section 6.7.2, Starting the Oracle Business Intelligence System Components
■
Section 6.7.3, Validating Oracle Business Intelligence URLs
6.7.1 Starting the bi_server2 Managed Server
Perform these steps to start the bi_server2 Managed Server:
1. Start the bi_server2 Managed Server using the Administration Console, as follows:
a. Expand the Environment node in the Domain Structure window.
b. Click Servers. The Summary of Servers page is displayed.
c. Click the Control tab.
d. 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.
6.7.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 OPMN command-line tool, located in ORACLE_INSTANCEbin.
2.
Run the opmnctl command to start the Oracle Business Intelligence system components:
■
opmnctl startall Starts OPMN and all Oracle Business Intelligence system components.
■
opmnctl start Starts OPMN only.
■
opmnctl startproc ias-component=component_name
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.
6-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
Starts a particular system component. For example, where coreapplication_ obips2 is the Presentation Services component:
opmnctl startproc ias-component=coreapplication_obips2
3.
Check the status of the Oracle Business Intelligence system components: opmnctl status
6.7.3 Validating Oracle Business Intelligence URLs
Access the following URLs:
■
Access http:APPHOST2VHN1:9704analytics to verify the status of bi_server1.
■
Access http:APPHOST2VHN1:9704wsm-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:APPHOST2VHN1:9704xmlpserver to verify the status of the Oracle BI Publisher application.
■
Access http:APPHOST2VHN1:9704ui to verify the status of the Oracle Real-Time Decisions application.
■
Access http:APPHOST2VHN1:9704mapviewer to verify the status of Oracle MapViewer.
6.8 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 Administration Console.
2. Access the following URLs to verify that routing and failover is functioning
properly:
■
http:WEBHOST1:7777analytics
■
http:WEBHOST1:7777xmlpserver
■
http:WEBHOST1:7777ui
3.
Start bi_server1 from the Administration Console.
4.
Stop bi_server2 from the Administration Console.
5.
Access the following URLs to verify that routing and failover is functioning properly:
■
http:WEBHOST1:7777analytics
■
http:WEBHOST1:7777xmlpserver
■
http:WEBHOST1:7777ui
6.
Start bi_server2 from the Administration Console.
6.9 Configuring Node Manager for the Managed Servers
