Configuring a database outbound protocol

You can use these steps to configure the SQL statement/stored procedure for the database outbound protocol.

In the Java driver and database protocols, one process only supports one Java or database protocol. They cannot be in the same process. In the Java driver, you can also run multiple instances in a single process.

  1. On the Database Outbound Protocol Properties dialog box, select a Database Connection (required). This lists all configured visible connections under the current site and master site. Master site connections are shown in italic.
  2. Select Close connection after write or Delay connection until needed. Both can also be selected.
    Close connection after write closes the connection after every outbound write. Clear this to keep the connection.
    Delay connection until needed delays the connection until it is required. Clear this to make the connection during thread start-up.
  3. Click the Message Format Select button to open the Select Record Format dialog box. This lists all selected visible table schemas under the selected connection. Make a selection and click OK.
    Sometimes, the format of the message coming in does not match any table schema, or, the table schema is unknown. If this happens, then you can use the VRL format option to define a VRL for messages without having to match any database table schema.
    To clear the text field, selectClear.
  4. For Action Options type, select SQL Statement or Stored Procedure.
    Selecting SQL Statement updates Content with the previous SQL statement content. Clicking Configure opens the Outbound SQL Statement Configurator dialog box, from which you configure the SQL statement.
    Selecting Stored Procedure is used mainly for selecting data with complex query conditions and deleting rows after reading. This updates Content with the previous stored procedure content. Click Configure to open the Stored Procedure Configurator dialog box, from which you configure the statement that calls the stored procedure.
  5. Select Use cached pre-xlate message as whole message to define whether the current thread uses the cached pre-xlate message or the outbound message as the whole message. When this is selected, the Database Outbound protocol driver attempts to extract the cached pre-xlate message from the message driver control. Then, it decodes it if it is waiting to be used.