Entry Step (REST Virtual Service)

To configure the Entry Step:

1. Click the Virtual Service name in the CloudStreams Governance view.

2. Expand the In Sequence step in the editor.

3. Click Entry Step and complete the following fields in the Properties view.

Name

You can optionally change the step name from Entry Step to any other name. There are no naming convention restrictions.

Type

(Read-only field.) Entry Step.

Protocol

The protocol (HTTP or HTTPS) over which the virtual service will accept requests. To specify HTTPS, select both HTTP and SSL.

The Entry Step allows you to bridge protocols between the consuming application and the native service. For example, suppose you have a native service that is exposed over HTTPS and a consuming application that submits SOAP requests over HTTP. In this situation, you can configure the virtual service's Entry Step to accept HTTP requests and configure its Routing Rule step to route the request to the Web service using HTTPS.

HTTP Methods

The HTTP methods that are supported by the native service (GET, POST, PUT and DELETE).

It is important to specify all the HTTP methods that are supported for the virtual service. For example, if the virtual service is deployed to CloudStreams and only the GET method was selected in the virtual service definition, then CloudStreams will only permit GET invocations. A POST request will be rejected with a return of statusCode 405 even if the native service happens to support POSTs. It is also important for the native service to return the correct Content-Type header with its responses.

At run time, CloudStreams determines the type of a request message based on the message's HTTP method and its Content-Type. For a list of valid HTTP method/Content-Type combinations, see the section The Request Message's HTTP Methods and Content-Types for REST Services in the document Administering webMethods CloudStreams.