IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Routing IDocs to separate message flows

You can use a pattern to process IDocs of various kinds with a single RFC program ID without having to redeploy or rediscover existing adapters, even when adding new types of IDoc.

Before you start:

Read the concept topic about Generic IDoc routing.

You can create a routing message flow that contains an SAPInput node. You can use this flow to route the IDocs, based on their type, to separate message flows that deal with each different IDoc type. If the set of discovered IDocs is extended, you can create a message flow and message definitions, then deploy them, without the need to change existing message flows or message definitions.

For more information about the pattern that is used in this 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.

The following instructions describe how to use a pattern to create the resources that you need.

Open the Patterns Explorer by following the instructions in Choosing a pattern.
Expand the Application Integration category, and the SAP category, then click MQ one-way (IDoc) to open the pattern. The pattern specification describes the pattern and how to use it.
Click Create New Instance.
Enter a name and provide the required configuration parameters for the pattern instance, then click Generate.
When the pattern has been generated, the Application Development view lists the resources that have been generated:
- A Java™ project
- A routing message flow:
- An .inadapter component
Add these resources to a BAR file then deploy the BAR file.
Use the mqsisetdbparms command to set your user name and password for the SAP system. For more information about how to use this command, see mqsisetdbparms command.
The pattern also creates a configurable service called idocpassthrough.inadapter.configurableservice. Deploy the configurable service by dragging it onto the broker in IBM Integration Explorer.

Result: The SAP adapter is connected by using the program ID that is specified in the configurable service. The message flow receives an IDoc from SAP and writes it to WebSphere MQ. The ESQL code in the Compute node specifies that the queue name to which the message is written is the same as the IDoc type. You can create separate message flows to process the different types of IDoc.

Next: The SAPInput node can route the IDocs according to their type, but it does not parse the binary data BLOB messages that they contain. You can create a message flow that contains an MQInput node, which uses message definitions in the DataObject domain to parse the binary data BLOB message into a structured record that IBM Integration Bus can manipulate. To use the DataObject parser to parse IDocs, you must set the Message domain property of the MQInput node to DataObject, and set the Message format property to SAP ALE IDoc. To create the message definitions, run the Adapter Connection wizard.

bc22060_.htm |

Last updated Friday, 21 July 2017