Configuring the FTM broker

The files defining FTM user defined nodes (for example: Standards Processing node, FlowManager Shutdown node, WebSphere® Decision Service Node) must be available in the LILPATH of the broker. To set the LILPATH to the resource directory use the mqsichangebroker command as follows:
mqsichangebroker broker -l <install dir>
/ftm/v3213/run/jplugin

Ensure that the user who starts the broker has at least read access to all of the files in the directory.

Note:

This directory contains the DecisionServiceImpl.par file. This file should be removed if your FTM application is not using IBM® Operational Decision Manager (ODM) through the Decision Service Node.

The fragmentation sample supplied does not use ODM by default, but can be configured to do so. This is to avoid a java.lang.NoClassDefFoundError: ilog.rules.res.session.IlrSessionException error message appearing in the log when the broker loads the DecisionServiceNode in an environment where ODM is not configured. For more information, see Fragmentation sample application.

Java™ classes and resources must be available in the class path. Add the following entries to the CLASSPATH environment variable:
<install dir>/ftm/v3213/run/classes
<install dir>/ftm/v3213/run/classes/*
Ensure that the user who starts the broker has at least read access to all files in the directory.
Then proceed to start the broker:
mqsistart broker
Note:

Changes to three properties are required for correct time stamp behavior when using WebSphere Message Broker V8.0.0, Fix Pack 4 as the FTM run time. These are set on a per execution group basis.


mqsichangeproperties <broker> -e <execution group> -o ComIbmGenericXmlParserFactory -n storeTimeZoneInValue -v yes 
mqsichangeproperties <broker> -e <execution group> -o ComIbmGenericXmlParserFactory -n writeTimeZone -v whenSet 
mqsichangeproperties <broker> -e <execution group> -o ImbESQLManager -n castWithAccurateZoneOffsets -v yes

In IBM App Connect Enterprise V9 and above these properties do not need to be modified.