Defining Module for EDI Properties

Property	Description
EDIBigDocThreshold	Determines the size at which Module for EDI considers a document to be large. Possible values are: 0 or -n. Zero or any negative whole number specifies that Module for EDI should consider no documents as large. The module processes all documents in the traditional manner, reading the document content into memory during processing. The default is -1. n. A positive whole number specifies the number of bytes over which Module for EDI treats a document as large. For example, if the value is 1000000, the module considers all documents greater than 1,000,000 bytes as large. Note: You must specify a threshold number that is at least three times the size of a document. For example, if the document size is 1 MB, set EDIBigDocThreshold to at least 3 MB. Otherwise, Module for EDI still treats the document as large even though its size is smaller than the threshold number.
EDICheckEncodingLength	Specifies the length of each portion of data to be validated for encoding.The Module for EDI validates an EDI document by dividing it into smaller portions of data where each portion of data is validated for encoding.You can add a suffix of K or M to the value. The default value is 20K.
EDIencoding	Specifies the character encoding for encoding EDI documents. The default is UTF-8. Module for EDI uses this property if it does not encounter an encoding variable in the pipeline.
EDIEncodingsToTry	Specifies a comma-separated list of character encoding to use if the default encoding standard property (EDIencoding) fails. If both the EDIencoding property and the EDIEncodingsToTry property fail, then the value for the file.encoding java system property is used. If this value is UTF-8, then ISO8859-1 is used.
EDIMaxFATransactionErrors	Specifies the maximum number of errors to report per FA transaction. Valid values are: n. Specifies the maximum number of errors that can be reported for any one FA transaction. The default is 100. -1. Specifies that any number of errors can be reported for any one FA transaction.
EDIUseNewRelationshipLabel	Indicates whether to display related documents identified by their control numbers or by their relationship labels on the Transaction Analysis page in My webMethods. Valid values are: true—Displays documents by relationship labels. false—Displays documents by control numbers. This is the default.
EDIAllowCustomControlNumberSequences	Specifies the control number sequence. Valid values are: false—Module for EDI looks up the next control number using the corporation names of the sender and receiver. This is the default. true—Module for EDI looks up the next control number using the sender and receiver IDs and qualifiers. If no record is found using this criteria, the module attempts to identify the sequence based on corporation names. If no sequence is found, the module creates a new sequence based on partner corporation names. strictCompatibility—Specifies whether to use either the external IDs of partners or their corporation names to define the control number sequence. Use this value for backward compatibility with Module for EDI 6.5.2 or if you want to adopt the sequence that a particular operation uses. (For example, with the batching feature, Module for EDI uses corporation names when generating outbound batches but uses sender/receiver IDs and qualifiers in services that add envelopes and groups.)
EDIResolveDuplicates	Specifies how Module for EDI assigns FA status when sending (or receiving) a document multiple times before the receiver returns an FA. false—When sending a document multiple times before the receiver returns an FA, the status of each document is set to None (“100”) in the EDITRACKING table. This indicates that Module for EDI has not yet received an FA. When the receiver returns an FA for one of these documents, the status of each document is updated to Duplicate (“120”), indicating that multiple documents exist in the EDITRACKING table that match this FA. This is the default. true—When sending a document the first time, its status is set to None (“100”) in the EDITRACKING table. This indicates that Module for EDI has not yet received an FA. If the same document is sent again before the receiver returns an FA: The status of the first document changes to Duplicate (“120”), indicating that multiple documents exist in the EDITRACKING table that match this FA. The status of the second document is set to None. This behavior occurs for each subsequent document sent before an FA is returned. When the receiver returns an FA, the FA acknowledges only the document that was sent last. The status of this last document is set according to the FA status reported in the FA document. The status of all prior documents remains Duplicate. Note: This behavior also applies to received documents.
disableCIDSupport	Specifies whether to disable the extraction of conversation IDs from EDI documents for Envelope and Group document types. true—Disables the extraction of conversation IDs from EDI documents for Envelope and Group document types. false—Enables the extraction of conversation IDs from EDI documents for Envelope and Group document types. This is the default. Note: For VDA documents, if you set this property to false, you must also add a package dependency from WmTN to WmPRT and then reload WmTN in order to extract the conversation ID correctly. For details, see the webMethods Service Development Help for your release.
ignoreFAStatusUpdateForOutboundBatch	Controls whether Module for EDI checks and updates the EDI FA Status of incoming EDI documents during batching. true—The module does not check and update the EDI FA Status. false—The module checks and updates the EDI Status. This is the default.
PersistUnchangedInboundEDIDocument	Specifies whether to persist EDI documents in Trading Networks exactly as they are received, without removing empty records and spaces between records. true—EDI documents are persisted exactly as they are received. false—EDI documents are persisted after removing empty records and spaces between records. This is the default.
EDIUseConvertToString61Behavior	Specifies whether Module for EDI performs less stringent validation during implementation of the wm.b2b.edi:convertToString service. Software AG recommends setting this property to false. true—Module for EDI performs less stringent validation against the flat file schema during implementation of the wm.b2b.edi:convertToString service. Specifically, Module for EDI prevents sorting the edidata from the wm.b2b.edi:convertToString service when the service’s input data does not follow the same order as the flat file schema and the sortInput parameter is set to false. false—Module for EDI performs stringent validation against the flat file schema during implementation of the wm.b2b.edi:convertToString service when the sortInput parameter is set to false. This is the default.
EDIDisableCONTRLVersion	Specifies whether both the release number and the version number of the UNIEDIFACT message are used to determine the version. Valid values are: true—Module for EDI considers only the release number of the UNEDIFACT message to determine the version of the UNEDIFACT message. false—Module for EDI considers both the release number and the version number when determining the version of the UNEDIFACT message. This is the default.
EDISchemaSource	Specifies whether the flat file schemas are created using either the SEF or XML files. The default is XML. Note: Ensure that the required schema packages are installed.
InstallSEFSchemaWithDescription	This property is applicable only when the EDISchemaSource configuration is set to sef. If InstallSEFSchemaWithDescription is set as true, while creating a Flat File Schema from a SEF file. The SEF file is read from packages\WmEDI\pub\SEFS\X12_SefDesc instead of packages\WmEDI\pub\SEFS\X12. The default value is false, which reads SEF files from packages\WmEDI\pub\SEFS\X12.