Exposing a Virtual Service as Virtual REST Service

CentraSite offers you the possibility to expose Virtual Services also as Virtual REST Services in webMethods Mediator.

Note: You cannot convert a virtual service as a virtual REST service, if the CentraSite run-time aspects are not enabled.

The REST-enabled support for a Virtual Service is achieved using the Enable REST Support policy action that comes pre-shipped with CentraSite.

When you include the Enable REST Support action in a Virtual Service's run-time configuration, clients can invoke the REST-enabled Virtual Service in Mediator using both a SOAP request and a REST request.

This policy action is set by default in the Receive stage for all Virtual Services. To disable the REST support for a Virtual Service, manually remove the Enable REST Support action from the Receive stage of the Virtual Service.

REST-Enabled Virtual Service in webMethods API Portal

Note: You cannot publish a REST-enabled Virtual Service to webMethods API Portal, if the CentraSite run-time aspects are not enabled.

When you publish a REST-enabled Virtual Service to webMethods API Portal, it is exposed only as a Virtual REST Service in API Portal. All the operations of the Virtual Service are exposed as REST Resources. This allows clients to test the exposed Virtual REST Service in API Portal using a REST request.

Currently, API Portal only supports the HTTP GET and POST methods with these kinds of REST Resources.

Limitations:

If a SOAP operation exposed as a REST resource is invoked using a GET request, the required values for the SOAP operation should be sent as Query parameters. But these Query parameters are not pre-populated with the exposed REST resource. You must manually specify them.

It is assumed that the default content-type is application/json.