Aggregating JMS messages into files

The Message-to-File (M2F) process that aggregates JMS messages into files requires the following steps:

1. Configure the JMS Client Connection within Data Mover to connect to the JMS provider and send each JMS message to the JMS destination.

2. Configure the Message Processing Rule to define the strategy to aggregate multiple JMS messages into a single file. Aggregated files are created in the specified Virtual Path.

3. Configure the Input Contract, with an onMessage trigger and one or more actions. Note that unlike other contract actions, a message-to-file action (M2FAction) is not associated with a workflow template and does not execute workflows but a Message Listener is activated for each action.

Naming convention

Aggregated files are named according to the following convention: jmsfile<JobId>-<date>-<time>.dat, where:

• jmsfile: fixed prefix

• JobId: identifier of the associated transfer job

• date: format YYMMDD

• time: format HHMMSS

• .dat: fixed extension

Example: jmsfile-4007-250324-154648.dat