CentraSite Documentation : Runtime Governance with CentraSite : Virtualized Services in CentraSite : Configuring SOAP-based Virtual Services : The Routing Protocols Step (SOAP) : “Content-based” Routing (SOAP) : Creating a Routing Rule for “Content-based” Routing (SOAP)
Creating a Routing Rule for “Content-based” Routing (SOAP)
To create a routing rule
1. Click the Endpoint button (next to the Route To column).
2. In the Search for Endpoint dialog that appears, click the Search button to search for the Web service endpoint to route the requests to.
3. Then select a service and click OK.
4. Click the Configure Endpoint Properties icon (next to the Endpoint button) if you want to configure a set of properties for each endpoint individually. In the dialog box, click the endpoint you want to configure and specify the following fields:
Field
Description
SOAP Optimization Method
Optional. Mediator can accept the following optimization methods to optimize the payloads of SOAP requests:
*MTOM: Indicates that Mediator 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 Mediator expects to receive a “SOAP with Attachment” (SwA) request, and will forward the attachment to the native service.
*None (the default).
a. Bridging between SwA and MTOM is not supported. If a consumer sends an SwA request, Mediator 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 Mediator from a native provider will be forwarded to the caller using the same format it received.
b. 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 Request Processing Step should include an Invoking webMethods IS Services in Virtual Services that sets the BUILDER_TYPE context variable to 'multipart/related'). This is necessary so Mediator knows how to parse the response properly.
WSS Header Customization
Indicates whether Mediator should pass the WS-Security headers of the incoming requests to the native service.
*Pass all security headers: Passes the security header, even if it is processed by Mediator (that is., even if Mediator processes the header according to the virtual service's security run-time policy).
Note:  
If the virtual service does not contain a security run-time policy, and the mustUnderstand attribute of the security header is 0/false, then Mediator will always forward the security header to the native service.
*Remove processed security header from request before routing: Removes the security header if it is processed by Mediator (i.e., if Mediator processes the header according to the virtual service's security run-time policy). Note that Mediator will not remove the security header if both of the following conditions are true: 1) Mediator did not process the security header, and 2) the mustUnderstand attribute of the security header is 0/false).
HTTP 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), Mediator will use the value of the global property pg.endpoint.connectionTimeout located in the file Integration Server_directory\packages\WmMediator\config\resources\pg-config.properties . The default of that property is 30 seconds.
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), Mediator will use the value of the global property pg.endpoint.readTimeout located in the file Integration Server_directory\packages\WmMediator\config\resources\pg-config.properties . The default of that property 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.
Note:  
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. If you specify a client certificate alias, you must also include in the virtual service's policy the “Require SSL” action and select that action's “Client Certificate Required” option. The “Client Certificate Required” option specifies whether client certificates are required for the purposes of: 1) Verifying the signature of signed SOAP requests or decrypting encrypted SOAP requests, and 2) Signing SOAP responses or encrypting SOAP responses.
*IS Keystore Alias: The keystore alias of the instance of Integration Server on which Mediator is running. This value (along with the value of Client Certificate Alias) will be used for performing SSL client authentication.
To create an XPath expression for the routing rule, do the following:
1. Click the Edit button (next to the If True column).
2. In the XPath Editor that appears, view the Namespace Map tab, which displays all predefined namespaces (for example, soapenv, soapenc, and so on.). If you want to add custom namespaces, click Add Custom Namespace/prefix, specify a name and value for the namespace and click OK. If you need to add additional rows, use the plus button.
3. In the XPath Editor's All Nodes tab, expand the namespace's node, choose the method you want for the XPath expression, and click OK.
4. In the XPath Editor's XPATH Evaluator tab, evaluate the XPath expression by specifying an argument in the XPath Expression field, and then click Evaluate.
5. After you have evaluated the XPath expression, click OK.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback