Note: This section applies to the Cleo Harmony and Cleo VLTrader applications only.
In the web UI, go to . In the native UI, select .
Use the Databases panel to configure one or more databases to be used either for VersaLex Transfer Logging or one of the optional Cleo VLNavigator applications. See Transfers and Applications. When you click New Database Connection, the Database Connection Configuration dialog appears. Enter values for the following fields:
- Connection Type
- Choose ODBC for databases where ODBC (Open DataBase Connectivity) is used. Choose MySQL Connector/J if a MySQL JDBC connection is used. Otherwise, select Other.
- Connection String
- JDBC connection string for accessing the database.
- Driver String
- This string describes the path to the Java class that will be used for accessing the database.
- Username
- Username for accessing the database (if required).
- Password
- Password for accessing the database (if required).
- Single Record Timeout (seconds)
- Prevents VersaLex from hanging on single-records transactional (that is, transfer log and operator trail log) inserts and updates.
- Test Database Connection
- Attempts to create a database connection using the entered Connection String, Driver String, Username, and Password and indicates success or failure.
See Database Definitions for information about JDBC drivers and driver/connection string values.
Database payload
See Sending database payload and Receiving database payload 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.
- Maximum supported BLOB size
- The maximum BLOB size supported by the database (incoming and outgoing payload will be stored in a BLOB data type).
- Polling interval for new outgoing payload
- The frequency at which VersaLex will check for new outgoing payload.
- 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.
- Maximum failed outgoing payload send attempts
- Dictates how many total times a transfer will be attempted before retries are halted.
- 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.
- 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.
- 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.
- 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.
- Maximum number of database connections
- If selected, specifies the absolute maximum number of allowed database connections (including poolsize) for database payload.
- Reserve connections for incoming
- Percentage of the maximum number of database connections to reserve for incoming requests.
- Automatically clear outgoing payload after successfully sent
- Indicates whether successfully sent payload should be automatically cleared by VersaLex.
- 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.
- 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.
- 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.
- Temporarily suspend incoming/outgoing database payload
- Indicates whether the database payload feature has been temporarily put on hold by a user.
- 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.
Comments
0 comments
Please sign in to leave a comment.