...
- Enable Enable correlation.
- Click Add. A new entry row appears.
- Enter the Header Name.
- Do one of the following:
- If you want to match messages where this header is set to a specific value: Enter , enter that value under Value of Header.
- You can also use criteria expressions to create, for example, string pattern matches.
- If you want to match all messages that include this header (no matter what value it is set to): Enable Correlate whenever the named header is present regardless of value.
- If you want to match messages where this header is set to a specific value: Enter , enter that value under Value of Header.
...
- Enable Enable correlation.
- If you want the correlation to be applied only if the request has the exact URL parameters specified in this table, enable Correlate only when the list of parameters matches exactly. Otherwise, any request that contains listed parameters as well as other parameters will correlate. Whether this option is enabled or disabled, a message that lacks one of the specified parameters will not match.
- Click Add. A new entry row appears.
- Enter the Parameter Name.
- Do one of the following:
- If you want to match messages where this parameter is set to a specific value: Enter , enter that value under Value.
- You can also use criteria expressions to create, for example, string pattern matches.
- If you want to match all messages that include this parameter (no matter what value it is set to): Enable , enable Correlate whenever the parameter name is present regardless of value.
- If you want to match messages where this parameter is set to a specific value: Enter , enter that value under Value.
For example, assume that an asset is deployed under the path http://myvirtserver:9080/MyAsset/MyPath and the following URL Parameters are specified in a responder:
...
The Data Source Correlation tab allows you to specify which data source row values to use in virtual asset responses. When an incoming message matches the responder correlation settings, Virtualize performs a data lookup in the data source based on the data source correlation settings to find a row of data. The row is then used to populate the response (as defined in the Response tab) with parameterized values from the data source. Note that if multiple rows are returned, the first one is used.
For example, the following configures a correlation between the loanAmount value in incoming messages and the Amount column within the ApprovalLists data source:
...
| To achieve this... | Do this.... |
|---|---|
Execute a Data Bank before responder correlation in order to use a data banked request value as part of custom correlation. | Chain a Data Bank to the Pre-correlation Incoming Request of a Message Responder. Use the data banked values in custom correlation to determine if certain criteria is met. You may also reference the data banked values in other forms of correlation or in the response message payload. |
A responder triggers a database update action. For example: update/remote/add a row to a relational database or run a SELECT query. | Chain a Data Bank to the Incoming Request of a Message Responder. You may also chain an XML Data Bank to the XML output of the DB tool and reference these data bank values to in the Responder output in order to have them populate the response with values obtained from a relational database. |
Database data constructs a response message manually. For example: iterate over returned records to generate a desired XML response format. | Chain the DB tool to the outgoing response of a Message Responder and attach an XML Transformer, an XSLT Tool or an Extension tool to it. The output of these tools will replace the content configured in the Message Responder editor's Response tab. This provides flexibility to construct the message manually. If you want to use only certain select values from the database, chain the DB Tool to the Incoming Request as described above. |
| A responder invokes another service. | Chain a SOAP Client or Messaging Client to the Incoming Request of the Message Responder. Chaining a SOAP or Messaging Client to the Outgoing Response of a Message Responder is not supported. |
| A responder invokes another service and uses some of its output to populate response parameters. | Chain a SOAP/Messaging Client to the Incoming Request of the Message Responder and attach a Data Bank to the response of the client. These data bank values can be referenced within the Message Responder Form Input or Form XML views to construct a dynamic response message. If you need to invoke that service with parameters extracted from the request received by the responder, then chain an XML Data Bank to the Incoming Request of the Responder, then chain a SOAP/Messaging Client to the Incoming Request of the responder and parameterize its request with the data bank values you've extracted from the request. Note that order matters here: the data bank needs to be placed before the client in order for the client to be able to use its values. |
| A responder validates incoming requests prior to finding a matching responder in a suite. | Chain a validator to the Pre-correlation Incoming Request of the Message Responder and attach a Text Data Bank to the validator to extract any reported errors. See Validating Incoming Requests for more information about this workflow. |
MQ Character Set Handling
...