Option | Description |
Name | You can optionally change the step name. There are no naming restrictions. |
Type | (Read-only field.) Routing Rule. |
Protocol | (Read-only field.) HTTP. |
Routing Type | Select Context-Based. |
Rule Name | Assign a name to the rule. Then, click the icon next to this field and choose one of the following variables in the Configure Routing Rule dialog box that appears: Time, IP Address (IPv4 or IPv6 format), Date, Consumer, Predefined Context Variable or Custom Context Variable (see
Using Context Variables in IS
Services). Then specify a value and operator appropriate for your chosen variable. If you need to specify multiple variables, use the plus button at the end of the row to add rows. Note: If you select the value Custom Context Variable, you must write an IS service to get/set the custom context variable, and then invoke that service in an Invoke IS Service step. CloudStreams provides an API to get/set custom context variables. For more information, see The API for Context Variables. CloudStreams automatically declares any custom context variables you have specified; there is no need for you to declare them. |
Route To | Specify the URL of the native service to route the request to, if the rule criteria are met. |
Click the icon next to this field and complete the Configure Endpoint Properties dialog box as follows: ![]() ![]() ![]() ![]() Note: Bridging between SwA and MTOM is not supported. If a consumer sends an SwA request, CloudStreams can only forward SwA to the native provider. The same is true for MTOM, and applies to responses received from the native provider. That is, an SwA or MTOM response received by CloudStreams from a native provider will be forwarded to the caller using the same format it received. Note: When sending SOAP requests that do not contain a MTOM or SWA attachment to a virtual service for a native provider endpoint that returns an MTOM or SWA response, the request Accept header must be set to multipart/related (or the virtual service's In Sequence step should include an IS service callout that sets the BUILDER_TYPE context variable to multipart/related). This is necessary so CloudStreams knows how to parse the response properly. | |
![]() ![]() | |
![]() ![]() ![]() | |
Default To | Enter a native service endpoint to route the request to in case all routing rules evaluate to False. Then, click the icon next to this field and complete the Configure Endpoint Properties dialog box, as described for the Route To field above. |
Use credentials from incoming request | Default. Authenticates requests based on the credentials specified in the HTTP header. CloudStreams passes the Authorization header present in the original client request to the native service. |
Use specific credentials | Authenticates requests according to the values you specify in the User, Password and Domain fields. |
Invoke service anonymously | Does not authenticate requests. |
Use existing HTTP Headers | Use the HTTP headers that are contained in the requests. |
Customize HTTP Headers | Use the HTTP headers that you specify in the Name and Value columns on this page. If you need to specify multiple headers, use the plus button to add rows. |