Print Page

Monday, February 18, 2008

Large EDI File Processing

This challenge is addressed by writing the payload to a input directory. The corresponding translated payload will also be written to an output directory.

p.s As a pre-requisite always apply the latest patch and set the appropriate heap size as per the performance best practice post.

1. Set the heap size as discussed in the peformance post.
2. Apply the latest patch.
3. You will need to set following two properties in

1) oracle.tip.adapter.b2b.edi.incoming.wiremessage.size
Specify the size of incoming EDI message that must be treated as large enough
to be kept in file system instead of memory, during message processing. The size
specified is in bytes.

Default is 300 MB (300000000)

Specify directory where large incoming message must be saved.

4. For outbound consider File batching as well as Disk caching.

These are the parameters needed to set for this in file -

# entries to support large file outbound processing
#outputSize is expressed in bytes

#entries to support no-lock processing of batched outbound messages

#entries to support splitting large batched outbound into smaller batches
#value determines size of smaller batches split off from the large batch
#if this property exists and is set to a value, then #oracle.tip.adapter.b2b.edi.outputDirectory
#and oracle.tip.adapter.b2b.edi.outputSize must be specified.
#if this property exists and is set to a value, oracle.tip.adapter.b2b.edi.fileBased #can be either true or false. true is preferred.

#Entry for file-based processing across multiple B2B instances.\\Oracle\\Product\\DVAPPSRV01\\ip\\log\\filebased.

No comments: