![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This chapter details how to start and stop the Administration Server, Security Control Managers, and Security Service Modules on Windows and UNIX systems.
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 service, where name is the machine name:
Table 3-1 lists the command line commands and Start Menu options for managing Administration Server processes. To use these commands, open a command window, navigate to the installation directory, and enter the command.
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.
To start and stop Administration Server processes on UNIX, navigate to the install directory and enter the shell script command as listed in Table 3-2.
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
, setting the appropriate environment variables and paths before rebooting.
To check the Administration Server runlevel
, run:
chkconfig --list WLESadmin
![]() ![]() ![]() |