Routing Rule Step (Straight Through Routing, SOAP Virtual Service)

When you select the Straight Through routing protocol, the virtual service will route the requests directly to the native service endpoint you specify. You may specify how to authenticate requests (as with all routing protocols).

To configure the Routing Rule step for Straight Through routing:

1. Click the virtual service name in the CloudStreams Governance view.

2. Expand the In Sequence step in the editor.

3. Click Routing Rule and complete the following fields in the Properties view.

Name

You can optionally change the step name from Routing Rule to any other name. There are no naming restrictions.

Type

(Read-only field.) Routing Rule.

Protocol

(Read-only field.) HTTP.

Routing Type

Select Straight Through.

Default To

The URL of the service to which the request is to be routed.

Then, click the icon next to this field and complete the Configure Endpoint Properties dialog box as follows:

Optimization Method: Select one of the following options:

None: The default.

MTOM: Indicates that CloudStreams expects to receive a request with a Message Transmission Optimization Mechanism (MTOM) attachment, and will forward the attachment to the native service.

SwA: Indicates that CloudStreams expects to receive a SOAP with Attachment (SwA) request, and will forward the attachment to the native service.

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.

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's 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.

Connection Timeout: The time interval (in seconds) after which a connection attempt will timeout. If a value is not specified (or if the value 0 is specified), CloudStreams will use the default value specified in Integration Server.

Read Timeout: The time interval (in seconds) after which a socket read attempt will timeout. If a value is not specified (or if the value 0 is specified), the default is 30 seconds.

SSL Options: To enable SSL client authentication for the endpoint, you must specify values for both the Client Certificate Alias field and the IS Keystore Alias field. If you specify a value for only one of these fields, a deployment error will occur.

SSL client authentication is optional; you may leave both fields blank.

Client Certificate Alias: The client's private key to be used for performing SSL client authentication.

IS Keystore Alias: The keystore alias of the instance of Integration Server on which CloudStreams is running. This value (along with the value of Client Certificate Alias) will be used for performing SSL client authentication.

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 the tab. If you need to specify multiple headers, use the plus button to add rows.