Flag | Value | ||
recWithNoIDLike46 | Determines how the pub.flatFile:convertToValues service handles recordWithNoID records. ![]() ![]() | ||
alwaysSortFields | Determines whether the pub.flatFile:convertToString service checks the order of the fields in composites and records that it receives as input (in ffValues) against the flat file schema that is specified in the ffSchema input parameter. ![]() ![]() | ||
allowSubfieldDelimiterIn NonCompositeField | Determines whether Integration Server Flat File Adapter allows subfield delimiters in non-composite elements. ![]() ![]() | ||
dontTrimControlCharacters | Determines how whitespace and control characters are handled by the service wm.b2b.edi:convertToString when the parameter spacePad is set to left or right. ![]() ![]() | ||
recordIdentifierCheck | Determines whether the pub.flatFile:convertToString service includes the record identifier in the string output parameter. ![]() ![]() | ||
spacePadJustifies | Controls how the input parameter spacePad justifies fixed length fields handled by the services pub.flatFile:convertToString and wm.b2b.edi:convertToString. ![]() ![]() ![]() ![]() ![]() ![]() This is the default. spacePadJustifies has no effect when spacePad is set to none. | ||
UNAOnlyForImmediateUNB | Controls how EDIFACT documents with multiple interchanges are validated when an interchange does not contain a UNA segment. When none of the interchanges contain a UNA segment, each interchange is validated against the default delimiters regardless of the value of this property. ![]() ![]() | ||
useAlternateCodeSets | Determines whether to enable the use of alternate code sets. ![]() ![]() | ||
useG11NEncodings and alwaysUseWebMEncodings | Determines whether the pub.flatFile:convertToValues and pub.flatFile:convertToString services use the webMethods charset or the default charset provided by JVM. ![]() ![]() The default value for alwaysUseWebMEncodings is false and useG11NEncodings is true. Example: alwaysUseWebMEncodings=false useG11NEncodings=true | ||
useReadableDelimiterReporting | Controls how the delimiter record parser parses non-readable delimiters, such as \r (carriage return), \n (line feed), or \t (tab). ![]() ![]()
This impacts how you can use the delimiter information in flow mapping. If you use the delimiters directly in flows with variable substitution, non-printable characters will not be substituted correctly when useReadableDelimiterReporting=true. For example, when the output of the pub.flatFile:convertToValues service shows that the record delimiter is \n and a user flow has an input set to the following: abc%@delimiters\record%def the resulting value will be as follows: If useReadableDelimiterReporting=true, the resulting value is abc\ndef. If useReadableDelimiterReporting=false, the resulting value is abc def |
Note: | When processing many small files, a file polling port might become disabled and the following exception might be returned: java.lang.IllegalArgumentException: Comparison method violates its general contract. If this occurs, modify the custom_wrapper.conf file to pass the following Java system property to Integration Server: java.util.Arrays.useLegacyMergeSort=true. For information about how to pass Java system properties to Integration Server, see webMethods Integration Server Administrator’s Guide |