JMS Queues
Basic Configuration 133
Queue Properties
The maximum try count property represents the number of times the system
retries to process a failed message before sending an e-mail notification. The
maximum try count default value is 5; the integration framework retries a failed
message five times.
The integration framework tries to process a failed message as many times as
specified by the maximum try count. If the message cannot be successfully
processed after the specified number of retries, the integration framework
changes the failed message status from ERROR to HOLD.
The error management retry mechanism uses the maximum try count parameter.
When a message status is changed from HOLD to RETRY, the Error Management
application retries its processing as many times as specified by the maximum try
count parameter.
The default value for the count parameter property is 0. The queue processing
framework attempts to process the error message indefinitely.
Cron Task for the Sequential Queues
The default settings direct the JMSQSEQCONSUMER cron task to poll the
outbound queue, sqout, and the sequential inbound queue, sqin, every 30
seconds. You must activate the applicable instances of the cron task (SEQQIN,
SEQQOUT), to avoid having the unprocessed inbound and outbound messages
remain in the queues.
If you do not use one or both of these queues, do not activate these cron task
instances.
Asynchronous Cron Task Inbound Processing
The XMLFILECONSUMER cron task and the FLATFILECONSUMER cron tasks
must first be created, configured, and enabled before cron task message
processing can occur.
XMLFILECONSUMER Cron Task Parameters
The XMLFILECONSUMER cron task is the mechanism that you must use to load
XML files without any application user intervention.
The XMLFILECONSUMER cron task has the following predefined parameters:
Parameter Description
EXTERNALSYSTEM A required parameter value that identifies the
external system value that the cron task data load
process uses.
SOURCEDIRECTORY A required parameter value that defines the
directory where source files are loaded. This
directory must exist on the application server.
To Next Page
Loading...