Field Description
Inbound
Publish XML Request as File Reference
Write the converted XML or TEXT to a file for each inbound transaction and publish the file reference in the requestFile attribute of the ResponderRequest message to the private process. Use of this option can decrease memory usage, improving performance. The Threshold property determines how large the XML must be before BusinessConnect
Container Edition writes the request to a file; other status values from the user are considered a failure.
Threshold (bytes) Specify a file size in bytes. The default value is 0. TIBCO BusinessConnect Container Edition writes XML requests that are this size and larger to a file and sends a reference to that file instead of the request itself. A value of 1000 is often appropriate. This can decrease memory usage within the EDI processing component, improving performance.
Include Date Folder Select this check box to create a file reference in a created folder based on the current date. This check box is selected Advanced Fields
70 | Configuring the X12 Protocol for Host
Field Description
by default.
Store Location Identify the directory in which TIBCO BusinessConnect Container Edition must store the files. If this field is empty or the directory specified is not valid, TIBCO BusinessConnect Container Edition behaves as if Publish XML Request as File Reference is not checked; it does not store a file; it sends the XML request.
Output XML Request in UTF-8 and Remove Empty Elements
Select this check box to instruct TIBCO BusinessConnect Container Edition to perform the following tasks:
l Convert the XML that is in UTF-16 format to UTF-8;
l Delete XML elements in the request that contain no values. This reduces the file size. Reducing the request size is especially important when you are using the XML for back-end processing.
Note: Converting the XML from UTF-16 to UTF-8 in this way increases memory usage. Consider converting the XML to UTF-8 in a separate JVM process instead of using this option.
Use In-memory Compression During EDI to XML Conversion
Select this check box to instruct TIBCO BusinessConnect Container Edition to compress information stored in memory during the EDI to XML conversion process. Although
compressing and uncompressing data increases the processing time of the conversion process, it can greatly reduce memory usage.
This option is useful when processing interchanges that contain a large number of messages. By default, this check box is unselected.
Threshold to Use File-based Storage During EDI to XML
Specify the threshold to use file-based storage during EDI to XML conversion.
Advanced Fields(Continued)
71 | Configuring the X12 Protocol for Host
Field Description
Conversion (bytes) This threshold has a default value of 20,000,000 bytes (20 MB).
This threshold is triggered only when an inbound message comes in from a trading partner and the threshold is applied on Interchange basis: if the size of the interchange is greater than the threshold, the BusinessConnect EDI engine makes the conversion engine in-built validate and process all the transactions in that interchange, including errors on the disk. Only one currently processed transaction is loaded into memory and discarded after processing in chunks, saving memory and keeping it low. This also supports the
interchange to process a lots of errors without loading them into memory.
Frequent use of this threshold feature for very small sized files slows the performance depending on the network and I/O performance. It must be used only for fairly large interchanges, or for interchanges with lots of errors Inbound and Outbound
Threshold to Use File-based Storage Prior to EDI Processing (bytes)
Specify the threshold to use file-based storage prior to EDI processing.
This threshold has a default value of 1,000,000 bytes (1MB).
This threshold is triggered for both outbound and inbound messages and applies on an interchange basis. If the
interchange or XML (in case of outbound) is greater than the threshold, it makes sure to be written to a temporary local file and given to the conversion engine instead of passing it as a blob to the engine. This reduces the memory
consumption prior to EDI processing.
This threshold does not resolve large number of smaller transaction details that are in memory, or the number of errors that can still accumulate during processing by the Advanced Fields(Continued)
72 | Configuring the X12 Protocol for Host
Field Description
conversion engine.
AuditReportLogging
Audit Report Location Specify the location used for audit reporting in EDI to XML processing when TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® validates and converts.
The Audit Report files are generated by the Instream
validation engine in XML form. The Audit Report location is also needed to be populated with an appropriate value when Insight Reporting Information is published to the private process The XML files have additional information pointing to the internal details of the validated transactions.
Example: C:\temp\DocSplitReport
Include Date Folder Select this check box to create a file reference in a created folder based on the current date. By default, this check box is selected. • If you select this check box, the date folder is added to the document path. • If you clear this check box, the date folder is omitted, and the document is stored under the tpName directory.
Advanced Fields(Continued)
73 | Configuring the X12 Protocol for Trading Partners