This chapter describes the steps to scale out your initial Oracle Business Intelligence domain to BIHOST2.
Scaling out your components involves installing the Oracle Business Intelligence on the other host computers, stopping and cloning the components on BIHOST1, packing and unpacking the domain and starting the components after scaling out.
bidomaintemplate.jar
file from BIHOST1 to BIHOST2.If you have configured a separate shared storage volume or partition for BIHOST2, then you must also install the Infrastructure on BIHOST2.
For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
To install the software on the other host computers in the topology, log in to each host, and use the instructions in Starting the Infrastructure Installer on BIHOST1 and Navigating the Infrastructure Installation Screens to create the Oracle home on the appropriate storage device.
Note:
In previous releases, the recommended enterprise topology included a colocated set of Oracle HTTP Server instances. In those releases, there was a requirement to install the Infrastructure on the Web Tier hosts (WEBHOST1 and WEBHOST2). However, for this release, the enterprise deployment topology assumes the Web servers are installed and configured in standalone mode, so they are not considered part of the application tier domain. For more information, see Configuring the Web Tier for an Enterprise Deployment
If you have configured a separate shared storage volume or partition for BIHOST2, then you must also install the software on BIHOST2.
For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
To install the software on the other host computers in the topology, log in to each host, and use the instructions in Starting the Installation Program and Navigating the Installation Screens.
Before you scale out, you must stop all the component processes in the domain on BIHOST1.
The component processes include the Node Managers, the Administration Server for the WebLogic domain, the system components, and the WLS_BI1 Managed Server, which is controlled by the Node Manager.
To stop all the components in the domain on BIHOST1, perform the following tasks.
Follow these steps to stop the system components using Fusion Middleware Control.
Follow these steps to stop the WLS_BI1 Managed Server using Fusion Middleware Control.
Use these steps to stop the Administration Server using the Node Manager.
After stopping all the component processes, you must clone the components in the domain on BIHOST1, which will create new components on BIHOST2 based on the initial domain you created.
Perform the following steps on BIHOST1 to create additional components by cloning your existing Managed Server, Node Manager, system components, and service instance. You will later pack and unpack the new components on BIHOST2.
Use the steps in this section to create a template jar file that contains the domain configuration information, which now includes configuration information about the Oracle HTTP Server instances.
Use the steps in this section to unpack the domain template containing the domain configuration information and copy the bidomaintemplate.jar
file from BIHOST1 to BIHOST2.
This section describes the steps to start the component processes on BIHOST1 and BIHOST2 after scale out. The component processes include the Node Managers, the Administration Server for the WebLogic domain, the system components, and the Managed Servers.
To start the components after scale out, perform the following tasks.
To start the per-domain Node Manager for the ASERVER_HOME domain directory on BIHOST1, use the procedure in Starting the Node Manager in the Administration Server Domain Home on BIHOST1.
To start the Administration Server using the Node Manager, use the procedure in Starting the Administration Server.
To start the per-domain Node Managers for the MSERVER_HOME directories on BIHOST1 and BIHOST2, use the procedure in Starting the Node Manager in the Managed Server Domain Directory on BIHOST1.
To start the WLS_BI1 and WLS_BI2 Managed Servers, use the procedure in Starting the WLS_BI1 Managed Server on BIHOST1.
After starting the components in the domain on BIHOST2, access these URLs to verify the configuration of Oracle Business Intelligence.
Perform these manual tasks to configure Oracle BI Publisher.
Follow these steps to update the JMS Shared Temp Directory for BI Publisher Scheduler. You need to perform the steps in this section on only one of the BI hosts (either BIHOST1 or BIHOST2).
Perform the following steps to update the BI Publisher Scheduler configuration:
The Oracle Business Intelligence Enterprise Edition (BI EE) data source must point to the clustered Oracle BI Servers through the Cluster Controllers. You must perform this task in BI Publisher.
Perform the following steps to set the Oracle BI EE data source in BI Publisher:
It is an Oracle best practices recommendation to create a backup after successfully configuring a domain or at another logical point. Create a backup after verifying that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.
For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.