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

You can control deployed Essbase server processes using script commands to start, stop, and view component status. Use these scripts to manage Essbase servers without stopping the compute instance.

You use the start.sh or stop.sh scripts to start or stop the WebLogic Administration Server and the Managed Server components. Use these scripts to restart these servers if they crash.
You use the systemctl <start|stop|status> essbase_domain-nodemanager service to start or stop the Node Manager service or to check its status. It's important that the Node Manager service is already running when you are using the start.sh/stop.sh/status.sh scripts.

Control the AdminServer and Managed Servers

The opc user has rights to use sudo to execute the commands shown in these examples. The oracle user does not, but it does have access to the paths of the Essbase cube objects and artifacts. Therefore, Oracle recommends using the opc user, with sudo permissions of oracle, to run the scripts that manage the WebLogic AdminServer and any Managed Server components, as shown in these examples.

As opc user, assume the privileges of the oracle user. Example:
```
sudo su - oracle
```
Navigate to the location of the scripts in the domain tools directory, <Domain Root>/<Domain Name>/esstools/bin/. Example:
```
cd /u01/config/domains/essbase_domain/esstools/bin
```

To check status of servers, run the status script.

./status.sh

In this example, AdminServer and Essbase managed server are running:

$ ./status.sh
.....

Name            Type            Machine                   Status
----            ----            -------                   ------
ess_server1     Server          myhost.example.com       RUNNING
AdminServer     Server          myhost                   RUNNING

If the status script fails with an error, for example, that the connection to Node Manager was refused, check the log to locate the cause of the error.

To stop AdminServer and all managed servers in the Essbase platform, run the stop script without any arguments:
```
./stop.sh
```
To stop a specific server, use the -i option and provide a server name:
```
../stop.sh -i ess_server1
```
To start AdminServer and all managed servers in the Essbase platform, run the start script without any arguments:
```
./start.sh
```
To start a specific server, use the -i option and provide a server name:
```
./start.sh -i ess_server1 
```

Control the Node Manager Process

To start or stop the Node Manager or view its status,

To start the Node Manager, as opc user:
```
sudo systemctl start essbase_domain-nodemanager
```
Note that this command will reconnect the Node Manager to existing administration processes. This command doesn't stop the AdminServer or the managed server(s).
To stop the Node Manager:
```
sudo systemctl stop essbase_domain-nodemanager
```
Note that this command doesn't stop the AdminServer or the managed server(s).
To restart the Node Manager:
```
sudo systemctl restart essbase_domain-nodemanager
```
Note that this command doesn't restart the AdminServer or the managed server(s).

To show status of the Node Manager:

sudo systemctl status essbase_domain-nodemanager