10-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
– Transaction Log directory
– JMS Persistence Store
– Global Cache
– BI Presentation Catalog
– BI Repository Publishing directory
– BI Publisher Catalog
– BI Publisher Configuration Keystore certs
– MW_HOME
10.3.2.1 Scale-out Procedure for Oracle Business Intelligence
Perform these steps to scale out Oracle Business Intelligence on APPHOST3:
1.
On APPHOST3, mount the existing Middleware home, which should include the Oracle Business Intelligence installation and optionally, if the domain directory
for Managed Servers in other nodes resides on shared storage the domain directory, and ensure that the new node has access to this directory, just like the
rest of the nodes in the domain.
2.
To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute the following command:
APPHOST3 cd ORACLE_COMMON_HOMEouibin APPHOST3 .attachHome.sh -jreLoc ORACLE_BASEproductfmwjrockit_160_version
To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the MW_HOME.home file and add ORACLE_
BASEproductfmw to it.
3. Run the Configuration Assistant from one of the shared Oracle homes, using the
steps in Section 6.1, Scaling Out the BI System on APPHOST2
as a guide.
4. Scale out the system components on APPHOST3, using the steps in
Section 6.2, Scaling Out the System Components
as a guide.
5.
Configure the bi_server3 Managed Server by setting the Listen Address and disabling host name verification, using the steps in
Section 6.4, Configuring the bi_server2 Managed Server
as a guide.
6.
Configure JMS for Oracle BI Publisher, as described in Section 6.5.3.5,
Configuring JMS for Oracle BI Publisher.
7.
Configure Oracle BI for Microsoft Office on APPHOST3, as described in Section 6.5.4, Additional Configuration Tasks for Oracle BI for Microsoft Office.
8.
Set the location of the default persistence store for bi_server 3, as described in Section 6.6, Configuring a Default Persistence Store for Transaction Recovery.
9.
Configure Oracle HTTP Server for APPHOST3VHN1, using the steps in Section 5.10.2, Configuring Oracle HTTP Server for the bi_servern Managed
Servers as a guide.
10.
Start the bi_server3 Managed Server and the system components running on APPHOST3. See
Section 10.1, Starting and Stopping Oracle Business Intelligence for details.
11.
Set up server migration for the new node, as described in the following sections:
■
Section 8.3, Enabling Host Name Verification Certificates
Managing Enterprise Deployments 10-5
■
Section 8.4, Editing the Node Manager Properties File
■
Section 8.5, Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
■
Section 8.6, Configuring Server Migration Targets
■
Section 8.7, Testing the Server Migration
12.
To validate the configuration, access the following URLs:
■
Access http:APPHOST3VHN1:9704analytics to verify the status of bi_ server3.
■
Access http:APPHOST3VHN1: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:APPHOST3VHN1:9704xmlpserver to verify the status of the Oracle BI Publisher application.
■
Access http:APPHOST3VHN1:9704ui to verify the status of the Oracle Real-Time Decisions application.
13.
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 further details.
10.4 Performing Backups and Recoveries
