webMethods and Intelligent Business Operations 10.2 | Integrating Cloud Applications | Administering CloudStreams | Virtual Services | Creating a New Connector Virtual Service (REST) | The "In Sequence" Step (Connector Virtual Service, REST) | The "Entry Step" (Connector Virtual Service, REST)
 
The "Entry Step" (Connector Virtual Service, REST)
This step specifies the protocol of the requests that the connector virtual service will accept, and the HTTP methods that the virtual services are allowed to perform on the REST resources.
* To edit the "Entry Step" (connector virtual service, 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 connector virtual service name.
The virtual service editor displays the three main processing steps: In Sequence, Out Sequence and Error Sequence.
3. Expand In Sequence.
By default, the In Sequence step contains the sub-steps Entry Step and Routing Rule. (You can add the optional Invoke IS Service step, 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.
Protocol
(Read-only field.) The protocol of the requests that the connector virtual service will accept. The value Local means that the service can only be called from Cloud Connector Services.
HTTP Method
The HTTP methods that the virtual services should be allowed to perform on the REST resources (GET, POST, PUT, DELETE).
It is important to specify all the HTTP methods that are supported for the virtual services. For example, if a virtual service is deployed to CloudStreams and only the GET method was selected here, 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 HTTP Method/Content-Type Combinations.
Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release