Administration and Deployment Guide

Starting and Stopping ALES Components

This chapter details how to start and stop the Administration Server, Security Control Managers, and Security Service Modules on Windows and UNIX systems.

Starting and Stopping the Administration Server On Windows

The Administration Server is installed on Windows as a service application with a default startup type of `manual'. To configure ALES services for automatic startup, use the Windows Services applet.

Starting the Administration Server starts the following services, where name is the machine name:

ALES ARME.admin.server.asi.name
ALES BLM.asi.name
ALES Service Control Manager
ALES WebLogic Server—WLS.asi.name

Table 2-1 lists the command line commands and Start Menu options for managing Administration Server processes. To use a command line, open a command window, navigate to the installation directory, and enter the command.

Table 2-1 Windows Program Menu Options and Commands

Menu Option	Command	Description
Start Server	`WLESadmin start`	Starts Administration Server processes when running under WebLogic, as well as the SCM on the same machine.
	`WLESadmin console`	Starts WebLogic-hosted Administration Server processes in separate console windows. When starting in console mode, a message like the following appears: `08/25/04 18:21:11utc ERR [3040]iomanager.cpp(95): *** Opening ERR Stream ***` This is NOT an error message. It indicates a test to ensure that the server can write to an error log. You must start the SCM separately when using this command.
Stop Server	`WLESadmin stop`	Stops Administration Server processes. When running in console mode, you may also stop a process by closing the console window or pressing Ctrl+C.

Menu Option

Command

Description

Start Server

WLESadmin start

Starts Administration Server processes when running under WebLogic, as well as the SCM on the same machine.

WLESadmin console

Starts WebLogic-hosted Administration Server processes in separate console windows. When starting in console mode, a message like the following appears:

08/25/04 18:21:11utc ERR
[3040]iomanager.cpp(95): *****
Opening ERR Stream *****

This is NOT an error message. It indicates a test to ensure that the server can write to an error log.

You must start the SCM separately when using this command.

Stop Server

WLESadmin stop

Stops Administration Server processes. When running in console mode, you may also stop a process by closing the console window or pressing Ctrl+C.

Starting and Stopping Administration Server on UNIX

The Administration Server is registered with the UNIX init subsystem. By default, it is not configured to start automatically. To configure it for automatic startup, the system administrator must link it into the correct init runlevel.

On Sun Solaris and Linux platforms, you must always start the server as root. A utility, such as SUDO (http://www.courtesan.com/sudo/), can be used to allow non-root users to start and stop it as root without having to give out the root password or violate the Application Security Infrastructure (ASI).

To start and stop Administration Server processes on UNIX, navigate to the install directory and enter the shell script command as listed in Table 2-2.

Table 2-2 UNIX Commands

Command	Description
WLESadmin.sh start or WLESadmin.sh console	Either command starts Administration Server processes as daemon processes. Note: Either command provides the same results.
WLESadmin.sh stop	Stops Administration Server processes. A process can also be stopped by closing the console window or pressing Ctrl+C.

Command

Description

WLESadmin.sh start

WLESadmin.sh console

Either command starts Administration Server processes as daemon processes.

Note: Either command provides the same results.

WLESadmin.sh stop

Stops Administration Server processes. A process can also be stopped by closing the console window or pressing Ctrl+C.

Administration Server Startup Option on Linux

To allow the Administration Server start up after a reboot on Linux, set it to start on runlevel3 (non-graphical runlevel) and runlevel5 (graphical runlevel). To do this, run the following command as root:

chkconfig --level 35 WLESadmin on

The database configuration is available to these scripts on boot so long as configurations are located in the /etc/profile directory. If the configuration is not located in this directory, edit bin/WLESadmin.sh, set the appropriate environment variables and paths before rebooting.

To check the Administration Server runlevel, run:

chkconfig --list WLESadmin

Starting and Stopping SCMs and SSMs on Windows

The SCM is installed on Windows as a service application with a default startup type of `manual'. To configure an SCM for automatic startup, use the Windows Services applet.

Table 2-3 lists the command line commands and Start Menu options for starting/stopping SCMs and SSM instances. To use a command line in Windows, open a command window, go to the SCM or SSM instance install directory, and enter the command.

The SCM must be running before starting the SSM instance. If the SSM instance is on the same machine as the Administration Server, the SCM may have been started when the Administration Server was booted. If the SSM instance is on a different machine, you must first start its SCM.

Table 2-3 Windows Start Menu Options and Commands

Menu Option	Command	Description
Refresh SCM	`WLESscm` refresh	Clears cached configuration data and loads fresh SSM configuration data from the Administration Server.
Start SCM	`WLESscm start`	Starts the Service Control Manager.
Start SCM (console mode)	`WLESscm console`	Starts the Service Control Manager in a console window.
Stop SCM	`WLESscm stop`	Stops the Service Control Manager. In console mode, you may also stop it by closing the console window or pressing `Ctrl+C`.
Refresh ARME	`WLESarme` refresh	Updates the SSM to include the most recent policy data from the Application Server.
Start ARME	`WLESarme` `start`	Starts the SSM instance.
Start ARME (console mode)	`WLESarme console`	Starts the SSM instance in a console window.
Stop ARME	`WLESarme stop`	Stops the SSM instance. In console mode, you may also stop the instance by closing the console window or pressing `Ctrl+C`.

Starting and Stopping SCMs and SSMs on UNIX

To start and stop SCMs and SSM instances on UNIX, go to the bin directory where the SCM or SSM instance is installed and enter the commands listed in Table 2-4. You must start the Service Control Manager before starting the SSM instance.

Note: For an additional SCM start-up option on Linux, see SCM Start-Up Option on Linux.

Table 2-4 Unix Commands

Command	Description
`WLESscm.sh` refresh	Clears cached configuration data and loads fresh Security Service Module configuration information from the Administration Server.
`WLESscm.sh start` or `WLESscm.sh console`	Starts the Service Control Manager as a daemon process. Note: Either command provides the same result.
`WLESscm.sh stop`	Stops the Service Control Manager. The SCM can also be stopped by closing the console window or pressing Ctrl+C.
`WLESarme.sh` refresh	Updates the SSM instance to include the most recent policy data from the Administration Server.
`WLESarme.sh` `start` or `WLESarme.sh console`	Either command starts the SSM instance as a daemon process. Note: Either command provides the same result.
`WLESarme.sh stop`	Stops the SSM instance. You may also close the console window or press `Ctrl+C`.

SCM Start-Up Option on Linux

To allow the SCM to start up after a reboot on Linux, set it to start on runlevel3 (non-graphical runlevel) and runlevel5 (graphical runlevel). To do this, run the following command as root:

chkconfig --level 35 WLESscm on

To check the runlevel of the Service Control Manager, run:

chkconfig --list WLESscm