Transaction/Alias ID
Transaction IDs uniquely identify a transaction. Typically, your application already has a way to identify each transaction. You simply need to select that field from the message as the identifier in this section.
For simple WebSphere MQ-based applications, using the MQMD Buffer.MsgId field can suffice.
If you chose to enable aliasing on the Models tab any transaction ID you create here becomes an alias ID. If you use payload data, you can specify additional alias IDs using the payload data. This is done on the Payload Data tab.
Settings on the activity apply to all input and output links. If the message format or location differs, than these details can be configured per link. For details, see the following table.
Field name | Description | Rqd |
|---|---|---|
Message Format | Name of a message format created on the Message Formats tab. Select a message format from the list. The list is populated from the default and custom message formats from the Message Formats tab. The last format listed is Technology Data. When selected the Message Field contains a list of technology data fields available to the activity's technology. If the technology data is not visible, make sure it is enabled. | x |
Message Field | Name of the message field you want to reference. The list of available fields for the message format you chose. The available fields change based on which message format you select. For details about each of the available options, refer to the documentation for message formats (Message format fields) and for WebSphere MQ (MQMD, MQDHL (dead letter header), and MQXQH (transmission queue header)) and WebSphere Message Broker (WMB Exit MQMD and WMB MPN MQMD) | x |
Indices | Identifies which index should be used for the message format data. Refer to your message format and the details about message formats to determine which index or indices you should use. Multiple transaction IDs in a single message can be monitored by specifying a range or All. | x |
Delimiter | Character used to separate the individual field from one or more message formats from the next field of the same or different message format. You can have different delimiters between your various message formats. You can also have a blank delimiter; that is, a delimiter with nothing defined. |
The table below describes the transaction filtering criteria fields.
Use these flexible filters to select the messages required when using a shared or common resource, such as shared transmission queues or brokers. You can select to monitor only certain types of transaction that flow through an activity. You can select to filter to include or exclude.
If all input and output links have the same filtering and same message formats, than they can be defined once in the activity properties. Otherwise they can be uniquely defined per link. You can define them on the activity and link in which case if a link definition exists, it is used for that link.
You can filter on technology data that is unique to the extension type.
Field name | Description | Rqd |
|---|---|---|
Type | Transaction completion type. One Field Value: Only one message field is evaluated against a value using an operator. Two Field Values: Two message fields are evaluated against each other. This is useful when you need to compare two fields and use the results of the comparison. | a |
Technology Data | Select to have the name of a technology used in the filter. The list of technology data available depends on the activity implementation type. | |
Message Format | Name of a message format created on the Message Formats tab. Select a message format from the list. The list is populated from the default and custom message formats from the Message Formats tab. The last format listed is Technology Data. When selected the Message Field contains a list of technology data fields available to the activity's technology. If the technology data is not visible, make sure it is enabled. | a |
Message Field | Name of the message field you want to reference. The list of available fields for the message format you chose. The available fields change based on which message format you select. For details about each of the available options, refer to the documentation for message formats (Message format fields). | a |
Indices | Identifies which index should be used for the message format data. Refer to your message format and the details about message formats to determine which index or indices you should use. | a |
Operator | See Operator. | a |
Value | Text or numeric string. Unlimited text. | b |
Conjunction | Logical connector used to connect this filtering criteria to the next criteria. Options are: AND (default), OR. | c |
[Add Parentheses] | Adds parentheses to the message filtering criteria table to group filter criteria. | d |
- Required if you filter transactions on this activity.
- Required if you are using One Field Value, unless your operator is set to Present or Absent. No, if you are using Two Field Values.
- Required when you are using two or more filtering criteria.
- Required only for grouping filter criteria.
Comments
Log in or register to comment.