WebSphere Data Interchange 3.2 and MQ Link for SAP R/3

Transcription

1 WebSphere Data Interchange 3.2 and MQ Link for SAP R/3 Author: Pete Murphy Written: 24nd May, 2003 Version: 1.0 (draft) Introduction WDI 3.2 is certified in the CA -EDI category. The mapping interface is a powerful tool for transforming IDocs into other documents such as EDI messages, XML structures or traditional records. To assist development of these transformations a set of IDoc formats are available for import in the WDI 3.2 client, and additional ones can be created (contact the author for further details). A common approach is to configure SAP R/3 to create or receive IDocs in files. However if the transformation solution is implemented on a different machine, the IDoc files will need to be transferred. Often a home grown file transfer solution is developed but there are usually issues with the reliability and maintenance. The alternative is to invest in a commercially written file transfer solution but this can be expensive This document explains how to exploit WebSphere MQSeries and the MQSeries Link for SAP R/3 to avoid the need for files. The MQ Link for SAP R/3 is certified in the CA-AMS category. In a nutshell this means (i) It must reliably receive ALE IDocs from SAP R/3 and pass this to a message handling software ; (ii) It must reliably send ALE IDocs into SAP R/3 from a message handling software. The MQ Link for SAP R/3 uses WMQ as the message handling software. As WDI 3.2 supports WMQ is it possible to connect SAP R/3 to WDI using the MQ Link and WMQ.

2 Overview SAP R/3 A L E SAP RFC MQ Link WDI 3.2 WMQ server bindings WMQ messaging WMQ server bindings The MQ Link connects to SAP R/3 using an RFC call and waits. When an IDoc is passed from SAP R/3 the MQ Link places it on an MQSeries queue. As part of placing the message on a queue an MQ Link exit needs to be called. This ensure the IDoc does not have any MQ Link header information prefixed to the WMQ message. WMQ will ensure the message reaches the correct queue. WDI transformation can be started automatically by using WMQ triggering. When the IDOC arrives in the WDI WMQ queue it will be processed by WDI 3.2. When WDI 3.2 creates an IDoc it will send it to the MQ Link inbound server WMQ queue. As part of receiving the message from a WMQ queue, an MQ Link exit adds the MQ Link header prefix not created by WDI 3.2. The MQ Link will use the INBOUND_IDOC_PROCESS or INBOUND_IDOC_ASYNCHRONOUS call to pass the IDOC into SAP R/3. As all the calls use WMQ transaction calls or SAP R/3 transactional call, messages are not lost or duplicated.

3 Setup and Configuration Details MQ Link configuration A standard MQ Link for SAP R/3 configuration can be used. The only extra step that is needed is to include the WDI32EXIT for the inbound and outbound server. For outbound configurations the file smqdestconf should include set the calluserexit= and exitname parameters For inbound configurations the file in.ini should include set the invokeexit= and exitname parameters

4 WDI 3.2 configuration ALE IDoc are similar but not identical to file IDocs. The difference is that segments are padded to 1000 bytes using blanks. WDI 3.2 formats are available for this structure ; contact the author for further information. A standard WDI WMQ triggering configuration and Profiles configuration can be used. The following screen short show a configuation used for MATMAS02 Idocs WMQ triggering - using WMQ Explorer and Properties for queue MATMAS02

5 WDI 3.2 MQ profile

6 WDI 3.2 Services Profile

7 WDI 3.2 Network Profile The network program is EDIMQSR. The MQ Link for SAP R/3 does not use RFH2 or JMS headers.

8 WDI 3.2 Mail Box Profile

9 Other considerations CA-AMS certification was designed to ensure reliable exchange of IDocs between SAP and a messaging middleware. As this removes the issues involved with losing file IDocs during file transfer, status IDocs are no longer needed in many cases. The MQ Link for SAP R/3 does not currently explicitly support IDoc with status segments (EDI_DS/DS40).