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.

1. Create the service level definition (SLD) for the Catalog Search service. This contains the endpoints and definitions that consumers can use to access the service.
   1. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the WSRR web user interface with the user ID that is assigned to the Development role.
   2. In the web user interface, switch to the Development perspective by selecting Development from the Perspective list.
   3. Click View > Technical Governance > Capability Versions > Service Versions.
   4. Click Catalog Search to display the service version details.
   5. Click New SLD. A new SLD is created called SLD – Catalog Search; this is displayed as a link under the Service Level Definitions relationship.
2. Define the service interface including the functional specification used to interact with the SLD.
   1. Click SLD – Catalog Search to display the SLD details.
   2. Click Edit Relationships.
   3. Click Add Service Interface alongside the Service Interface relationship.
   4. In the Name field, enter *, and click Search.
   5. Select the radio button alongside CatalogServiceInterface, and click Apply Selected Targets.
   6. Click Finish to save your changes.
3. 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 Service Level Definitions relationship, selecting the required type from the Entity type list; completing all of the remaining details.
   1. Click Propose Scope. The new governance state is SLD Scope Review, and the Approve Scope and Revise Scope buttons are now displayed.
   2. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the Business Space user interface with the user ID that is assigned to the SOAGovernance role.
   3. In the Business Space user interface, switch to the SOA Governance space if necessary, by clicking Go to Spaces > SOAG.
   4. Ensure that the Overview page is selected.
   5. In the Watch List widget, click SLD – Catalog Search. The displayed page changes to the Browse page.
   6. In the Service Registry Detail widget, click Action > Approve Scope. The new governance state is SLD Scoped, and the Propose Specification action is now available in the Action menu.
4. Define the available endpoint that is currently deployed, and that can be reached for this SLD.
   1. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the WSRR web user interface with the user ID that is assigned to the Operations role.
   2. In the web user interface, switch to the Operations perspective, if necessary, by selecting Operations from the Perspective list.
   3. Click View > Technical Governance > Capability Versions > Service Versions.
   4. Click Catalog Search to display the service version details.
   5. Click SLD – Catalog Search to display the SLD details.
   6. Click Edit Relationships.
   7. Click Add Service Endpoint next to the Available Endpoints relationship.
   8. In the Name field, enter *.
   9. Click Search.
   10. Select the check box alongside http://CSProductionHost:9443/services/catalog/ and http://CSStagingHost:9081/services/catalog/, and click Apply Selected Targets.
   11. Click Finish to save your changes.
5. Associate the SLD with the REST Service The SLD needs to be associated with the implementation of the REST service, Catalog Search.
   1. Click Edit Relationships.
   2. Click Add REST Service next to the Bound REST Services relationship.
   3. In the Name field, enter *.
   4. Click Search.
   5. Select the check box for Catalog Search
   6. Search and click Apply Selected Targets.
   7. Click Finish to save your changes.
6. Complete the SLD specification.
   1. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the WSRR web user interface with the user ID that is assigned to the Development role.
   2. In the web user interface, switch to the Development perspective by selecting Development from the Perspective list.
   3. Click View > Technical Governance > Capability Versions > Service Versions.
   4. Click Catalog Search to display the service version details.
   5. Under the Service Level Definitions relationship, click SLD – Catalog Search to display the SLD details.
   6. Click Propose Specification. The new governance state is SLD Review, and the Approve Specification and Revise Specification buttons are now displayed.
   7. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the Business Space user interface with the user ID that is assigned to the SOAGovernance role.
   8. In the Business Space user interface, switch to the SOA Governance space if necessary, by clicking Go to Spaces > SOAG.
   9. Ensure that the Overview page is selected.
   10. In the Watch List widget, click SLD – Catalog Search. The displayed page changes to the Browse page, and the details of the SLD are shown in the Service Registry Detail widget.
   11. In the Service Registry Detail widget, click Action > Approve Specification. The new governance state is SLD Subscribable, and the Supercede and Deprecate actions are now available in the Action menu. This SLD is subscribable, meaning that service level agreements can now be requested against it.
7. View the service level definition structure.
   1. In the Service Registry Navigator widget, review the structure of the Catalog Search.
   2. In the Service Registry Detail widget, click Action > View in Graphical Explorer.
   3. Review the structure of the Catalog Search service, and its relationship to the service level definition.
8. Complete the Catalog service specification.
   1. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the WSRR web user interface with the user ID that is assigned to the Development role.
   2. In the web user interface, switch to the Development perspective by selecting Development from the Perspective list.
   3. Click View > Technical Governance > Capability Versions > Service Versions.
   4. Click Catalog Search to display the service version details.
   5. Click Propose Specification. The new governance state is Specification Review, and the Approve Specification and Revise Specification buttons are now displayed.
   6. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the Business Space user interface with the user ID that is assigned to the SOAGovernance role.
   7. In the Business Space user interface, switch to the SOA Governance space if necessary, by clicking Go to Spaces > SOAG.
   8. Ensure that the Overview page is selected.
   9. In the Watch List widget, click Catalog Search (1.0). The displayed page changes to the Browse page, and the details of the Catalog service are shown in the Service Registry Detail widget.
   10. In the Service Registry Detail widget, click Action > Approve Specification. The new governance state is Specified, and the Propose Realization action is now available in the Action menu.
9. Complete the Catalog service realization. Because the service is already deployed, any deployed or installable assets are linked during this stage.
   1. Optional: If you have security enabled and have assigned separate user IDs for each of the governance enablement profile roles, as described in Governing an existing service, log in to the WSRR web user interface with the user ID that is assigned to the Development role.
   2. In the web user interface, switch to the Development perspective by selecting Development from the Perspective list.
   3. Click View > Technical Governance > Capability Versions > Service Versions.
   4. Click Catalog Search to display the service version details.
   5. Click Propose Realization. The new governance state is Realization Review, and the Approve Realization and Revise Realization buttons are now displayed.
   6. Click Approve Realization. The new governance state is Realized, and the Propose Staging Deployment button is now displayed.