Admin ServiceOptimizer Further Detail Scripts and Utilities UNIX

Script/Utility Description StartUp Requirements Termination Requirements Logfiles

startup

The purpose of this script is to start the System Monitor and check that various environment variables are set.

The script spstart will start spsysmon, which will start all the named processes in the database if it is the master system monitor (see Admin ServiceOptimizer Further Detail Core Processes System Monitor).

A sample script will be supplied for spstart, which will need to be tailored for a particular ServiceOptimizer instance. In particular the database and password will need to be provided (this is not part of the environment).

Parameter	Options	Description
[-h]	-	Print usage message

ServiceOptimizer can be started up and shutdown automatically using the Unix 'cron' facilities.

The spstart script should be run in foreground when starting
manually from the command line.

The script will start the System Monitor then terminate.

A log file is produced, recording incorrect environment variables, in $SPHOME/<instancename>/log.

It is named

<instance>.<node>.spstart.<MMMDDHHMMSS>

Start-Up on Boot

The purpose of this script is to start the System Monitor on system boot. A sample script (SERVICEPowerInst) is supplied. This must be tailored (as described within the script itself) and placed in directory /etc/init.d on Solaris or /sbin/init.d on HPUX.

A link ( SxxxServiceOptimizer) to the script must be placed in directory /etc/rc3.d on Solaris or /sbin/rc3.d on HPUX. The xxx should be changed to a number that defines the order of running the scripts in that directory.

It should be set such that the database system is started before the ServiceOptimizer system starts.

Starting ServiceOptimizer during system reboot should be done at level 3 typically, when all necessary services required to support ServiceOptimizer have been started. The script calls spsysmon via nohup as a background process. This must be done with the correct runtime environment set-up.

Parameter options are start and stop.

None

The process will start the System Monitor then terminate.

A lofgile is produced:

$SPHOME/<instancename>/log/<instance>.<node>.SxxxSERVICEOptimizer.log

listing any success or failure messages.

Shut-Down

The script spstop will ask spsysmon to close down all the ServiceOptimizer processes. If this is not achieved within a certain time, it will try to close down the offending processes gracefully. If one or more processes will not close down, spsysmon will keep trying to close them down gracefully. After a certain number of attempts at this, spstop will use a 'hardkill' to terminate any still running processes.

A sample spstop script is supplied.

Parameter	Options	Description
[-h]	-	Print usage message

The spstop script should be run in foreground when starting
manually from the command line.

The script will stop the System Monitor then terminate.

A log file is produced, in $SPHOME/<instancename>/log.

It is named <instance>.<node>.spstop.<MMMDDHHMMSS>

It records whether the ServiceOptimizer system was successfully shut down.

Shut-down on System Shut-Down

The purpose of this script is to stop the System Monitor and thereby cause SERVICEOptimizer to close down on system shutdown. A sample script ( SERVICEPowerInst) is supplied which must be tailored (as described within the script itself) and placed in directory /etc/init.d on Solaris or /sbin/init.d on HPUX.

A link (KxxxSERVICEOptimizer) to the script must be placed in directory /etc/rc3.d on Solaris or /sbin/rc3.d on HPUX. The xxx should be changed to a number that defines the order of running the scripts in that directory.

Parameter options are start and stop.

None

The script will shut down the System Monitor (and, thereby, the rest of the ServiceOptimizer system) then terminate.

A lofgile is produced:

$SPHOME/<instancename>/log/<instance>.<node>.KxxxSERVICEOptimizer.log

listing any success or failure messages.