The properties of this node are described.
Property | Description |
---|---|
Runtime Tab | |
Runtime ID | Enter a unique identifier for each asynchronous receiver within a service definition. |
Destination Name | Enter the name of the queue to which the message is to be sent
using the following format: <machineName>/private$/<DestinationName> Sterling Selling and Fulfillment Foundation does not support Queue Lookup through the Active Directory. |
Max Threads | The maximum number of threads for this process. |
Transactional/Non Transactional | Select if the messages are to be received in a Transactional
or Non Transactional Mode. Note: If you
plan to use transactional mode of messaging, create the queue in MSMQ
as a transactional queue.
|
Server Tab | |
Server Name | Select the name of the server which actually executes the service. For more information about creating a new server, see "Adding a New Server". |
Exception Tabs | See Table 1 for the receiver link exception handling properties. |
The following are the MSMQ node's connection properties:
Connection | Node Connection Rules |
---|---|
Can be the first node after the start node | Yes, for services invoked both in a synchronous or asynchronous mode |
Can be placed before |
|
Can be placed after |
|
Passes data unchanged | Transport nodes do not modify data |