Documente Academic
Documente Profesional
Documente Cultură
Background
Whenever large (binary) file needs to be transferred by using PI, there might be a chance for Out of Memory
error which might results in server restart. Technically, it often fails in the sender adapter.
The most popular work around is to split the file in to multiple parts in Sender Adapter and Combining them in
Receiver Adapter (via OS Scripts)
From PI 7.30 onwards File/FTP adapter natively supports transferring large size files by splitting them in to
smaller chunks based on the configured size. Each chunk will be processed as an individual XI Message in
sender adapter and all the chunks are combined based on the sequence in receiver adapter. Since all the
chunks have to be combined in the actual order, QoS EOIO has to be used to enable this feature.
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Configuration Options
Select 'EOIO' as a QoS under Processing tab.
Option 1
You can choose the required chunk size option from the given list of 1, 2, 5, 10, 20 and 50 MB.
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Option 2
Custom values which are not possible in default options can also be configured in additional parameters.
Parameter Name
Possible Values
chunkMode
chunkSizeKB
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Sender Adapter will create XI message with additional dynamic headers for each chunk and forwarded to
Messaging System for IRD processing.
Example
For this example, chunk size is configured as 2 MB and the below input file (~4.5 MB) is used.
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
For demo purpose and to identify/analyze how the actual split happens, the input file is created with the data
like below ( 1 to 600000)
As per the configuration, three chunks should be created with the size of 2 MB, 2MB and ~500 KB.
Chunk 1 (2 MB)
Transferring first 2 MB
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Chunk 2 (2 MB)
Transferring next 2 MB (Total 4 MB)
Dynamic Headers
The entire chunk mode related dynamic headers will be set under the namespace http://sap.com/xi/XI/System/
Generic
Header
Value
ChunkStart
ChunkMode
Active/End
ChunkKey
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
First Chunk
Next Chunk
Last Chunk
If multiple files sent from different file sender channels, receiver adapter uses the chunk key to identify the
proper output file(for combining). During the creation(and append) of output file, it uses the chunk key like
below.
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
In Temp mode, the temp files wont be deleted till the last chunk is received.
Recovery Mode
If the input file is very large, it would normally take more time to be transferred completely. If there is any
server failure in the middle, the transfer can resumed from the chunk it stopped (Not from the beginning)
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Payload of Chunk 1
Payload of Chunk 2
Payload of Chunk 3
As per the above screenshots, the split never cosiders the payload. It's just a binary split. So the following
limitations would apply
Only for File Sender to File Receiver
No Mapping
No Content Based Routing
No Content Conversion
No Custom Modules
Technically, other type of receiver adapters can be used. But it won't have the option to combine the chunks.
How to choose the chunk size? Smaller chunk size ensures more reliability?
Yes. But significantly affects the performance. Smaller chunk size creates more chunks (more XI messages)
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Troubleshooting
If chunks are stuck in the EOIO queue, it can be monitored with
http://host:port/MessagingSystem/monitor/sequenceMonitor.jsp
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)
Peter Hermanns
Jun 25, 2013 3:58 PM
Very good information. One additional point leading us to move to PI 7.31 in the near future i guess.
Mariana Mihaylova in response to Marilyn S on page 11
Jun 12, 2013 12:36 PM
Hi Jose, We will try to recover the missing images.
Marilyn S in response to Mariana Mihaylova on page 11
May 29, 2013 6:23 PM
Mariana
Still some images are missing.
Thanks,
Jose
Mariana Mihaylova
Aug 27, 2012 2:40 PM
Hi Siva, All
All images should be fine now.
Thanks,
Mariana
Sivasubramaniam Arunachalam in response to Goradindla Sreerama Reddy on page 11
Jul 12, 2012 3:55 PM
Hi Sreeram,
Due to SDN to SCN migration, few screenshots are corrupted. I will check with SCN team.
Thanks,
Siva
Goradindla Sreerama Reddy
Jul 12, 2012 3:52 PM
not able to view the screeb shots can you correct the screens shots
regards
Sreeram
Sivasubramaniam Arunachalam in response to Shabarish Vijayakumar on page 11
Jan 10, 2012 7:19 AM
Yes. But we can use it at our own risk.
Process Integration (PI) & SOA Middleware: File/FTP Adapter - Large File Transfer (Chunk Mode)