The following tables identify the runtime properties that can be set for transports defined as inbound transports for Managing Transports Used for Access Configuration.
There are no runtime properties for an HTTP inbound transport.
Property | Description |
Check Interval | The interval, in seconds, that checks for new messages; the default is 50 seconds |
Folder Name | The name of the folder from which new messages are retrieved; the default is INBOX |
Folder Open Attr | The folder attributes, such as Read, Write, and Read/Write; the default is READ_WRITE |
XA Support | Select True or False to identify if transactionality is supported. |
File
Property | Description |
Delimiter | Identifies any special characters that are used to separate messages. Required if Message Separator Mode is set to byDelimiter. |
Encoding | Identifies the encoding of the specified attributes, such as File Header/Footer and Message Header/Footer, excluding the embedded XML message content. |
File Footer | Identifies the constant string used to end every file. |
File Header | Identifies the constant string used to begin every file. |
File Move to Directory | Identifies the directory to which the file is moved when the Move option is set for File Process. |
File Name Pattern | The regular Java expression that specifies what files to read; ".*" reads all files |
File Process | Identifies what is done after reading the file. Choose Delete, Rename, or Move. If Rename, renames the file and adds the File Rename Suffix. If Move, moves the file to the location identified by File Move to Directory. |
File Read Order | Identifies the order by which the files are read. |
File Rename Suffix | Identifies the suffix appended to the file name when the Rename option is set for File Process. |
Fixed Length | Sets the expected message maximum length. Used when either of the Message Separator Modes are set. |
Message Footer | Identifies the constant string used after each message. |
Message Header | Identifies 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 |
JMS
Property | Description |
Non XA Queue Session Acknowledge | 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 Transacted | Select True or False. |
Timeout | The number of seconds without establishing a connection before triggering a timeout. |
XA Support | Select True or False. |
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com