Use this page to confirm that you want to start or stop a region.
- START
- Click this to start the region. Clicking this opens the Region Start Options dialog box. Specify the options you require,
and then click OK.
- STOP
- Click this to stop the region. Clicking this opens the Region Stop Options dialog box. Specify the options you require, and
then click OK.
- Mark as Stopped
- Check this if you know that all the processes for this server are already stopped.
Region Start Options
- Cold Start
- Click this to cold start a
Performance and Availability Cluster (PAC), this will remove all existing data from each
Scale-Out Repository (SOR) in the
PAC. If an region is cold started and another instance is already running in the same
PAC, then the start will be changed to a warm start.
- Use current user credentials
- Start the region as the user you have already logged in as.
- User Name
- Username of the user you want to use to start the region.
- Password
- Password of the user you want to use to start the region.
Region Stop Options
- Clear dynamically assigned server address values
- Check this to indicate that you want addresses and port numbers that were dynamically assigned when you created new communications
processes and listeners to be cleared.
- Use "Force stop" option
- Check this if you want to perform a forced shutdown of the server.
- Use current user credentials
- Stop the region as the user you have already logged in as.
- User Name
- Username of the user you want to use to stop the region.
- Password
- Password of the user you want to use to stop the region.
Note: When an enterprise server starts or stops, it connects to Directory Server to obtain its configuration details and, later
in the start or stop process, to update Directory Server information. To do this, it requires Directory Server user credentials,
that is, credentials that Directory Server will verify and authorize. In order to update the Directory Server information,
this user must be granted modify permission on the appropriate enterprise server resource within Directory Server.
The start or stop process also requires user credentials that the enterprise server will verify and authorize. In order to
run the command used to start or stop the enterprise server, the user must have Alter permissions on the casstart resource
within the OPERCMDS resource class.
It is important to note that the enterprise server is a separate security domain from the Directory Server. For example,
it may be using different security configuration and different security managers.
You can specify that startup or stop should use built-in default users or the credentials with which you are currently logged
on to Enterprise Server Common Web Administration. Alternatively, you can specify a different username and password.
If you use the currently logged on user, or specify alternative user credentials, you must ensure that the user is present
in both the Directory Server and the enterprise server security domains. Within the Directory Server domain, the user must
have modify permission on the appropriate enterprise server resource within the Servers resource class. Within the enterprise
server security domain, the user must have alter permissions on the casstart resource within the OPERCMDS resource class.
Region Processes Status
[1]
The
Region Processes bar indicates at which stage of the starting and stopping process the region is at. The Directory Server initiates the starting
and stopping processes and queries the status at specific stages.
Communication Process Status
[1]
The
Communication Process bar(s) indicate the status of each Communication Process used by the region. It indicates if the Communications Processes
are started, and each listener owned by it. A disabled listener will not attempt to start, this state is indicated by red
bar. A pending listener needs to be started from the Listeners page, but until then it is displayed as a yellow bar.
Monitoring and Control Access Status
[1]
The
Monitoring and Control Access bar indicates if
ESCWA can communicate with the monitoring and control elements of the region (formerly known as ESMAC). This will display
Stopped if
ESCWA cannot contact it,
Starting if monitoring and control is initiating, and
Started if the region is fully initiated and any correctly configured region features are started.
Region Features Status
[1]
The
Region Features indicators display the status of each feature for the region:
- When monitoring and control access cannot be contacted, the indicators will be blank.
- If it is starting and any of the MSS, JES, IMS, and MQ features have been enabled, the indicators for these will be displayed
as a yellow bar.
- If it is started and any of the MSS, JES, IMS, and MQ features have been enabled but have not been configured correctly,
the bars will be red to indicate that these features are not enabled as expected.
- If it is started and any of the MSS, JES, IMS, and MQ features have been enabled and have been correctly configured, or TRANCLASS
and CWS have been configured on the region, the bars will be green to indicate that these features are enabled as expected.