In previous article, we discussed IR Settings needed for your first XI scenario. Now, let us delve into ID Configuration. Integration Directory is a configuration tool which helps to configure the routing rules for the business scenarios created in Integration Repository. The ID binds the technical routing information to the interfaces via the communication channels. Communication channels contain the adapters which do the job of translating incoming message to XML and vice versa in case of outgoing message. There are different types of adapters like File, IDoc, RFC, JDBC, JMS, Mail, SOAP, HTTP etc. There are many Third-Party adapters provided by Third-Party Vendors like Seeburger, RosettaNet etc. Note that incoming message (i.e message from the sender system) is referred to as outbound message while outgoing message(i.e message being delivered to the target system by XI) is referred to as inbound message. The frame of reference is always the communicating systems and never the XI box or the integration system. Now, let us start with Directory Configuration.

Define Collaboration Profiles

Collaboration Profiles contain the information about involved parties, business systems/services, and the communication channels.

• Access path – Start Integration Builder (SXMB_IFR) -> Integration Directory
• Create a new scenario object and save it
• Expand the above created object
• Choose ‘Service Without Party’
• Right-click on ‘Business System’ and choose ‘Assign Business System…’
• In the wizard, leave the Party name blank, select your BS and uncheck the box ‘Create Communication Channels Automatically’
• Expand your service (BS), right-click on ‘Communication Channel’ and select ‘New…’
• Name the communication channel as ‘File_sender’
• Choose adapter type as ‘File’ and option as ‘Sender’
• Specify the transport protocol, message protocol, adapter engine as shown
• Also specify the File Access Parameters and Processing Parameters as shown
• Sender file adapter is now configured
• Save the communication channel
• Similarly, create receiver communication channel ‘IDoc_Receiver’ with adapter type as ‘IDoc’, option as ‘Receiver’, Transport and Message Protocol as ‘IDoc’. You will also need to specify Adapter Engine, RFC Destination, Interface Version, Port and SAP Release. RFC destination must be defined in SM59 to point to the target SAP R/3 system, likewise port should defined using transaction IDX1.