Governing an existing REST service
This tutorial shows you how to use the service management profile to govern an existing REST service, and control its visibility and use across the organization.
What you should be able to do
At the end of this tutorial, you should be able to:- Register an existing REST service and its REST service interface, along with its endpoints, in WSRR.
- Identify and define the business capability that the service provides.
- Provide a complete specification of the existing service version, including the service level definition, that can be consumed by other services.
- Complete the service lifecycle to ensure that the service endpoints are visible and enabled in the various environments.
Introduction
The use of REST for interactions between consumers and providers has become more commonly used. There are many competing specifications available for representing REST in the marketplace. The REST model is not a representation of any single specification; instead, it represents the concepts relevant to governance. WSRR provides guidance about how to govern REST systems and is flexible enough that you can do what you need to do with that representation. This tutorial examines how this is achieved.
- The description of the interface. The description can be modeled in detail by using the format of one of the REST specifications, or it can be a simple text description contained in a governed document. The WSRR REST model implements a REST service interface.
- Representation of the endpoint. A REST service, like any other service, has an endpoint with a network address. This endpoint is modeled in the same way as all other endpoints in WSRR so that its state, whether online or offline, can be governed. The REST service can be queried by a runtime system; for example, an enterprise service bus (ESB). The WSRR REST model represents this using a REST service endpoint.
- Realization of a Capability Version. In the same way that a Capability Version can be realized as a web service or as an SCA Module, it can also be realized by a REST service, which enables a REST service to play a part in the complete governance story.
- The business plans the services that it needs according to a top-down service lifecycle.
- The IT department discovers and catalogs the services that it is using, introducing governance and control over existing services.
If you have security enabled, you can add more realism to this tutorial by creating a separate user ID for each role (SOAGovernance, Development, and Operations), and assigning each user ID to its role by using WSRR security. Then, at each stage of the tutorials where you change perspective because the actions are performed by a different role, log out of the WSRR dashboard and log in with the appropriate user ID. You can assign users to roles by using the web UI; for more information, see Add and remove principals for a role.
The tasks that make up this tutorial are divided into a number of sections that form a sequence. If you want to carry out all the tasks, complete the sections strictly in the order shown. However, you can also examine a specific section for reference purposes.