Outbound Mapper Container Template

This template is made up of a msgflow file as shown in the following figure. It is merely a starter file for use as a container for all your outbound mappers. The template demonstrates the inclusion of the two outbound mapper templates. The data source properties of the mappers are promoted.

To use the template, copy the file into your implementation project and rename it to OutboundMapperContainer.subflow. If possible, include it in the same broker schema as the mappers that it will contain. Use this container to group all your outbound mappers into a single flow for inclusion in your event processing or physical transmission wrapper flows.

Figure 1. OutboundMapperContainer.subflow
OutboundMapperContainer.subflow