Integration Directory: Unit Summary

z Create and work with Collaboration Profiles z Design Logical Routings

z Work with Collaboration Agreements

z Completely and correctly configure Integration Scenarios within the Integration Directory

Exercise 1: File sender to IDoc Part 3: Integration Directory and Testing Exercise steps

Step 1 – System Landscape Directory Step 2 – Integration Repository Step 3 – Integration Directory Step 4 – Testing

Step 3 – Directory

3.1 From the Integration Builder home page, select “Integration Directory”. This will launch the Java Web Start application. Log in with your user ID and password from the

Integration Server (abap client 800).

3.2 The first step is to create a scenario object. This will serve as container for all your configuration work in the following exercises. Create and save a new scenario object called “TBIT40_WORKSHOP_##” (replace ## with your group number). Save the scenario object immediately after creating it.

3.3 Expand “TBIT40_WORKSHOP_##” Æ “Service without party” and right-click on

“Business System” Æ “Assign Business System…”.

3.4 In the wizard, leave the Party name blank and then select your own business system (TBIT40_LEGACY_BS_##). Uncheck the box “Create Communication Channels Automatically”. This service (business system) represents the legacy system which will be sending data as XML files.

Note:

in case your business system is not listed, a cache refresh is necessary. Close the wizard and use the menu “Environment / Clear SLD data cache“. Once this is done by any user, the Integration Directory will fetch all currently available business systems from the SLD.

3.5 Now create a communication channel. The communication channel is essentially the physical connectivity to/from the application system. This is where the adapter

configuration takes place. In this case we need to configure the file adapter to poll for new files and send them to the Integration Server.

3.5.1 Expand your service (TBIT40_LEGACY_BS_##) and right-click on “Communication Channel” Æ “New…”. Name your communication channel “File_sender_##”.

04 - IntegrationDirectoryEx - File to IDoc3.doc 2

- Message Protocol: File (you can process the file as-is, or convert a flat file to XML).

- Adapter Engine: Integration Server (this is where you can choose between the central or local Adapter Engine).

3.5.5 For the File System Access Parameters, enter the following:

- Source Directory: d:/usr/sap/trans/tmp/group##

(Attention: use “/” instead of the backslash “\” used in windows) - File Name: Vendor##.xml

3.5.5 Select File Type “binary”.

3.5.6 Enter the following processing parameters:

- Quality of service: Exactly Once

- Poll Interval (secs): 60000 (*Note that the poll interval is very high on purpose, in order to keep the amount of messages to a minimum, for training purposes).

- Processing mode: delete (the file will be deleted after being processed).

3.5.7 The sender file adapter is now configured. Save your communication channel.

3.6 The next step is to create a “Sender Agreement” object. This defines a binding between the communication channel you just created, and the outbound interface.

3.6.1 In the left frame, right-click on “Sender Agreement” Æ New.

3.6.2 As service, select your business system TBIT40_LEGACY_BS_## (no party).

3.6.3 Select your interface (Vendor_out). Make sure that the correct namespace is utilized.

3.6.4 In the screen “Edit Sender Agreement”, use F4 help for the Sender Communication Channel field. Select your communication channel (File_sender_##). Save and close.

3.7 From the left frame, create a new “Receiver Determination” object. This is the main part of the routing process, where you assign a receiver for your message.

3.7.1 Select your sender service and interface

3.7.2 In the “Configured Receivers” area, choose the existing service for the target R/3 system R3_BACKEND (check with instructor). Save your receiver determination.

3.8 In the following steps, you will create an “Interface Determination” object. Now that we have defined a receiver for the message, we need to assign an inbound interface, and an interface mapping (if necessary).

3.8.1 In the receiver determination you just created, have a look below at the area

“Configuration Overview for Receiver Determination” at the bottom of your screen, and hit refresh for that the business system you assigned is displayed in that area as well.

3.8.2 In the column “Receiver (Partner/Service)” open the details by using the little triangle . The entry “Not defined” shows you that there is no interface determination present. Right-click on the entry “Not Defined” and select “New Specific”, in order to create a new interface determination object.

04 - IntegrationDirectoryEx - File to IDoc3.doc 4

(since the software component this interface belongs to may not be assigned to the business system).

After choosing CREMAS.CREMAS03, the inbound interface is shown in the interface determination.

3.8.4 A mapping has to be specified since the sender interface is different from the selected receiver interface. Use the F4 help next to the Inbound Interface to select your interface mapping.

3.8.5 When you are done, please save the Interface Determination object.

3.9 Finally you will create a “Receiver Agreement” object. This will allow you to assign a receiver communication channel to the receiver service/interface you have chosen.

3.9.1 Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of the screen, hit “Refresh”.

3.9.2 In the column “Receiver Agreement (Communication Channel)” right click and select

“New Specific”.

3.9.3 In the screen “Edit Receiver Agreement”, for the field “Receiver Communication Channel”

use the input help (F4), and select the communication channel “IDoc_receiver”. This is a predefined channel which is used for all inbound IDocs into the R/3 system. Save the Receiver Agreement.

3.10 Go back to the main receiver determination screen and refresh. Now your configuration is complete. Before activating the objects we need to set up the input file in the next step

(indeed, as soon as your sender communication channel is activated, the polling sequence of the file adapter will start immediately).

Optional:

You may assign the business system R3_BACKEND to your scenario:

In the Integration Directory, navigate to the section “Objects” to find the business system R3_BACKEND under “Service Without Party / Business System”. Right-click on the name of the business system to select the entry “Add to Scenario...”. Select your scenario TBIT40_WORKSHOP_## and choose “Add”.

Now the business system is listed in your scenario. This is not relevant for runtime, just a logical assignment. You may optionally do the same with the communication channel IDoc_Receiver of business system R3_BACKEND.

Step 4 – Testing

4.1 Find the file Vendor##.xml which you had previously saved, and copy it to your shared folder group## on the XI server. Please note, the name of the file should match exactly what you have specified in your sender communication channel.

4.2 Now you can go back to the Integration Directory, open your change list and activate your objects.

4.3 Monitor your directory. After a few seconds your file Vendor##.xml should disappear. This means that the file adapter has successfully processed it and the file was deleted.

4.4 In SAPGUI, choose monitoring Æ Integration Engine monitoring (transaction SXMB_MONI).

4.5 Choose “Monitor for Processed XML Messages”. You can filter using different criteria, for example by date and also by sender service (find your own business service name in the drop-down list). In the monitor, your message should appear with a checkered flag (message processed successfully). From there you can also navigate to the IDoc adapter.

4.6 In the backend R/3 system, go to transaction WE05 or BD87 and search for IDocs according to the logical system name used by your sender. Verify that your IDoc was posted. If

everything goes well, the IDoc should have status 53 (application document posted). If you expand the status record you will see the vendor number that was created. Write down the vendor number for future reference.

4.7 Check in transaction MK03 that your vendor was created.

Appendix: naming conventions and terminology

SAP Exchange Infrastructure

Runtime

Topics

Lecture topics

XI Overview

System Landscape Directory Integration Repository Integration Directory Runtime

Runtime Workbench Adapter Framework

Business Process Management Server Administration

Security

B2B and Industry Standards

After completing this unit, you will be able to:

z Explain basic concepts of XI message processing.

z Describe the concept of the Integration Engine and the Pipeline, and detail the difference.

z Use the message monitoring capability of the XI.

z Explain the XI-SOAP message format.

z Describe the caching capabilities of the Integration Server

In document TBIT40 Implementation & Operation 2004 Q4 (Page 174-182)