Administration Application Guide
This chapter details how to start and stop processes and services on both the Administration Server and Security Service Modules.
Both the Service Control Manager and the Administration Server are registered with the Windows Service Manager. On install, they are not configured to start automatically. To have them start automatically, the system administrator must toggle the Manual start to Automatic in Windows. On Windows, to set services to start automatically, click Start>Settings>Control Panel>Administrative Tools>Services, and toggle the Startup Type from Manual to Automatic for each service that has a WLES
Description prefix. Starting the Administration Server starts the following services, where name is the name of the machine on which you installed the product:
Table 6-1 lists the commands and Program menu options you use to manage Administration Server processes. To use commands to start and stop processes on Windows, open a command window, go to BEA_HOME\wles42-admin\bin
(for Administration Server commands) or BEA_HOME\wles42-scm\bin
(for Service Control Manager commands) and enter the command. Verify your services have started properly by checking the Services option in Windows.
Both the Service Control Manager and the Administration Server are registered with the Unix init subsystem. On install, they are not configured to start automatically. To have them start automatically, the system administrator link them into the correct init runlevel in Unix.
On Sun Solaris and Linux platforms, you must always start these servers as root. A common utility called SUDO
(http://www.courtesan.com/sudo/) or something similar can be used to allow non-root users to start and stop these processes as root without having to give out the root password or violate the Application Security Infrastructure (ASI). Table 6-2 lists the services for Sun Solaris and Linux platforms.
Note: To start and stop processes on Unix, go to BEA_HOME/wles42-admin/bin
(for Administration Server commands or BEA_HOME/wles42-scm/bin
(for Service Control Manager commands) and enter the shell script command as listed in Table 6-2.
On Linux platforms, to allow the Administration Server start up after a reboot, you must properly set it to run on the proper init runlevel. This is not done by default. To properly register the Administration Server to start on boot, you must tell it to start on runlevel 3 and runlevel5, where runlevel 3 is the non-graphical runlevel and runlevel 5 is the graphical runlevel. A server comes up and goes into runlevel 3 or 5 depending upon the configuration. To register the Administration Server on Linux, run the following command as root:
chkconfig --level 35 WLESadmin on
Note: The database configuration is available to these scripts on boot. The scripts use configurations located in the /etc/profile
directory, where many database configurations are put. If you do not put the database configuration in /etc/profile
, edit bin/WLESadmin.sh
to set the appropriate environment variables and paths before rebooting.
To check the runlevel of the Administration Server, run:
chkconfig --list WLESadmin
After you install the Security Service Module, create the instance, and enroll it, you must start the necessary processes by running the appropriate batch or shell scripts. Before you start these processes, make sure that the Administration Server and all of its services are running.
For each machine, you must start the following processes:
For instructions on how to start the required processes, see the following sections:
There are two components that must be started for Security Service Module to function properly: the SCM process and the ARME process. You can use either the program menu options or the commands (listed in Table 6-3) to start these processes:
Note: To verify these services have started properly, check the Services option in Windows.
The Service Control Manager is registered with the Windows Services manager. On install, it is not configured to start automatically. To have it start automatically, the system administrator must toggle the Manual start to Automatic in Windows. The Authorization and Role Mapping Engine (ARME) is also not registered with the Windows Services manager. On Windows, to set the Service Control Manager to start automatically, click Start>Settings>Control Panel>Administrative Tools>Services, and toggle the Startup Type from Manual to Automatic for the WLES Service Control Manager
.
Note: If you have installed the Security Service Module on the same machine as the Administration Server, you do not need to start the SCM; it is already started when you boot the Administration Server. If you installed the Security Service Module on a different machine, you must start the SCM and then the ARME process.
Table 6-3 lists the commands and program menu options you use to start and stop processes for a Service Control Manager and Security Service Module ARME instance. To use commands to manage processes on Windows, open a command window, go to BEA_HOME\wles42-scm\bin
(for Service Control Manager commands) or to use ARME commands, open a command window, go to BEA_HOME\wles42-ssm\<
ssmtype
>-ssm\instance\instancename\bin (
where <
ssmtype
>
is either java, iis, wls
, or webservice)
, and enter the command as shown in Table 6-3. Verify your services have started properly by checking the Services option in Windows.
Note: You must start the Service Control Manager before starting the ARME process.
To start and stop processes on Unix, go to /opt/beahome/wles42-ssm/<
ssmtype
>-ssm/bin (
where <
ssmtype
>
is either apache, java
, wls
, or webservice)
, and enter the commands listed in Table 6-4.
Note: You must start the Service Control Manager before starting the ARME process.
Note: For an additional Linux platform start-up option, see Start-Up Option on Linux Platforms.
On Linux platforms, to allow the Service Control Manager to start up after a reboot, you must set it to the proper init runlevel. This is not done by default. To properly register the Service Control Manager to start on boot, set it to start on runlevel 3 and runlevel 5, where runlevel 3 is the non-graphical runlevel and runlevel 5 is the graphical runlevel. A server comes up and goes into the appropriate runlevel depending upon the configuration. To register the Service Control Manager on Linux, run the following command as root:
chkconfig --level 35 WLESscm on
To check the runlevel of the Service Control Manager, run:
chkconfig --list WLESscm