2 Managing Oracle Business Intelligence Processes

This chapter describes managing Oracle Business Intelligence processes and includes the following sections:

About Managing Oracle Business Intelligence Processes

System administrators start and stop the Oracle Business Intelligence system and component processes to perform a range of maintenance operations that require process downtime.

Understanding the state (that is, up, down, starting, and stopping) of each component in the Oracle Business Intelligence system is an essential activity when diagnosing and resolving availability and performance issues, and when performing life-cycle and management operations. See Diagnosing and Resolving Issues in Oracle Business Intelligence.

Oracle Business Intelligence runs within Oracle WebLogic Server, and therefore Oracle WebLogic Server must be started before Oracle Business Intelligence components can be started and maintained.

To make changes to server configuration settings, the Business Intelligence Catalog, the repository (.rpd file offline), and other settings, you must restart the appropriate Oracle Business Intelligence components before those changes can take effect.

When you stop Oracle Business Intelligence, end users are logged out, and when ready, the system prompts you to log in again, ensuring session state consistency.

For information about the Oracle Business Intelligence installed components, see Oracle Business Intelligence Components.

Conditions for Starting the Oracle Business Intelligence System

Starting the Oracle Business Intelligence system begins with the Administration Server, then the Managed Servers, and the system components.

If the computer that hosts the Administration Server is not running or has been rebooted, then you must ensure that the computer is running and you must start the Oracle Business Intelligence system.

To start the Oracle Business Intelligence system, the repository database (which contains Scheduler schemas) that was specified during installation must be running, and a network connection to it must be available. Otherwise, error messages are displayed.

The procedure for starting the system differs slightly depending on the platform, as described in the following sections.

Using Commands to Start, Stop, and View Status of Oracle BI EE Processes

Several components of the software can be controlled using script commands.

You use script commands to start, stop, and view status of Oracle Business Intelligence components.

Starting Oracle Business Intelligence Component Processes in a Domain

Learn about how to start all component processes within a domain.

Assumptions

  • The start command starts Node Manager locally if not already running.

  • The start command runs only from the master host.

  • The start command does not complete until component processes are started or fail consecutively to start the specified number of times in the restartMaxValue parameter (-m).

  • Component processes start in order.

  • The command initially prompts for credentials and automatically creates a boot.properties file, so that subsequent runs do not require credentials.

  • You must have file system permissions, and know the boot identity credentials.

  • If the system is clustered across multiple servers, then the Node Manager on each server must be manually started (aside from the master host) by running DOMAIN_HOME/bin/startNodeManager.sh

  1. Enter an appropriate command to run the start script located in:

    DOMAIN_HOME/bitools/bin

    On UNIX | Windows:

    ./start.sh | start.cmd {-noprompt} {-i <list of instances>} {-r <restartIntervalSeconds>} {-m <restartMaxValue>} {-r <restartIntervalSeconds>} {-c}

For example, ./start.sh -i obis1,obips1 -r 10,000 -m 30 -c
    Argument Description

    -h<Domain home>

    (optional) Enables you to specify the domain home, includes the domainName directory. Default is DOMAIN_HOME if set.

    -i <startServersList>

    (optional) Enables you to specify instances to start up in a comma-separated list. You can use the administration server, a managed server or a system component instance name as the instance.

    -r<restartIntervalSeconds>

    (optional) Specifies the number of seconds during which the system components can be restarted. Default is 3600, Maximum is 214748647, Minimum is 300.

    -m<restartMaxValue>

    (optional) Specifies the number of times that the Node Manager can restart the System Components within the interval specified in Restart Interval in Seconds. Default is 2, Maximum is 2147483647, Minimum is 0. If set to 0, then auto restart of system components is disabled.

    -c<Clear cached credentials>

    (optional) Clears and resets the cached WebLogic administrator credentials, prompts for user name and password. Use this parameter after changing the default WebLogic Server administrator password. The password is encrypted and cached as before, for later use in start/stop, without user interaction. Default is false.

    The Node Manager credentials are not changed.

    If no instances are specified as arguments in the command, the administration server, managed server, and all system components, are started by default.

  2. A list of the inactive components to be started is displayed.
  3. Components are started.

    If you don't specify -i, then start will start all inactive processes. It does not fail if something is already running.

    The administration server, managed servers, local and remote node managers, and system components are started.

    The number of started components is displayed.

    The status of all components is displayed.

Stopping Oracle Business Intelligence Component Processes in a Domain

This section describes how to stop running component processes within a domain.

Assumptions

  • The stop command stops Node Manager locally and remotely on clustered servers in the command.

  • The stop command runs only from the master host.

  • The stop command continues until all specified component processes are shutdown.

  • The stop command initially prompts for credentials and automatically creates a boot identity file, so that subsequent runs do not require credentials.

  • Stopping specific process may cause failover, so familiarize yourself with Scaling Your Deployment.

Node Manager must be running. The nodemanager.properties file must include QuitEnabled=true.

You must have file system permissions, and know the system administrator identity credentials to boot WebLogic Server.

  1. Enter an appropriate command to run the stop script located in:

    DOMAIN_HOME/bitools/bin

    On UNIX | Windows:

    ./stop.sh | stop.cmd {-i <list of instances>} {-c}
For example, ./stop.sh -i obis1,obips1
    Argument Description

    -h<Domain home>

    (optional) Enables you to specify the domain home includes the domainName directory. Default is DOMAIN_HOME if set.

    -i <list of instances>

    (optional) Enables you to specify instances to shut down in a comma-separated list. An instance can be the administration server, a managed server or a system component instance name.

    -c<Clear cached credentials>

    (optional) Clears and resets the cached WebLogic administrator credentials, prompts for username and password. Use this parameter after changing the default WebLogic Server administrator password. The password is encrypted and cached as before, for later use in start/stop, without user interaction. Default is false.

    Node Manager credentials are not changed.

    If no instances are specified as arguments in the command, the administration server, managed server and all system components are shutdown by default.

  2. Components are shut down.

Viewing the Status of Oracle Business Intelligence Components in a Domain

The status command displays a status report for components within a domain.

Assumptions

  • The status command reports node manager status.

  • The status command only runs from the Master Host.

  • The status command requires the local node manager process to be running.

  • The first run prompts you for credentials, and automatically creates a boot identity file so that subsequent runs do not require credentials.

Prerequisites

You must have file system permissions, and know the boot identity credentials.

  1. Enter an appropriate command to run the status script located in:

    DOMAIN_HOME/bitools/bin

    On UNIX | Windows:

    ./status.sh | status.cmd {-v}

where {-v} is verbose
  2. The command displays component name, type, status, and machine name.

Using Fusion Middleware Control to Start and Stop BI System Component Processes

If the Oracle Business Intelligence system has been started, then you can start, stop, and restart the Oracle Business Intelligence system component processes, using Fusion Middleware Control.

If Fusion Middleware Control is not available, then see Using Commands to Start, Stop, and View Status of Oracle BI EE Processes.

  1. Go to the Overview page, as described in Displaying Oracle Business Intelligence Pages in Fusion Middleware Control.
  2. Display the Processes tab of the Availability page, then either click Start All, or Stop All, Restart All buttons for all processes, or select a process row and use the appropriate button to start, stop, or restart an individual process as appropriate, as shown in the following illustration.

    You also use this page to view the status of system components.

    Description of GUID-5F56F666-758B-4B24-AEC3-5E54497CACA1-default.gif follows
    Description of the illustration GUID-5F56F666-758B-4B24-AEC3-5E54497CACA1-default.gif

You can use other methods to start and stop Oracle Business Intelligence processes:

Using Fusion Middleware Control to Start and Stop Java Components

Use this topic to monitor status and start and stop Oracle Business Intelligence Java components (Administration Server and Managed Servers) using Fusion Middleware Control.

You can also display the WebLogic Server Administration Console to manage Java components by choosing a menu option on the WebLogic Domain menu.

  1. Log in to Fusion Middleware Control.
  2. Expand the WebLogic Domain folder and select the bidomain node.

    Fusion Middleware Control displays the WebLogic Domain home page, as shown in the following illustration.

    Description of GUID-B251795C-4EF4-4B1D-8B4A-DF74499367B7-default.gif follows
    Description of the illustration GUID-B251795C-4EF4-4B1D-8B4A-DF74499367B7-default.gif

    The WebLogic Domain home page is the starting point for monitoring status of servers, clusters, deployments, and partitions and for starting and stopping Oracle Business Intelligence Java components using Fusion Middleware Control. You can also click a menu option to display the WebLogic Server Administration Console, where you can manage and configure Oracle Business Intelligence Java components. See Managing Oracle Business Intelligence Java Components Using the Oracle WebLogic Server Administration Console.

  3. Using the WebLogic Domain home page, you can perform the following Oracle Business Intelligence management tasks:

Using Oracle WebLogic Server Administration Console to Start and Stop Java Components

In the event the standard methods for starting and stopping Java components cannot be used, you can use the Oracle WebLogic Server Administration Console.

It is not recommended to use Oracle WebLogic Server Administration Console to start and stop Java components. You can also use or Fusion Middleware Control to start and stop Java components (see Using Fusion Middleware Control to Start and Stop BI System Component Processes).

  1. Start the Oracle WebLogic Server Administration Console.
  2. In the Domain Structure region, click Deployments.
  3. The Oracle WebLogic Server Administration Console displays the Summary of Deployments page.
  4. Display the Control tab.
  5. Select a check box for each component to start or stop.
  6. Click Start or Stop to start or stop the selected components as required, as shown in the following illustration.