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 and remotely (on clustered servers) if not already running.

  • The start command runs only from the master host.

  • The start command does not complete until component processes are either started or fail consecutively to start the number of times specified by 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.

Prerequisites

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

To start component processes running in a domain using a command:

  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. An instance can be the administration server, a managed server or a system component instance name.

    -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. Note: 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 username and password. Use this parameter after changing the default WebLogic Server administrator password. The password will be encrypted and cached (as before), for later use in start/stop, without user interaction. Default is false.

    Note: 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. Component(s) 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 server(s), 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.

Prerequisites

  • Node Manager must be running.

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

To stop component processes running in a domain using a command:

  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 will be encrypted and cached (as before), for later use in start/stop, without user interaction. Default is false.

    Note: 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. Component(s) 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.

Pre-requisites

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

To view the status of Oracle Business Intelligence components in a domain using a command:

  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.