Oracle® Solaris Cluster Data Service for Oracle Business Intelligence Enterprise Edition Guide

Exit Print View

Updated: July 2014, E39576–01
 
 

BI Scheduler Configuration

This section describes how to configure the BI scheduler and create the appropriate Oracle Solaris Cluster resource groups and resources for both a failover and a multi-master case.

How to Define a Failover Configuration for BI Scheduler

The failover BI scheduler configuration does not require a cluster controller because there is only one active BI scheduler process.

  1. As user oracle (or any non-root user), install the Oracle Database client software on the servers that will host the scheduler.

    The schedulers need access to the Oracle Database client libraries and tnsnames.ora file to be able to connect to the scheduler database.

  2. Create and configure a database to hold the scheduler job information.

    For more information, see the section “Configuration Tasks for Oracle BI Scheduler ” in the Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition.


    Note -  If the schedule database is an Oracle database on an Oracle Solaris Cluster configuration, make the schedule highly available by using the Oracle Solaris Cluster HA for Oracle Database agent or by using an Oracle RAC database with Oracle Solaris Cluster software.
  3. Configure the scheduler.

    For more information, see the section “Configuring Oracle BI Scheduler Instances in a Clustered Environment” in the Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition.

  4. Edit the scheduler user parameters file to provide appropriate Oracle Solaris information.

    To access the Oracle client libraries, the scheduler uses parameters set in the BI_INSTALL_DIRECTORY/setup/user.sh file. Uncomment and provide appropriate values for the Oracle Solaris entries:

    $ cat ~/OracleBI/setup/user.sh
    …
    ORACLE_HOME=/export/home/oracle/app/oracle/product/11.1.0/client_1
    export ORACLE_HOME
    TNS_ADMIN=$ORACLE_HOME/network/admin
    export TNS_ADMIN
    PATH=$ORACLE_HOME/bin:/opt/bin:$PATH
    export PATH
    LD_LIBRARY_PATH_64=$ORACLE_HOME/lib: $LD_LIBRARY_PATH_64:/opt/jdk/jdk1.6.0_20/jre/lib/sparc
    export LD_LIBRARY_PATH_64
    …
  5. As the obiee user, launch the scheduler configuration utility.
    $ cd Oracle-BI-Install-dir/setup
    $ . ./sa-init64.sh
    $ schconfig
  6. Use the schconfig utility to set the following parameters:
    • Set the Data Source Name to the scheduler database service name in the tnsnames.ora file.

    • Set the User Name and Password to the user name and password that you use to access the scheduler database.

    • Set the Scheduler Script Path and Default Script Path to locations that reside on a global file system.

    • To simplify setup and to avoid having to use certificates, set the Administrator Password to null.

    • Set Participant in Cluster to False.

    • Set the SAW Machine Name to the logical hostname of the Presentation Services tier.

    The schconfig utility modifies the BI_DATA_DIRECTORY/scheduler/config/instanceconfig.xml file.

  7. Register the BI scheduler resource type.
    # clresourcetype register ORCL.obiee_scheduler 
  8. Create the BI scheduler resource.
    # clresource create -g bi-svr-rg \
    -t ORCL.obiee_scheduler \
    -p Run_64_bit=True \
    -p Resource_dependencies_offline_restart=bi-svr-hasp-rs,bi-svr-lh-rs \
    -p BI_INSTALL_DIRECTORY=/failover/obiee/OracleBI \
    -p BI_DATA_DIRECTORY=/failover/obiee/OracleBIData \
    bi-sch-rs 
  9. Verify the status of the resource.
    # clresource status bi-sch-rs
    === Cluster Resources ===
    Resource Name 	Node Name 	State 	Status Message
    ------------- 	--------- 	----- 	--------------
    bi-sch-rs           phys-red1 	Online 	Online - Service is online.
                      phys-red2 	Offline	Offline

How to Define a Multi-Master Configuration for BI Scheduler

A multi-master BI Scheduler configuration requires primary and secondary BI Cluster Controllers to be configured as explained in BI Cluster Controller Configuration, although strictly speaking, the secondary BI Cluster Controller is optional when creating an Oracle Solaris Cluster configuration. The BI Cluster Controller is responsible for directing requests coming in from the Presentation Services clients to the active BI scheduler.

  1. As user oracle (or any non-root user), install the Oracle Database client software on the servers that will host the scheduler.

    The schedulers need access to the Oracle Database client libraries and tnsnames.ora file to be able to connect to the scheduler database.

  2. Create and configure a database to hold the scheduler job information.

    For more information, see the section “Configuration Tasks for Oracle BI Scheduler ” in the Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition.

  3. Configure the scheduler.

    For more information, see the section “Configuring Oracle BI Scheduler Instances in a Clustered Environment” in the Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition.

  4. Edit the scheduler user parameters file to provide appropriate Oracle Solaris information.

    In order to access the Oracle client libraries, the scheduler uses parameters set in the BI_INSTALL_DIRECTORY/setup/user.sh file. Uncomment and provide appropriate values for the Oracle Solaris entries.

    $ cat ~/OracleBI/setup/user.sh
    …
    ORACLE_HOME=/export/home/oracle/app/oracle/product/11.1.0/client_1
    export ORACLE_HOME
    TNS_ADMIN=$ORACLE_HOME/network/admin
    export TNS_ADMIN
    PATH=$ORACLE_HOME/bin:/opt/bin:$PATH
    export PATH
    LD_LIBRARY_PATH_64=$ORACLE_HOME/lib: $LD_LIBRARY_PATH_64:/opt/jdk/jdk1.6.0_20/jre/lib/sparc
    export LD_LIBRARY_PATH_64
    …
  5. As the obiee user on each cluster node, launch the scheduler configuration utility.
    $ cd Oracle-BI-Install-dir/setup
    $ . ./sa-init64.sh
    $ schconfig
  6. On each cluster node, use the schconfig utility to set the following parameters:
    • Set the Data Source Name to the scheduler database service name in the tnsnames.ora file.

    • Set the User Name and Password to the user name and password that you use to access the scheduler database.

    • Set the Scheduler Script Path and Default Script Path to locations that reside on a global file system.

    • To simplify setup and to avoid having to use certificates, set the Administrator Password to null.

    • Set Participant in Cluster to True.

    • Set the SAW Machine Name to the physical host name of the Presentation Services component.

    The schconfig utility modifies the BI_DATA_DIRECTORY/scheduler/config/instanceconfig.xml file.

  7. Create the resource.
    # clresource create -g mm-bi-svr-rg \
    -t ORCL.obiee_scheduler \
    -p BI_INSTALL_DIRECTORY=/export/home/obiee/OracleBI \
    -p BI_DATA_DIRECTORY=/export/home/obiee/OracleBIData \
    -p Resource_dependencies_offline_restart=mm-bi-svr-hasp-rs \
    mm-bi-sch-rs
  8. Verify the resource status.
    # clresource status mm-bi-sch-rs
    === Cluster Resources ===
    Resource Name   Node Name        State   Status Message
    -------------   ---------        -----   --------------
    mm-bi-sch-rs    phys-red1:red-zone1  Online  Online
                  phys-red2:red-zone2  Online  Online