Configuring Batch Adapter BatchRecord Connectivity Map Properties

Parse or Create Mode

Specifies how this adapter Connection for the record-processing OTD is used. Set this parameter as follows:

• Parse: To use the OTD for parsing an inbound payload.

• Create: To use the OTD for creating an outbound payload.

  An instance of the OTD can be used for parsing an inbound payload (only) or for creating an outbound payload (only). A single OTD cannot be used for both purposes at the same time in the same Collaboration.

Select Create or Parse.

The configured default is Parse.

Synchronized

Specifically applies to legacy Batch adapter Projects. Provides backward compatibility to allow Projects that were created using the Batch adapter version 5.0.7 or earlier to be imported and deployed without a change in the adapters behavior. The selections are, 

• Yes: Provides backward compatibility for legacy (pre-5.0.8 Batch adapter) Projects. The adapter run in synchronized mode, one instance of the Collaboration after the other.

• No: For use with new Batch adapter Projects. The adapter run in parallel, creating multiple instances of the Collaboration that run in parallel.

  ---

  Note –

  All OTD instances used in a Project should have the same value for this property.

  ---

Select Yes or No.

The default setting is Yes, simulating Projects created with Batch adapter version 5.0.7 or earlier.

Delimiter on Last Record

Allows you to supply the delimiter to be used with the final record. Use this parameter only when the Record Type is set to Delimited.

Some message formats insist that the final message in a record set has no trailing delimiter. However, in most cases, you can safely leave this parameter set to Yes.

Select Yes or No.

The configured default setting is Yes.

Record Delimiter

Specifies the delimiter to be used for records. Use this parameter when the Record Type is set to Delimited.

The value entered is interpreted as a sequence of one or more bytes. If there are multiple bytes in the delimiter, each must be separated by a comma. You can enter the delimiters in the following formats: 

• ASCII Characters: The adapter supports all ASCII characters.Example: *,*,* (records separated by ***)Example: | (records separated by a |)

• Escaped ASCII: The adapter supports \r, \n, \t, and \f.Example: \r,\n (records separated by CR NL)Example: \n (records separated by NL only)

• Hex: The adapter supports 0x00 to 0x7EExample: \0x0D,\0x0A (records separated by CR NL)

• Octal: The adapter supports 000 to 0177.Example: \015,\012 (same as \0x0D,\0x0A)

  ---

  Note –

  When using character delimiters with DBCS data, use single byte character, or equivalent hex values that do not coincide with either byte of the double byte characters. When using escaped ASCII, Hex, or Octal, the “\” character is required.

  ---

A valid character to use as data record delimiter. 

Record Size

Specifies a number indicating the record size (byte count). Use this parameter when the Record Type is set to Fixed, and a number indicating length must be supplied.

A number from 1 to 2,147,483,647 indicating the record size (byte count).

Record Type

Specifies the format of the records in the data payload in the Collaboration.

Each payload contains zero or more records. Using this and related parameters, you can pass records individually to another component within the Service Bus. Available options: 

• Delimited: The records are separated by the delimiter specified under the Record Delimiter parameter.

• Fixed: The records are all of a given size, specified by the Record Size parameter.

• Single Record: If the payload is to be processed “as-is,” select this option.

• User Defined: This option is not supported.

Select Delimited, Fixed, or Single Record.

The configured default is Delimited.