Step 3: Reconfigure Outbound Mapping Services
In FIX Module 6.5, to send a message to a trading partner, it was necessary to complete a multi-step configuration process:
Create an outbound mapping service to map an internally-generated message (from a back-end system) to a
bizdoc and invoke the
fix.tn.doc:addContentPart service.
Create a processing rule for the IS document type and configure the processing action:
Invoking the outbound mapping service in the
Execute Service option.
Using
FIX Transport as the
Deliver Document By option.
In
FIX Module 7.2, sending a message to a trading partner is much simpler. The
fix.tn.doc:addContentPart service has been replaced by the
wm.fix.tn.trp:send service, which transforms messages into FIX format and sends them to the FIX engine. Also,
FIX Module 7.2 does not require you to define a processing rule. Therefore, you must update your outbound mapping services that invoked
fix.tn.doc:addContentPart in
FIX Module 6.5 to now invoke
wm.fix.tn.trp:send instead.
To update the mapping of outbound services
1. In My webMethods, delete the processing rule that is configured in the processing rule Action, Deliver Document By option.
For information about using processing rules, see the webMethods Trading Networks Administrator’s Guide for your release.
2. In Designer, change the mapping of any services that call fix.tn.doc:addContentPart, instead, mapping the IS document directly to the fixIData input field of the
wm.fix.tn.trp:send service. For complete information about mapping services, see the webMethods Service Development Help for your release.