MSMQ sender

The properties of this node are described.

Configuration properties

Table 1. MSMQ sender configuration properties
Property	Description
Destination Name	Enter the name of the queue to which the message is to be sent using the following format: <machineName>/private$/<DestinationName> Sterling™ Order Management System Software does not support Queue Lookup through the Active Directory.
Time To Live	Enter the time period after which the messages are to be deleted from the queue. A value of 0 causes the message to never be deleted from the queue. If this is set to a non-zero value, messages in the queue which are not consumed for the specified time interval are automatically deleted from the queue by the provider.
Persistent/Non Persistent	Select if the messages are to be Persistent or Non-Persistent when dropped into the queue.
Transactional/Non Transactional	Select Transactional if you want the message to be committed to the queue only after the service is completed. Select Non Transactional if you want the message to be committed to the queue immediately. For example, if the ON_SUCCESS event of any standard Sterling Order Management System Software API is attached to a service, in which the message is transactionally written to the queue, the message is committed to the queue only upon successful completion of the ON_SUCCESS event. The message is then rolled back from the queue if there is any error in the ON_SUCCESS event after the message is staged. However, in non-transactional mode, the message remains in the queue, once it is staged and is not rolled back. Note: If you plan to use transactional mode of messaging, create the queue in MSMQ as transactional queue.
String Message	Select this field if you want to set the PROPID_M_BODY_TYPE to VT_BSTR De-select this field if you want to set the PROPID_M_BODY_TYPE to VT_EMPTY.

Note: The JMS session objects can be pooled based on the service being executed. Hence, whenever the JMS sender requires a session object, the Application Platform framework tries to get a free session object from the pool. If there are no free sessions available, a new session object is created to send the message and then added to the pool. Any session object that is idle for a certain configurable period of time is closed by the framework. The yfs.jms.session.reaptime property in the yfs.properties file is used to set the JMS session reaptime. To modify this property, add an entry for it in the <INSTALL_DIR>/properties/customer_overrides.properties file.