Large document handling
webMethods B2B Integration loads the content of a document in its memory, when it processes the business documents. For large documents, this process might lead to memory constraints. These constraints are noticeable when webMethods B2B Integration runs a query on EDI or XML documents during the document recognition or when it tries to perform pre-processing or processing actions.
webMethods B2B Integration removes these constraints with a process to handle large documents. It saves the content of large documents in a temporary space, reads the content in fragments, and processes the document by retrieving a specified number of bytes as configured in the General configuration.
When large document handling is enabled in your tenant, you must configure the property Large document threshold in webMethods B2B Integration > Administration > General configuration > Large Document Handling.
Specify when webMethods B2B Integration must consider a document as a large document. When webMethods B2B Integration receives a document that matches the specification, it processes the document as a large document.
Enabling large document handling
To enable the webMethods B2B Integration large document handling feature, contact the IBM® support team.
Defining size for large documents
The following list provide the threshold limit for a large document:
- The maximum limit, a document is considered large if it exceeds 31457280 bytes (30 MB). webMethods B2B Integration supports the payload of up to 500 MB.
- The minimum limit, any document at least 1048576 bytes (1 MB) can be considered large. Configure the value that you want in the General configuration.
- The default value is 5242880 bytes (5 MB).
Also set the Query threshold, which is the maximum size of the payload webMethods B2B Integration reads to run the queries that are defined in an XML or EDI document type.
For more information, see Configuring general options.
Channel for large documents
When webMethods B2B Integration large document handling is enabled in your tenant, two endpoint URLs for the inbound channel appear.
For more information, see Creating channel.
Points to note
- When you call an integration from webMethods B2B Integration to webMethods Integration, the content for the large document is null. To view the content of the large document, you must call getTransactionContentParts from webMethods B2B Integration operations in webMethods Integration.
- Set the contentType in the submit operation to application/EDI for VDA payloads.
- Use application/EDIStream for large documents for the contentType in the submit operation.
- Operations convertDocumentToEDIMessage, convertEDIMessageToDocument, and processEnvelope support the processing of large documents. For more information about detailed changes for large documents in EDI connector.
- In the webMethods.io B2B Connector -
- For the addTransactionContentPart operation, you must set the input parameter readContentAs as type stream for a payload over 5 MB.
- For the submit operation, you must set the input parameter readContentAs as type stream for a payload over 5 MB.
- Do not submit multiple large documents simultaneously for processing.
Limitations
- You cannot view and download the content of the large document through Partner Portal.
- EDI transaction size must not exceed 50 MB.
- When a large EDI payload is submitted with the Validate document structure enabled in webMethods B2B Integration, you might receive a timeout error if there is no response from webMethods Integration within 5 minutes.
-
webMethods B2B Integration
does not support the following functions:
- The validation for XML and flat file large documents.
- The verification of the digital signature for XML large documents.
- The processing and reprocessing of cXML documents as large documents.
Workaround - Change the value that is configured in the Large document threshold field as per the cXML payload size or higher, and reprocess the document.
- EDI standards VDA and Tradacoms for large documents.