Outbound Mappers

The IBM® FIN Mapper Pack outbound mappers expect to have access to the information shown in Output mapper context data in Coding output mappers. The output mappers all start with the ISFToFINCommonMapper subflow. It starts with the BeginOutboundMapper subflow and terminates with the EndOutboundMapper subflow. It calls the ISFToFinMapper subflow for the specific message mapper processing in between.

Figure 1. Outbound mapper subflow
Outbound Mapper subflow

The failure terminal of the BeginOutboundMapper node is connected directly to the EndOutboundMapper node. In this way, if any exceptions occur during the mapping, the EndOutboundMapper subflow records them in the database so that operations personnel can be made aware of the failure.

The ISFToFINMapper subflow is shown in the following figure.

Figure 2. ISFToFINMapper outbound mapper subflow
ISFToFINMapper Outbound mapper subflow
This subflow starts with the CheckConfig node, which is responsible for loading the channel category from the cache, determining an appropriate message type to use based on the business concept from the ISF XML header, locating an appropriate message definition set to use, determining if input ISF validation is required, and handling the various failures that were detected while performing these services. It then creates an XML domain on the output root to receive the FIN messages MTXML tree. It begins populating the message tree with MT blocks 1, 2, 3, 4, and 5, using addenda directly from the input environment ISF XML. Block 4 is created in its proper place in the tree, but it is left unpopulated since this is the job of the body mapper for that message type. Finally, it creates the array of mapping labels that are used to route processing to each subflow involved in the body mapping for that specific message type. Labels are added for:
  • The configured pre-body mapper (optional).
  • The specific target mapper.
  • The configured post-body mapper (optional).
It uses the message type to determine the body mapper target label and to locate the pre-body and post-body mapper label names in the configuration setting. A fixed and final return label, ISFToFINMapperRouteBackLabel, is appended to the list in order to route the processing to the back label of this subflow after all of the body mappers have completed.

The RouteToNextMapper subflow routes the processing to the appropriate body mapper subflows as set by the PrepareRouting node. Processing is returned to this subflow when the back label is encountered at the end of the routing list.

The ComIbmFxhStandardsProcessing subflow performs the MTXML to MT mapping. Mapping failures are emitted by various failure output nodes on this subflow, which are routed to the ThrowSpnException compute node for processing.

The Cleanup compute node records any errors that were detected and ensures that the MT output conforms to the channel specified character set ID (CCSID). If a character set is not specified, the default of 1208 is used. It also removes all processing artifacts from the environment tree upon completion of the mapper service.