Runtime Properties for Messaging Types

The following tables describe the runtime properties set when creating a message service. These runtime properties are set when defining endpoints used for a message service sending outbound messages.

JMS

PropertyDescription
Non XA Queue Session Acknowledge Mode

Select one of the following:

AUTO_ACKNOWLEDGE: The session automatically acknowledges a client’s receipt of a message when it has either successfully returned from a call to receive or the MessageListener it has called to process the message successfully returns.

CLIENT_ACKNOWLEDGE: The client acknowledges a message by calling the message’s acknowledge method. Acknowledging a consumed message automatically acknowledges the receipt of all messages that have been delivered by its session.

DUPS_OK_ACKNOWLEDGE: This option instructs the session to lazily acknowledge the delivery of messages. If JMS fails, duplicate messages may be delivered. Use of this option can reduce session overhead because the session minimizes the work that prevents duplicates.

Non XA Queue TransactedSelect True or False
TimeoutDefault is 3000 seconds.
XA SupportSelect True or False.

File and FTP

PropertyDescription
Append Message CountIdentifies how many messages are written to a file before a new file is created. The default is 1, meaning one message per file.
DelimiterIdentifies any special characters that are used to separate messages. Required if Message Separator Mode is set to byDelimiter.
EncodingIdentifies the encoding of the specified attributes, such as File Header/Footer and Message Header/Footer, excluding the embedded XML message content.
File DirectoryRequired for FTP; not used for File. Identifies the output directory. Multi-byte characters are not supported for this property.
File FooterIdentifies the constant string used to end every file.
File HeaderIdentifies the constant string used to begin every file.
File Name PartIdentifies the outbound file name prefix. For FTP, multi-byte characters are not supported for this property.
Fixed LengthSets the expected message maximum length. Used only when either of the Message Separator Modes, byFixedLengthInBytes or byFixedLengthInChars, are set.
Maximum File SizeUsed to limit the output file size. When the Maximum File Size is reached, the file service does not append any more messages. At least one message is output to a file regardless of the designated Maximum File Size.

If Append Message Count is set to a value greater than 1 and is reached first, however, the file service stops appending messages before Maximum File Size is reached.

Message FooterIdentifies the constant string used after each message.
Message HeaderIdentifies the constant string used before each message.
Message Separator Mode

Choose one of the following:

byDelimiter: Separates messages by delimiter; use with the Delimiter property

byFixedLengthInBytes: reserves x bytes for each message, where x is set by the Fixed Length property

byFixedLengthInChars: reserves x characters for each message, where x is set by the Fixed Length property

ModeUsed for FTP only. Identifies the transfer mode. Choose one of the following:

ASCII

Binary

Padding ByteIdentifies the byte to be used to fill the remaining reserved space when byFixedLengthInBytes property is set.
Padding CharIdentifies the character to be used to fill the remaining reserved space when byFixedLengthInChars property is set.

Email

PropertyDescription
Close Connection after OperationSelect True or False.
XA SupportSelect True or False.

Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com