Managing Availability in Oracle Business Intelligence (Horizontally Scaling)

If you have multiple instances of a given Oracle Business Intelligence component in the deployment, you should first configure shared files and directories for the clustered components to use.

For information, see Setting Up Shared Files and Directories.

After horizontally scaling out, you typically configure an HTTP server and load balancer to distribute requests across multiple managed servers. For information, see Load Balancing in a Cluster in Administering Clusters for Oracle WebLogic Server. If a front end load balancer has been setup, then you must set the WebLogic Server Front-End Host and Port for the BI cluster (bi_cluster).

The commands described in this section should only be used by advanced users. Note that availability commands automatically create a symmetric set of processes when configuring additional hosts.

For more information, Using the WebLogic Scripting Tool (WLST).

Note:

To add a new node to a cluster when SSL has been configured, you must scale out to the new cluster (see Adding New Computers), then ensure SSL is correctly set up (see Configuring SSL in Oracle Business Intelligence in Security Guide for Oracle Business Intelligence Enterprise Edition).

Adding New Computers

You can add a new computer to extend the BI cluster across multiple computers, increasing availability and capacity.

Assumptions

  • The new computer must meet the same install pre-requisites (for example, operating system, memory).

  • SDD must have been set up.

  • ORACLE_HOME must be the same absolute path on both computers.

  • It is recommended, but not required, that the DOMAIN_HOME is the same on both hosts.

  • A symmetric set of active-active components is created on the new computer.

  • The BI system must be stopped (offline).

  • You must have appropriate file system (offline) or Weblogic Administrator (online) permissions.

  • The same ports are allocated as on the original host.

  • The managed server is added to the existing Oracle Business Intelligence cluster.

  • Cluster Controller, Scheduler and BI Server mastership is not changed.

  • Note that optional base computer and server parameters are provided to support the case where m1/bi_server1 has been deleted.

  • Unless provided the computer (WebLogic machine) name will default to the listen address and must be less than 32 characters.

To add a new computer:

Creates an additional managed server, node manager, system components and services on the new computer.

  1. On the master computer, run the clone script:

    DOMAIN_HOME/bitools/bin/clone_bi_machine.sh|cmd [-m <new machine name>] <listen address> <pack file>

    <new machine name> is optional and defaults to the listen address.

    The SSL certificate step is done for you in the script.

  2. On the new machine, install WebLogic Server and Oracle Business Intelligence.

    For information, see Installing and Configuring Oracle Business Intelligence.

  3. Test connectivity between the two hosts.
  4. Copy the pack file from the master host computer (the one with the Admin server) to the new computer.
  5. On the new computer, apply the pack file by running the unpack command.

    For example in:

    ORACLE_HOME/oracle_common/common/bin

    ./unpack.sh -template=[location of copied jar file from master node] –domain=DOMAIN_HOME -nodemanager_type=PerDomainNodeManager

    Note:

    The syntax to display help is: ./unpack.sh|cmd -help.
  6. On the new computer, start node manager using the startNodeManager script.

    For example in:

    /oraclehome/user_projects/domains/bi/bin

    Enter:

    ./startNodeManager.sh
  7. Re-synchronize the data source on new machine.

    Run the script in:

    DOMAIN_HOME/bitools/bin/sync_midtier_db.cmd

    For more information, see BI-Specific WLST Command Reference.

  8. On the master host computer, start inactive components in:

    DOMAIN_HOME/bitools/bin/

    Enter:

    ./start.sh

    For information, see Starting Oracle Business Intelligence Component Processes in a Domain.

Post Conditions

  • Computer, Managed server, Node Manager and System Components are created.

  • Service instances are registered on the second computer.

  • Ports are allocated.

Removing Existing Computers

Remove a failed or redundant computer from a BI Cluster.

Assumptions

  • No binaries, configuration or state is deleted from the removed computer.

  • Cluster Controller, Scheduler and BI Server mastership is unchanged.

  • You cannot remove the master computer.

  • Service Instance registrations can be added or removed.

  • The BI system can be running (online) or stopped (offline).

  • You must have appropriate file system (offline) or Weblogic Administrator (online) permissions.

  • The command does not result in a loss of service.

  • The command can only result in a loss of availability if forced by the user.

Pre-requisites

If possible, you should stop active components on the target computer before removing it using the status.sh and stop.sh scripts. For information, see Using Commands to Start, Stop, and View Status of Oracle BI EE Processes.

To remove an existing computer:

  1. Use the deleteBIMachine WLST command to remove components created by cloneBIMachine or clone_bi_machine.sh in:

    ORACLE_HOME/oracle_common/common/bin/wlst.sh

    For example:

    deleteBIMachine(DOMAIN_HOME, <machine>)

    Or run the delete_bi_machine.sh script in:

    DOMAIN_HOME/bitools/bin/delete_bi_machine.sh|cmd machineName

  2. The command displays the removed computer name.

Post Conditions

  • Computer, Managed Server, Node Manager and System Components are removed from that computer.

  • Service Instances are unregistered from that computer.

  • Ports are unallocated.