Creating a service level agreement

This lesson shows you how to use the governance enablement profile to create a new service level agreement (SLA), and to submit and approve an SLA request. In this example, the SLA is between the consumer, Commercial Address Formatter application, and the provider, Address Formatter service.

What you should be able to do

At the end of this lesson, you should be able to:
  • Create an SLA.
  • Request the SLA.
  • Approve the SLA request.

Roles participating in this task:

Introduction

The SLA is the technical implementation of the document of understanding (DOU) that allows the context and actual interaction patterns (service level definition, interface, binding, port, endpoints, policies, and so on) to be selected and potentially refined in terms of this particular context. A DOU might cover a number of different SLAs in different contexts or different interaction patterns. The application version consumer, Commercial Address Formatter in this case, is selecting from the subscribable service level definitions that the provider has made available. After the consumer has made their selection, and verified that it provides the necessary quality of service and resource requirements, the provider can negotiate, and thus approve, reject or refine the request. In this way the consumer is selecting the service level definition that best fits their requirement.

Part 1: Creating an SLA

Development

Note: In order to complete this step, the developer must have the WSRRadmin role.
The new SLA is associated with the DOU that was created in the tutorial Creating and approving a document of understanding.
  1. If you have security enabled, and have assigned separate user IDs to each of the governance enablement profile roles, as described in Governing an SCA service: the consumer story, log in to the dashboard with the user ID that is assigned to the Development role. Otherwise, go to the next step.
  2. In the dashboard, switch to the Development view by selecting it in the view list in the title bar. Ensure that the Overview page is selected.
  3. Click the DOU in the Watch List widget to view it details.
  4. In the Detail widget, click the Edit icon (Edit icon).
  5. Click Add Service Level Agreement under the Subscriptions heading and click Create to create a new SLA.
  6. Enter the following details:
    1. Name: SLA - Commercial Address Formatter consumption of Address Formatter
    2. Enter SLAComm128 in the Context Identifier field. This allows the consumer to identify which SLA is in play within a particular relationship with the provider if there are more than one. The naming convention for Context Identifiers is specific to your own enterprise. Additionally, other negotiated characteristics of the agreement can be entered into the SLA, such as Average Messages Per Day, Peak Message Rate. These values will be an agreed subset of the behavior described in the SLD.
    3. Enter values of your choice in the availability and termination date fields.
    4. Click Add Service Level Definition under the Agreed Endpoints heading.
    5. Enter * in the Name field, and click Find.
    6. Select the check box alongside SLD – Address Formatter and click Finish.
    7. Click Finish to save your changes.

Part 2: Requesting the SLA

By requesting the SLA, the development team is effectively asking the provider of the service for permission to use the service level definition associated with the application version.

  • Transition the SLA to the SLA Requested state.
    1. Click SLA - Commercial Address Formatter consumption of Address Formatter under the Subscriptions heading to view its details.
    2. Select Action > Request SLA , and note that the new governance state is SLA Requested.

Part 3: Approving the SLA request

SOA Governance

The provider of the service has the option to approve or reject the request, or ask for it to be revised. Here, the request is approved, which moves it to the Inactive state. This means that the development team that want to consume the service can continue their development based on the consumption of this specific service level definition, but they do not yet have authorization to access any endpoints.

  1. If you have security enabled, and have assigned separate user IDs to each of the governance enablement profile roles, as described in Governing an SCA service: the consumer story, log in to the dashboard with the user ID that is assigned to the Operations role. Otherwise, go to the next step.
  2. In the dashboard, switch to the Operations view by selecting it in the view list in the title bar. Ensure that the Overview page is selected.
  3. Click the SLA in the Watch List widget to view it details.
  4. Transition the SLA to the SLA Inactive state. Select Action > Approve SLA Request , and note that the new governance state is SLA Inactive.

What you did in this tutorial

In this lesson, you completed the following activities:
  • Created an SLA.
  • Submitted an SLA request.
  • Approved the SLA request.