Generic IDoc routing

When passthrough mode is not used, the library contains a fully parsed IDoc structure. These structures are specific to each IDoc, therefore the library must have a type defined for every IDoc that could be received by the .inadapter component. This library is determined by the RFC Program ID that is configured on the adapter and the ALE or RFC configuration on the SAP side. This behavior can affect how message models are managed.

Whenever you need to develop message flows in isolation, where each flow is to handle a different type of IDoc, the ALE parsed mode is not appropriate because all flows have a common denominator (the library), which needs to be changed whenever a new IDoc type is added.

By using the generic passthrough mode, you can create a routing message flow that uses the IDoc type field of the generic IDoc model to separate WebSphere® MQ queues, for example. You can create message flows that deal with each different IDoc type. If the set of discovered IDocs is extended, you can create a message flow and a library (which contains just the new IDoc), then deploy them, without the need to change existing message flows or libraries.

By using this method, you can also use a single RFC program ID to receive all IDoc types, while still allowing individual IDoc processing.

For instructions about how to route generic IDocs, see Routing IDocs to separate message flows.

For more information about the pattern that is used in the task, see Data distribution SAP to WebSphere MQ: one-way (for IDoc). You can view patterns in the product documentation by using the links only when you use the product documentation that is integrated with the IBM Integration Toolkit, or when you use the online product documentation.