In recent days, when I went through the XI forum, I noticed the real need of a scenario which has to transfer some binary data from one location to another with the same filename. Hence, I decided to take this as a challenge and do it. This blog is about how I achieved file copy scenario using XI 3.0 SP 9 (without SP12). The easiest way to achieve this is using modules. h3. Overall process in a brief diagram 
Brief Description on the above diagram As a first step, the binary file is read by the module ‘ReadFileBean’ and converts the binary data into Base64. This module reads the filename directly form the Sender Channel. Both these are put into the tags and passed into the AFW. There mapping is made using the same data type and message type, and finally the XML is passed to the ‘WriteFileBean’ module. Here, this module converts the Base64 back to binary data, and writes into the directory found on Receiver Channel using the filename found on the tag. We will not use the CallSapAdapter module on Receiver Channel h3. Integration Repository Designs Data type design 
Message Mappings 
h3. Integration Directory Configurations Sender Channel 
You can notice the binary file (dll file) is read. Sender Module 
In the above figure, you can see that the ReadFileBean module is read before the CallSapAdapter. This helps the module to load first and transform the binary file to an XML file and send it to adapter engine. Receiver Channel 
In the above figure, only the target directory is read by the module and the filename is read from the tag. Receiver Module 
Brief Description on the above diagram As a first step, the binary file is read by the module ‘ReadFileBean’ and converts the binary data into Base64. This module reads the filename directly form the Sender Channel. Both these are put into the tags and passed into the AFW. There mapping is made using the same data type and message type, and finally the XML is passed to the ‘WriteFileBean’ module. Here, this module converts the Base64 back to binary data, and writes into the directory found on Receiver Channel using the filename found on the tag. We will not use the CallSapAdapter module on Receiver Channel h3. Integration Repository Designs Data type design Message Mappings h3. Integration Directory Configurations Sender Channel You can notice the binary file (dll file) is read. Sender Module In the above figure, you can see that the ReadFileBean module is read before the CallSapAdapter. This helps the module to load first and transform the binary file to an XML file and send it to adapter engine. Receiver Channel In the above figure, only the target directory is read by the module and the filename is read from the tag. Receiver Module
14 Comments
