CentraSite User's Guide : Runtime Governance : Virtual Service Asset Management : Managing Virtual Service Assets through CentraSite Control : Virtual SOAP Service Management : Configuring Virtual Services : Creating Context-based Routing Rule
Creating Context-based Routing Rule
To create a context-based routing rule
1. In the Variable column, select Time, IP Address, Date, Consumer, Predefined Context Variable or Custom Context Variable. For more information, see Virtual Service.
2. In the Value column, specify an applicable value. For Date select Before, After or Equal To and provide a date. For Time choose Before or After and provide a time. For IP Address, type numeric values for Between and And. For Consumer, click Browse and select a consumer application name.For Predefined Context Variable or Custom Context Variable, choose the String or Integer data type. Select a predefined variable name or custom variable name from the drop-down list. For String, choose Equal To or Not Equal To and type a value. For Integer, choose Greater Than, Less Than, Not Equal To, Equal To or and type a value.
a. For the list of the predefined context variables, see Virtual Service.
b. The predefined context variable PROTOCOL_HEADER is not available in the drop-down list; to include PROTOCOL_HEADER in the rule, define the variable as Custom Context Variable. For more information, see Context Variables in Virtual Services.
c. If you define a custom context variable in the routing rule, you must write a Virtual Service and invoke it in the Virtual Service's Request Processing step. In this Integration Server service, use the API to get/set the custom context variable.
3. In the Combination Uses field, choose an operator for the expression: AND (the default) or OR.
4. In the Route To field, click Endpoint, and then choose the URL of the Native Service to route the request to, if the rule criteria are met.
5. Click Configure Endpoint Properties (next to the Endpoint button) to configure a set of properties for each endpoint individually. In the dialog box, click the endpoint you want to configure and specify an appropriate information for each of the displayed 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 Virtual Service 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 or 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 (that is, 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 or 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 uses 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 uses 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.
6. Click OK.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)
Product LogoContact Support   |   Community   |   Feedback