Use Commands to Start, Stop, and View Status of Processes

Start 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 primary host.
The start command doesn't 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 don't 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 primary host) by running DOMAIN_HOME/bin/startNodeManager.sh. On Windows, don't start Node Manager as a service in a multi-node, clustered deployment because the system doesn't work in this case.

Enter an appropriate command to run the start script located in:
DOMAIN_HOME/bitools/bin

On Linux | 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
```
Use the optional arguments.
- -h<Domain home>
  Use to specify the domain home, includes the domainName directory. The default is DOMAIN_HOME if set.
- -i <startServersList>
  Use 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>
  Use to specify the number of seconds during which the system components can be restarted. The default is 3600, Maximum is 214748647, Minimum is 300.
- -m<restartMaxValue>
  Use to specify the number of times that the Node Manager can restart the System Components within the interval specified in Restart Interval in Seconds. The default is 5000, Maximum is 2147483647, Minimum is 0. If set to 0, then auto restart of system components is disabled.
  
  When you start components using start.sh|cmd and don't use the option -m<restartMaxValue>, the command uses the default value in start.servers.config.json, and sets the maximum number to 5000.
- -c<Clear cached credentials>
  Use to clear and reset the cached Oracle WebLogic Server administrator credentials, prompts for user name and password. Use this argument after you change the default Oracle WebLogic Server administrator password. The password is encrypted and cached for later use in start/stop without user interaction. The default is false.
  
  The Node Manager credentials aren't changed.
If you don't specify any instances as arguments in the command, the Administration Server, Managed Server, and all system components, start by default.
A list of the inactive components to start is displayed.
Components start.

If you don't specify -i, then start starts all inactive processes. It doesn't 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.

Permanently Change the Maximum Number of Attempts for Restarting System Components

You can permanently configure the number of times that the Node Manager tries to restart the System Components.

When System Components started by the Node Manager fail, the process automatically attempts to restart them until the maximum number of restart attempts is reached. The default maximum number of restart attempts is set to 5000, but this default value might be too large in cases when the process keeps failing, and you might want the process to fail sooner to avoid using unnecessary resource consumption in the restart attempts (for example, for CPU, memory, or hard disk generated core files disk consumption). You can permanently decrease the number of times that the Node Manager attempts to restart System Components.

You can permanently configure the startup script to use a maximum restart value that you specify instead of using the default value of 5000. You change the maximum restart value by customizing max_restart_value in the startup script.

Take a backup of the startup script in <oas_home>/bi/modules/oracle.bi.sysman/scripts/start.sh|start.cmd.
Open start.sh|start.cmd for editing and check the max_restart_value.

When max_restart_value is set to -1, it uses the default value 5000, defined in the start.servers.config.json file.

Specify a new default maximum restart value, for example, set the value to 30 as shown below.

# Default System Components Restart values. Indicates that the default should be used
# max_restart_value=-1
max_restart_value=30

Stop and start the System Components to reflect the change.

Note:

As the administrator, you're responsible for making backups and maintaining customizations. Unless specifically noted, patches to the system might overwrite your customizations. Ensure that you back up any files before editing them, and when editing, comment out original code rather than removing it.

Stop Component Processes in a Domain

Learn about 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 primary host.
The stop command continues until all specified component processes are shut down.
The stop command initially prompts for credentials and automatically creates a boot identity file, so that subsequent runs don't require credentials.
Stopping specific process may cause failover, so familiarize yourself with Scale 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 Oracle WebLogic Server.

Enter an appropriate command to run the stop script located in:
DOMAIN_HOME/bitools/bin

On Linux | Windows:
```
./stop.sh | stop.cmd {-i <list of instances>} {-c}
For example, ./stop.sh -i obis1,obips1 
```
Use the optional arguments.
- -h<Domain home>
  Use to specify the domain home including the domainName directory. The default is DOMAIN_HOME if set.
- -i <list of instances>
  Use 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>
  Use to clear and reset the cached Oracle WebLogic Server administrator credentials, prompts for username and password. Use this argument after changing the default Oracle WebLogic Server administrator password. The password is encrypted and cached, for later use in start/stop, without user interaction. The default is false.
  
  Node Manager credentials aren't changed.
If you don't specify any instances as arguments in the command, the Administration Server, Managed Server and all system components shut down by default.
Components shut down.

View the Status of Components in a Domain

Use the status command to view a report displaying the status of components within a domain.

Assumptions

The status command reports node manager status.
The status command only runs from the primary 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 don't require credentials.

Prerequisites

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

Enter an appropriate command to run the status script located in:
DOMAIN_HOME/bitools/bin

On Linux | Windows:
```
./status.sh | status.cmd {-v}

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