Providing a service level definition for the service

After completing the scoping and planning information, you must provide a clear statement about the service levels that consumers of this service can access. The service level definition (SLD) provides access to key information classes that are extracted and created when the SCA module was loaded.

In this example, you will associate three different endpoints, each with a different binding, with the SLD; this is acceptable here because the SLD is very simple in terms of its description. However, if each binding has very different qualities of service behavior, each needs its own SLD to describe that behavior; for example, the throughput of a web services binding might be very different to that displayed by a messaging binding.

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 provider story, log in to the web user interface with the user ID that is assigned to the Development role. Otherwise, go to the next step.
2. In the web user interface, switch to the Development perspective, if necessary, by selecting Development from the Perspective list.
3. Create the SLD for the Address Formatter service. This encapsulates the endpoints, protocols and interfaces that consumers can use to access the service.
   1. Click View > Technical Governance > Capability Versions > Service Versions.
   2. Click Address Formatter to display the service version details.
   3. Click New SLD. A new SLD is created called SLD - Address Formatter; this is displayed as a link under the Service Level Definitions relationship.
4. Define the service interface, and hence the functional specification used to interact with the SLD.
   1. Click SLD - Address Formatter to display the SLD details.
   2. Click Edit Relationships.
   3. Click Add Service Interface alongside the Service Interface relationship.
   4. Enter * in the Name field, and click Search.
   5. Select the radio button alongside AddressFormatterInterface, and click Apply Selected Targets.
   6. Click Finish to save your changes.
5. Scope the SLD. This provides the opportunity to define specific requirements or features that must be met. Customized SLDs might have many properties that must be set at this point, but this is not done in this tutorial. (Alternatively, you can create a new SLD under the Provides relationship, selecting the required type from the Entity type list; all details must then be filled in from that point.)
   1. Click Propose Scope, and note the new governance state is SLD Scope Review, and that Approve Scope and Revise Scope buttons are now displayed.
   2. 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 provider story, log in to the Business Space user interface with the user ID that is assigned to the SOAGovernance role. Otherwise, go to the next step.
   3. In the Business Space user interface, switch to the SOA Governance space if necessary, by clicking Go to Spaces > SOAG, and ensure that the Overview page is selected.
   4. In the Watch List (SOA Governance) widget, click SLD – Address Formatter to display the SLD details.
   5. In the Service Registry Detail widget, click Action > Approve Scope, and note that the new governance state is SLD Scoped, and that a Propose Specification transition is now available in the Action menu.
6. Define the named exports, and hence the binding protocols used to access the SLD. In this case, the service exposes itself using three different bindings: MQSeries, Web Services and JMS.
   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 provider story, log in to the web user interface with the user ID that is assigned to the Development role. Otherwise, go to the next step.
   2. In the web user interface, switch to the Development perspective, if necessary, by selecting Development from the Perspective list.
   3. Click Tasks > SLD Tasks > Scoped Service Level Definitions, then click SLD - Address Formatter to display the SLD details.
   4. Click Edit Relationships.
   5. Click Add Service Export alongside the Bound SCA Exports relationship.
   6. Enter * in the Name field, and click Search.
   7. Select the check boxes alongside AddressFormatterMediation_WS, AddressFormatterMediation_JMS, and AddressFormatterMediation_MQ, and click Apply Selected Targets.
7. Define the available endpoints for these three exports. The MQSeries and JMS bindings are displayed as SCA Service Endpoints, and the Web Services binding is displayed as a SOAP Service Endpoint.
   1. Click Add Service Endpoint alongside the Available Endpoints relationship.
   2. Enter * in the Name field, and click Search.
   3. Select the check boxes alongside http://localhost:9080/AddressFormatterWeb/sca/AddressFormatterMediation_WS, jms:jndi:AddressFormatter/AddressFormatterMediation_JMS_RECEIVE_D?jndiConnectionFactoryName=AddressFormatter/AddressFormatterMediation_JMS_CF, and wmq://HOST1:1414/msg/queue/RECQ1@QM123, and click Apply Selected Targets.
   4. Click Finish to save your changes.
8. Complete the SLD specification.
   1. Click Propose Specification, and note the new governance state is SLD Review, and that Approve Specification and Revise Specification buttons are now displayed.
   2. 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 provider story, log in to the Business Space user interface with the user ID that is assigned to the SOAGovernance role. Otherwise, go to the next step.
   3. In the Business Space user interface, switch to the SOA Governance space if necessary, by clicking Go to Spaces > SOAG, and ensure that the Overview page is selected.
   4. In the Watch List (SOA Governance) widget, click SLD – Address Formatter to display the SLD details.
   5. In the Service Registry Detail widget, click Action > Approve Specification, and note the new governance state is SLD Subscribable, and that Supercede and Deprecate transitions are now available in the Action menu. This SLD is subscribable, meaning that service level agreements can now be requested against it.
9. View the service level definition structure.
   1. In the Service Registry Detail widget, click Action > View in Graphical Explorer.
   2. Examine the structure of the Address Formatter service, and its relationship to the service level definition and the information defined in the original SCA module.
10. Complete the Address Formatter service specification.
    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 provider story, log in to the web user interface with the user ID that is assigned to the Development role. Otherwise, go to the next step.
    2. In the web user interface, switch to the Development perspective, if necessary, by selecting Development from the Perspective list.
    3. Click View > Technical Governance > Capability Versions > Service Versions.
    4. Click Address Formatter to display the service version details.
    5. Click Propose Specification, and note the new governance state is Specification Review, and that Approve Specification and Revise Specification buttons are now displayed.
    6. Click Approve Specification, and note the new governance state is Specified, and that a Propose Realization button is now displayed.
11. Complete the Address Formatter service realization.
    1. Click Propose Realization, and note the new governance state is Realization Review, and that Approve Realization and Revise Realization buttons are now displayed.
    2. Click Approve Realization, and note the new governance state is Realized, and that a Propose Staging Deployment button is now displayed.

    At this point in the lifecycle, you are ready to register the endpoints that are used in any given environment, and to enable the endpoints as the service completes its lifecycle.