MSMQ Adapter 6.0 | webMethods MSMQ Adapter Documentation | webMethods MSMQ Adapter Installation and User’s Guide Documentation | Adapter Notifications | Listener Notifications | Configuring Listener Notifications | Configuring Asynchronous Listener Notifications
 
Configuring Asynchronous Listener Notifications
Perform the following tasks to configure asynchronous listener notifications.
*To configure an MSMQ asynchronous listener notification
1. Review the steps in Before You Configure Listener Notifications.
2. Start Designer.
3. Using Designer, perform the following:
a. Right-click the package in which the notification should be contained and select New > Adapter Notification.
b. Select the parent namespace and type a name for the adapter notification.
c. Click Next.
4. Select MSMQ Adapter as the adapter type and click Next.
5. Select Asynchronous Listener Notification from the template and clickNext.
6. Select the appropriate Notification Listener Nameand click Next.
7. Select a package and folder to contain the notification, type a unique name for the notification, and click Next.
8. Click Finish.
9. Designer creates an asynchronous listener notification and an asynchronous publishable document type, and the editor for the adapter notification appears.
a. You can select the Adapter Settings tab at any time to confirm listener notification properties such as the Adapter Name, Adapter Listener Name, and Adapter Notification Template as necessary.
b. In the Publish Document section, you can specify how you want the notification document to be published:
*To publish documents to Broker, select webMethods Broker /Local. This is the default option.
*To publish documents to a JMS provider, select JMS Provider, and provide values for the following input fields:
Field
Description/Action
Connection alias name
The name of the JMS connection alias configured on Integration Server.
Destination name
The name of the destination from which you want the JMS trigger to receive messages.
Destination type
Whether the destination is a Queue (default) or a Topic.
10. Select theFilter tab to specify which property values should match the arriving message to run the notification.
a. From the drop-down menu, select one of the following Message Filtering Modes:
*MATCH_ONE - Any one of the selected properties can be used to identify the message.
*MATCH_ALL - All selected properties will be used to identify the message.
Note:
If none of the properties are selected, all messages will pass the filter criteria.
b. Select the property fields and enter the values for the properties. Use the following icons to manage the rows in theProperty column:
*To define new property fields, select the icon (or the icon).
*To change the order of the property fields to ensure that the parameters are parsed in the correct order, use the or icons.
*To delete a property field, use the icon.
You can add the following property fields to the Property column.
Property
Description
MessageId
Identifies the message using a hex string.
CorrelationId
Identifies the message using a hex string correlation identifier. For example, {F944A0B1-1DA0-4A93-A266-E54ACDD55342}\30775.
Delivery
Specifies how Message Queuing delivers the message. Valid values are:
*1 - indicates that along its route, the message is stored locally on disk until it is forwarded to the next computer.
*0 - indicates that along its route, the message stays in volatile memory until it is received.
Priority
Specifies the message priority. The value is between 0 - 7. The lower number indicates lower priority. Default: 3.
Note:
Message Queuing automatically sets the priority level of the transactional messages to 0, which indicates that the priority is ignored by the transaction.
AppSpecific
Specifies application-generated single integer values.
11. Select the Output Message Property tab to identify the message property fields that will be generated in the notification publishable document.
You can add the following property fields:
Property
Property Type
Description
Ack
java.lang.Integer
Specifies the type of acknowledgment messages that Message Queuing will post in the administration queue when acknowledgments are requested.
AdminQueuePathName
java.lang.String
Specifies the queue path name used for Message Queuing-generated acknowledgment messages.
AdminQueueFormatName
java.lang.String
Specifies the queue format name used for Message Queuing-generated acknowledgment messages.
AppSpecific
java.lang.Integer
Specifies application-generated single integer values.
ArrivedTime
java.lang.String
Specifies the time when the message arrives in the queue.
CorrelationId
java.lang.String
Identifies the message using a hex string correlation identifier. For example, {F944A0B1-1DA0-4A93-A266-E54ACDD55342}\30775.
CorrelationIdByteArray
byte array
Identifies the message using a 20-byte correlation identifier.
Delivery
java.lang.Integer
Specifies how Message Queuing delivers the message. Valid values are:
*1 - indicates that along its route, the message is stored locally on disk until it is forwarded to the next computer.
*0 - indicates that along its route, the message stays in volatile memory until it is received.
DestinationQueuePathName
java.lang.String
Specifies the destination queue path name of the message
DestinationQueueFormatName
java.lang.String
Specifies the destination queue format name of the message.
MessageId
java.lang.String
Identifies the message using a hex string.
MessageIdByteArray
byte array
Identifies the message using an MSMQ-generated 20-byte message identifier.
IsAuthenticated
java.lang.Integer
Indicates whether the message was authenticated at the request of the sending application. Valid values are:
*1 - the message is authenticated.
*0 - the message is not authenticated.
IsFirstInTransaction
java.lang.Integer
Indicates whether the message was the first message sent in its transaction. Valid values are:
*1 - the message is first.
*0 - the message is not first.
IsLastInTransaction
java.lang.Integer
Indicates whether the message was the last message sent in its transaction. Valid values are:
*1 - the message is last.
*0 - the message is not last.
Label
java.lang.String
Provides a description of the message.
Journal
java.lang.Integer
Specifies whether Message Queuing stores copies of the message as it is routed to the destination queue. Valid values are:
*0 - the journal is disabled.
*1 - the message is stored in the applicable dead-letter queue on failure.
*2 - a copy of the message is stored in the computer journal if the message was successfully delivered to the next computer.
MaxTimeToReachQueue
java.lang.Integer
Specifies the time limit (in seconds) for a message to reach the queue.
MaxTimeToReceive
java.lang.Integer
Specifies the time limit (in seconds) for the message to be retrieved from the target queue.
MsgClass
java.lang.Integer
Indicates the message type.
Priority
java.lang.Integer
Specifies the message priority. The value is between 0 - 7. The lower number indicates lower priority. Default: 3.
Note:
Message Queuing automatically sets the priority level of the transactional messages to 0, which indicates that the priority is ignored by the transaction.
SendTime
java.lang.String
Indicates when the message is sent.
SourceMachineGuid
java.lang.String
Indicates the GUID of the computer that sent the message.
12. Select the Permissions tab to manage the access control list (ACL) information. Use the drop-down menu to select each of the ACL types. For general information about assigning and managing ACLs, see the webMethods Service Development Help for your release.
13. From the File menu, select Save.