IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 205 / 330

JMS Queues
Cluster Configuration
191
Integration cron tasks deliver enterprise service messages from flat or XML files
and interface tables. The cron task places messages into the queue store on the
server where the cron task is running, which limits the processing to a single
server.
To configure integration cron tasks to place messages into multiple queue stores
on different application servers:
T Interface tables – Enable multiple instances of the interface table cron task
to different servers and use the cron task properties to select different
groups of data. You can use the External System, Interface, and Queue
table properties to select data.
T Import XML file data – Enable multiple instances of the XML file import
cron task to different servers and use the cron task properties to select
different files to import. Use the source directory and file name properties
to select the import files.
T Import flat file data – Enable multiple instances of the flat file import cron
task to different servers. Use the cron task property source directory to
select different files to import.
After messages are in the queue, all application servers can simultaneously pull
messages from their respective queue stores and process them into the system.
Message-driven beans must be enabled on each application server in the cluster.