Releasing Services

Releasing a service means advancing it to completion.

  • If a completion workflow is configured, releasing a component advances it to the completion workflow process.
  • If a completion workflow isn't configured, once all components in a service are deployed, releasing the components makes the service visible to the requester (for example, the Service Portal user).

By default, the Release checkbox is enabled in the manual deployment wizard, so that components advance to completion automatically. However, if there are manual steps in your provisioning process, you may want to disable the Release checkbox so that you can carry out these steps before the completion workflow starts. For example, you may need to install software, check operating system patches, or migrate VMs (with vMotion or Storage vMotion).

Note: When you set up automated deployment of approved service requests, VMs and virtual services are automatically released after deployment.

Manually releasing services after deployment

If a service is in the "Deployed" state but has not been released as part of the deployment process, you can release it manually.

Access through:

Views > Service Requests

Available to:

Administrator, Operator with Approval, Operator Access Rights

To manually release a service after deployment:

  1. Do one of the following:
    • Select the request in the list of Service Requests and click Request Details.

      OR

    • In the Infrastructure or Applications view, right-click the service and select Provisioning > View Service Request.
  2. In the Request Details dialog, navigate to the service in the tree then in the Details tab, click Release.
  3. Add a comment as required and click OK.
  4. Tip: You can also click Service Requests in the shortcut menu toolbar.