The relevant objects are structured, organized, and saved in the Integration Directory in the form of configuration objects.
The Integration Directory is structured around the cross-system task areas.
1) Collaboration profile- Specify the potential senders and receivers of messages and the technical communication paths.
2) Receiver determination and interface determination define the flow of messages in a system landscape.
3)In Sender agreement and receiver agreement you define the technical details for message processing
The Business Scenario provides you with a central point of access for all integration objects such as interfaces, mappings, software components and so on.
To address a business system from the SLD as the sender or receiver of messages in logical routing, you must define it as a service (of type Business System) in the Integration Directory.
Create a Business System,Leave the party field empty to define the service as a Service Without Party.
Make specifications that specially refer to the service as a sender or receiver.
Now create two communication channels FILESENDER AND FILERECEIVER and assign them to the service.
Assign parameters for FILESENDER and FILERECEIVER communication channel
Select the File Adapter as shown from the adapter metadata.
Configure the Sender FTP adapter to be able to send files to the Integration Server.
FTP Connection Parameters
1)Enter the host name or IP address of the FTP server.
2)Specify the port number of the FTP server. The default is the standard port for the FTP server (21).
3)Connection mode Permanent
4)Set the FTP connection transfer mode to Binary.
5)Specify the directory where the files are located
6)set the Anonymous Logon User Name and password
7)specify the folder where the file is placed
8)Specify the name of the file that you want to process.
Since the text file to the Integration Engine,comprises complex data structures that are to be converted into an XML document, choose File Content Conversion and make the required entries for conversion under Parameters for Content Conversion as shown below
Configure the Receiver File/FTP adapter to save XML messages from the Integration Server in files
Now Define Sender Agreement, where you define how the message is to be transformed so that it can be processed by the Integration Engine. A sender agreement contains a reference to a communication channel. here the communication channel to define is FILESENDER.
In your Receiver Agreement you define how the message is to be transformed so that it can be processed by a receiver. A receiver agreement contains a reference to a communication channel In this case is the FILERECEIVER
ReceiverDetermination is a Configuration object in SAP Exchange Infrastructure that describes the assignment of a sender interface and an outbound interface to one or more receivers. Select the service and save.Then in the configuration overview refresh and check for the mapping program and Receiver Agreement.
You use an Interface Determination to specify for a sender and a receiver,which inbound interface is to be used for the inbound processing of a message.
In an interface determination you define the following for the outbound interface of a sender
1)An inbound interface(FILEOUTPUT_IB)
2)An interface mapping for the outbound and inbound interface (FILEINPUT_TO_FILEOUTPUT_INTERFACE)
Save and Activate in the change list where you select your saved objects. Now the status become from Being Processed to Active.
This configuration should convert the flat file like this.
The input.txt file placed in the Test folder is being picked and deleted since the processing mode is delete.
A new file output.txt is created with time stamp in the Test folder as shown below.
This completes the scenario.Please go through various blogs posted by fellow webloggers on to the sap exchange infrastructure forum for various other scenarios.