Cloud Application Integration (On-Premises) : Administering CloudStreams : Virtual Services : Creating a New Virtual Service (REST) : The "In Sequence" Step (REST) : The "Entry Step" (REST)
The "Entry Step" (REST)
The Entry Step (required) specifies the protocol (HTTP or HTTPS) over which the virtual service will accept requests, and the HTTP methods (GET, POST, PUT, DELETE) that the virtual service should be allowed to perform on a REST resource.
This 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.
To configure the "Entry Step" (REST)
1. Open Software AG Designer and display the CloudStreams Development perspective by clicking Window > Open Perspective > Other > CloudStreams Development.
2. In the CloudStreams Governance view, expand your CloudStreams Governance project and click the virtual service name.
The virtual service editor displays the three main processing steps: In Sequence, Out Sequence and Error Sequence.
3. In the virtual service editor, expand In Sequence.
By default, the In Sequence step contains the sub-steps Entry Step and Routing Rule. (You can add the optional Transform and Invoke IS Service steps, as described later.)
4. Click Entry Step and complete the following fields in the General page in the Properties view.
Option
Description
Name
You can optionally change the step name to any other name. There are no naming restrictions.
Type
(Read-only field.) Entry Step.
HTTP Methods
The HTTP methods that the virtual service should be allowed to perform on the REST resource (GET, POST, PUT, 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 CloudStreamswill 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. See HTTP Method/Content-Type Combinations.
Protocol
The protocol (HTTP or HTTPS) over which the virtual service will accept requests. To specify HTTPS, select both HTTP and SSL. CloudStreams supports HTTP v1.1 only.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)
Product LogoContact Support   |   Community   |   Feedback