This weblog tries to explain and answer some of the queries (ex. , etc) from the forum where the requirement was to make XI as a FTP to transfer files. The trick # involved is to use a combination of 1. A Generic content conversion or Avoid Content Conversion (See Update Section Below)2. No Mapping and 3. Adapter Specific Message Properties (most of the case you will need the same file name at the target end too) Avoiding content conversion will make the scenario more generic. Hence any file irrespective of its file type can be picked up by the File Adapter. You can ignore the screenshots of the file adapter configurations (Sender and Receiver) and refer the UPDATE section to configure it to pick and post files irrespective of its type. To acheive the Generic content conversion an assumption is made that every file has it's end Separator as a new line (which i believe is a standard norm we encounter). For example my test file is as follows: 01,TYPE,DATE,30032006 02,SHABZ,T-SYS,XITEAM 02,ANISH,T-SYS,XITEAM 02,ALBY,T-SYS,ABAPTEAM 02,RATHEESH,T-SYS,ABAPTEAM 03,TRAILER The field separator might be different for other files and even the number of fields. The file can also be a fixed field length type. So we configure our file adapter to pick any file suiting the criteria so that it picks the file irrespective of its field separator or it being a fixed field length type but keeping in ming that each record in file would be separated by a new line. You can also have a look at Configuring Generic Sender File CC Adapter weblog which employs the same logic as we are going to implement here. The Data type created is as follows; (It will be of the Record-Row kind, the content conversion of which will be shown later) In case of avoiding the Content Conversion, we can use a dummy Data type and its corresponding Message type. This dummy message type can be hence used in the message interfaces.
The following is its corresponding Message Type. 
Now the trick is in the creation of the message interface. Use the same message type created in both the outbound and inbound message interface.Outbound Message Interface:
Inbound Message Interface:
Do not create any Mappings and hence no interface mapping too. In the Configuration we look at the Sender and Receiver File Adapter configurations. Sender File Adapter#:Refer the UPDATE section to configure the File Adapter without content conversion
Receiver File Adapter#:Refer the UPDATE section to configure the File Adapter without content conversion
The rest of the configuration is done as in any normal scenario except that we wouldnt specify an interface mapping during the creation of the interface determination. 
Once saved and activated our scenario should be up and running. Note: In order to get the functionality of the same file name in the destination refer The specified item was not found. weblog (SP14 and above) #UPDATE : Do refer the discussion (comments) below. As JK mentioned, we can avoid the whole content conversion itself by using the Message protocol as 'File'. This will pick any file may it be a .txt, .pdf, .doc or .xls (and much more) extension. As I mentioned earlier, in combination with the adapter specific message properties (SP 14 and above), we can get the same file name/file extension of the source at the target side too. Try a minor change to the File Adapter configuration as shown below ; Sender File Adapter : Message Protocol : File File Name : *.* In Adapter specific message properties : Enable File Name & File Type Receiver File Adapter : Message Protocol : File File Constuction Mode : Create In 'Adapter specific message properties' : Enable File Name & File Type Thus the restriction on the file structure can be avoided. And in case of large files to be FTPed we could try the approach suggested by Mike A New Approach: Have a look at this latest How to send any data (even binary) through XI, without using the Integration Repository which talks of even avoiding the IR completely for such a scenario.
The following is its corresponding Message Type. Now the trick is in the creation of the message interface. Use the same message type created in both the outbound and inbound message interface.Outbound Message Interface:Inbound Message Interface: Do not create any Mappings and hence no interface mapping too. In the Configuration we look at the Sender and Receiver File Adapter configurations. Sender File Adapter#:Refer the UPDATE section to configure the File Adapter without content conversionReceiver File Adapter#:Refer the UPDATE section to configure the File Adapter without content conversion The rest of the configuration is done as in any normal scenario except that we wouldnt specify an interface mapping during the creation of the interface determination. Once saved and activated our scenario should be up and running. Note: In order to get the functionality of the same file name in the destination refer The specified item was not found. weblog (SP14 and above) #UPDATE : Do refer the discussion (comments) below. As JK mentioned, we can avoid the whole content conversion itself by using the Message protocol as 'File'. This will pick any file may it be a .txt, .pdf, .doc or .xls (and much more) extension. As I mentioned earlier, in combination with the adapter specific message properties (SP 14 and above), we can get the same file name/file extension of the source at the target side too. Try a minor change to the File Adapter configuration as shown below ; Sender File Adapter : Message Protocol : File File Name : *.* In Adapter specific message properties : Enable File Name & File Type Receiver File Adapter : Message Protocol : File File Constuction Mode : Create In 'Adapter specific message properties' : Enable File Name & File Type Thus the restriction on the file structure can be avoided. And in case of large files to be FTPed we could try the approach suggested by Mike A New Approach: Have a look at this latest How to send any data (even binary) through XI, without using the Integration Repository which talks of even avoiding the IR completely for such a scenario.
17 Comments
