| |
Before you begin
Review Define services and process groups and Define and assign policies.
After you have defined a service and assigned the appropriate policies to the service and its process groups, you need to deploy the service to the resource pools on which it will run. WLOC uses the following placement algorithm when choosing the resource pools for an initial deployment:
The Controller examines the resource requirements, software dependencies, and high-availability requirements that you configured for the service.
The Controller examines all resource pools that are currently active, including those that are hosting other services, and uses the following process of elimination to determine which resource pools are candidates for hosting the service:
If the service requires high availability, resource pools that do not support high availability are eliminated as candidates.
If the service specifies software requirements, resource pools that do not offer access to all of the required software are eliminated as candidates.
If the service consists of a single process, resource pools that offer fewer computing resources than the service's minimum resource requirements are eliminated.
If the service consists of multiple processes, WLOC may use multiple resource pools to run the service.
After this process of elimination, WLOC determines which resource pool or combination of resource pools can be used to host the service. Then, it uses one of the following placement algorithms that you configure, as described in Define general properties for a service, to choose a resource pool or collection of resource pools:
Prefer resource pools with the most resources: WLOC selects the resource pool combination that provides the greatest amount of computing resources.
Prefer resource pools with fewer resources: WLOC selects the resource pool that most closely matches the minimum resource requirements of the service. This algorithm ensures the most efficient use of resources in your data center.
Service States
A service can be configured to be in one of the states defined in the following table. The meaning of the state varies for plain and ESX Agents.
| State | Description |
|---|---|
Undeployed |
Plain Agents: No JVMs are running. ESX Agents: All JVMs have been deleted from the ESX server. |
Staged |
Plain Agents: No JVMs are running. (Same as Undeployed.) ESX Agents: JVMs have been created, but are not running. |
Deployed |
The minimum number (at least) of JVMs associated with the service are running. |
In the Services table, one of the following values displays in the runtime Status column to indicate the current or transitional state.
| Runtime Status Value | Description |
|---|---|
undeployed |
Service state is Undeployed. |
staged |
Service state is Staged. |
deployed |
Service state is Deployed. |
staging |
Service is transitioning from Undeployed to Staged state. |
starting |
Service is transitioning from Staged to Deployed state. |
stopping |
Service is transitioning from Deployed to Staged state. |
destroying |
Service is transitioning from Staged to Undeployed state. |
failed stage |
Service failed to stage. Service state is returned to Undeployed. |
failed start |
Service failed to start. Service state is returned to Staged. |
failed stop |
Service failed to stop. Service state is returned to Deployed. |
failed destroy |
Service failed to destroy. Service state is returned to Staged. |
Note: You configure the number of times WLOC attempts to transition a service to the requested state when defining the service, as described in Define general properties for a service.
Steps to Deploy a Service
To deploy a service:
The list of currently defined services is displayed in the Services table. The Status column indicates the current state of the service.
| Button | Description |
|---|---|
Stage |
Stage the service (and transition it to the Stage state). |
Start |
Deploy the service (and transition it to the Deployed state). If the service is in the Undeployed state, WLOC transitions it to the Staged state and then to the Deployed state. |
Stop |
Stop the service (and transition it to the Unstaged state). If the service is in the Undeployed state, WLOC transitions it to the Staged state and then to the Deployed state. |
Unstage |
Undeploys the service (and transitions it to the Undeployed state). If the service is in the Deployed state, WLOC transitions it to the Staged stage and then to the Undeployed state. |
Note: You can also right-click a service in the Inventory pane for which you want to manage state, and then select one of the options listed above on the context menu. You can also manage all of your service's states simultaneously, but the All Services option is only valid when the context menu is opened at the Services level.
The following confirmation message appears (where
xxx indicates the transition request):
Request to xxx service was successfully sent
At this time, the configured state of the service is changed and WLOC will begin to transition the service toward the new configured state.
After you finish
Perform one or more of the following tasks:
Monitor service performance, as described in Monitor resources.
If the service failed to transition, view the events and pending approvals, as described in Monitor events and pending approvals.
To troubleshoot a failed transition, view the log files, as described in View and configure log and audit messages.
 |
