Starting and Stopping Services

In order to start services, the following configuration files must be updated for the specific site configuration:

$NMS_HOME/etc/system.dat.model_build

$NMS_HOME/etc/system.dat

$NMS_HOME/etc/system.dat.init

Starting Services

To start services, complete these steps:

1. Login to the server machine as the Oracle Utilities Network Management System Admin user.

2. Enter:

sms-start

SMService starts. It reads and caches the system.dat file by default and starts the remaining services based on the data it just cached.

Note: Using the -f [filename] option with sms-start will override the default behavior and SMService will cache the specified file instead (for example, system.dat.init or system.dat.model_build).

Stopping Services

• To stop clients:

sms‑stop -c

Stop all user sessions with the -c option, which notifies Web Workspace clients that the administrator is forcing an exit. The session stops immediately if users acknowledge the dialog box or automatically after a 5 second delay.

• To stop services:

sms‑stop -s

When stopping services, you may have other tools running. The services are the core dependencies of all applications, so when services are stopped, all tools should be stopped and then restarted after the services have been re-launched.

• To stop both clients and services:

sms‑stop -a

Note: Occasionally, there are tools or isis processes that may continue to exist as defunct and/or hung processes after the above commands do (or do not) run to completion. Check the process list on the Unix machines for these processes and kill them prior to restarting. Otherwise, otherwise the system may not restart properly.

• To set all users as logged out in the CES_USER_LOG table:

sms‑stop -u

Note: This should only be done when all users are told to stop their processes.

Starting and Stopping the WebLogic Managed Server

Additional scripts are provided to start and stop the WebLogic managed server individually and in parallel with starting or stopping services. These require configuration from the nms‑wls‑config script.

nms‑wls‑config

Generates the configuration files required for nms‑wls‑control, nms‑all-start, and nms‑all‑stop. This scripts prompts for WebLogic Admin Server credentials. If not provided on the command line, it prompts for the admin server URL and managed server name as well. Credentials are stored encrypted in $NMS_HOME/etc/wls in the format used by the WLST storeUserConfig function.

Usage: nms-wls-config [-a ADMINSERVER] [-s SERVER]

Configure WebLogic Connect

Optional arguments:

-h, --help show this help message and exit

-a ADMINSERVER, --admin ADMINSERVER

URL of the adminserver. This is of the form

t3:/hostname:7001

t3s:/hostname:7002

-s SERVER, --server SERVER Name of the managed server

nms-wls-control

Uses the WebLogic Scripting tool to start or stop the WebLogic managed server associated with an NMS environment. This requires configuration created by the nms-wls-config script.

Usage: nms-wls-control start | stop

nms-all-start

Starts NMS services and the WebLogic managed server in parallel using sms-start and nms-wls-control. This requires configuration created by the nms-wls-config script.

Usage: nms-all-start

nms-all-stop

Stops NMS services and the WebLogic managed server in parallel using sms-stop and nms-wls-control. This requires configuration created by the nms-wls-config script.

Usage: nms-all-stop