Using the Fragmentation sample application

The FTM Fragmentation Sample project includes test messages for both sterling and euro currencies and pacs.008.001.02.xml formats. These messages can be used to exercise the sample application through a number of scenarios.

The messages for each format must be put to the specified FileInput directory as shown in the following table.
Table 1. Message format
Message format FileInput directory FileOutput directory IBM® MQ queue output
pacs.008.001.02 (GBP) <system path>\pacs_in <system path>\pacs_out -
pacs.008.001.02 (EUR) <system path>\pacs_in - FXH.FRAG_SAMP.CREDIT_TXFR_OUT_MT103
Notes:
  • You can test pacs.008.001.02 with both EUR and GBP currencies:
  • Sterling GBP payments output to a specified FileOutput directory.
  • Domestic EUR payments output to specified IBM MQ queue.
  • You can change the location of the FileInput directory and FileOutput directory, by specifying new directories in the Fragmentor msgflows shown in Figure 1 and De-Fragmentor msgflows shown in Figure 2
  • When moving large files to the input directory for the FileInput node, to avoid reading incomplete files, we recommend to use mv command or chmod g-x,g+s fileToBeLocked.
  • The upper limit for any queue in WebSphere® MQ is 100 MB. The FileInput node imposes a limit of 100 MB. If your application needs to process messages larger than 100 MB, you can override the FileInput node record size limit by taking the following actions: Before starting the broker, set the environment variable MQSI_FILENODES_MAXIMUM_RECORD_LENGTH to the required limit as an integer number of bytes. For example: SET MQSI_FILENODES_MAXIMUM_RECORD_LENGTH=268435456 which can be set in environment variables.
    Setting Inbound Fragment size
    The number of inbound transactions to be processed per fragment can be set, change the value of PMT_CNT_LIMIT. Deploy the BAR file containing Fragmentor.msgflow. For more information, see Figure 3,
    Setting Outbound Fragment size
    The number of outbound transactions to be processed per fragment can be set, change the configuration value of OUT_FRAG_SIZE key. For more information, see Decision Service simulation configuration values.
Figure 1. Fragmentation Input directory setting
fragmentorMsgFlow.jpg
Figure 2. De-Fragmentation Output directory setting
De-FragmentorMsgFlow.jpg
Figure 3. Fragmentation size setting
fragmentorMsgFlowBarFile.jpg
Figure 4. Decision Service simulation configuration values
iLogSimulation.jpg