See Database Definitions
for information about the database payload feature.
- Database Incoming Mailboxes
-
For each trading partner mailbox, indicates whether VersaLex incoming payload should
be inserted into the database rather than write to the file system.
- Possible values: Selected or
Unselected
For incoming transfers to enabled mailboxes, if the database is not currently
available, the transfer from the trading partner is not accepted.
- Default value: Unselected
- Maximum supported BLOB size
-
The maximum BLOB size supported by the database (incoming and outgoing payload will
be stored in a BLOB data type).
- Possible values: Dependent on database
- Default value: 65535 bytes
- Polling interval for new outgoing payload
-
The frequency at which VersaLex will check for new outgoing payload.
- Possible values: 5-60 seconds
- Default value: 5 seconds
- Outgoing payload attempt timeout
-
For abnormally terminated or unresponsive sends, the timeout at which the send will
be retried by either a parallel or restarted VersaLex.
- Possible values: 10-60 minutes
- Default value: 30 minutes
- Maximum failed outgoing payload send attempts
- Dictates how many total times a transfer will be attempted before retries are halted.
- Possible values: 0-n
- Default value: 0 (no maximum)
- Maximum number of concurrent sends
- Maximum number of concurrent outgoing database payload actions that can be active at
any given time. If the limit is reached and more outgoing payload is found, it is put
on hold until one of the current outgoing database payload actions completes.
- Possible values: 1-n
- Default value: 50
- Maximum number of concurrent sends per mailbox
- Maximum number of concurrent outgoing database payload actions that can be active at
any given time for any given mailbox. If the limit is reached and more outgoing
payload is found for a mailbox, it is put on hold until one of the current outgoing
database payload actions for that mailbox completes.
- Possible values:
1-n and
<= Maximum number of concurrent
sends
- Default value: 5
- Bundle (serialize) same mailbox sends per mailbox
- At each polling interval, indicates to bundle payload for the same mailbox together
up to the configured amount and send one-by-one using just one mailbox session.
- Possible values: Selected or
Unselected
2-n
- Default value: Unselected
5
- Database connection poolsize
- If database payload is enabled, indicates the number of database connections
immediately obtained and continually reused. These connections are used strictly for
database payload.
- Possible values: 0-n
VersaLex will still obtain connections above the
poolsize specified when necessary and will continue to reuse those connections until
they become idle for an extended period of time.
- Default value: 20
- Maximum number of database connections
- If selected, specifies the absolute maximum number of allowed database connections
(including poolsize) for database payload.
- Possible values: Selected or
Unselected
Poolsize-n
- Default value: Unselected
0
- Reserve connections for incoming
- Percentage of the maximum number of database connections to reserve for incoming
requests.
- Possible values: 0-75 percent
- Default value: 33 percent
- Automatically clear outgoing payload after successfully sent
-
Indicates whether successfully sent payload should be automatically cleared by
VersaLex.
- Possible values: Selected or
Unselected
- Default value: Selected
- Stream incoming payload direct into the database
- Indicates whether incoming payload should be streamed directly into the database or
through a temporary file. For Oracle and MySQL, this may need to be turned off
depending on specific database and driver versions and configuration. This option is
not available on SQL Server nor DB2, as a filesize must be known prior to initiating the
stream.
- Possible values: Selected or
Unselected
- Default value: Selected
- Include user inbox subdirectories as incoming database payload
-
Indicates whether files stored by a connected HTTP, FTP, or SSH FTP client in a
subdirectory of their configured inbox should be inserted into the database.
- Possible values: Selected or
Unselected
When this value is false, only files stored in (or
renamed into) the user’s inbox are inserted into the database.
- Default value: Unselected
- Include user outbox subdirectories as outgoing database payload
-
Indicates whether files retrieved by a connected HTTP, FTP, or SSH FTP client in a
subdirectory of their configured outbox should be updated in the database.
- Possible values: Selected or
Unselected
When this value is false, only files retrieved
from the user’s outbox are updated in the database.
- Default value: Unselected
- Temporarily suspend incoming/outgoing database payload
- Indicates whether the database payload feature has been temporarily put on hold by a
user.
- Possible values: Selected or
Unselected
- Default value: Unselected
- Unlike all other VersaLex configuration parameters, these parameters are stored in the
database rather than the conf/Options.xml file.
- Retries are automatically scheduled based on Autosend Retry
Attempts and Autosend Restart. See Other system options.