Database Communication Points

The Rhapsody Integration Engine comes with a number of different database communication points, each tailored to suit different scenarios. This section describes each of the communication points, and the scenarios in which they should be used:

Database Insertion Communication Point
Database Communication Point
Scenarios

Database Insertion Communication Point

The Database Insertion communication point allows a single row in a single table to be inserted or updated. The values to be inserted can be constants, message properties, fields, or the current date-time. While it is only useful in a limited number of scenarios, it is the simplest database component to configure and so should be used if only one row in one table needs to be changed. All the queries run by this communication point may be dynamic; that is, they can be parameterized based on values from a message.

Database Communication Point

Input Mode

The Database communication point in Input mode is used to poll a database table to detect changes. Once changes have been detected, the queries specified in the configuration are used to generate an XML message representing the new data. When running in input mode, the database communication point can be used with or without a 'key' value. When using a key value, the input database communication point requires that the main table contains a key column which can be used to order and restrict the rows returned. In addition, the queries it runs must be static; that is, they cannot be parameterized based on values from a message. When not using a key value, no key column is specified in the configuration, but the script must update the row so it does not get read again.

Output Mode

The Database communication point in Output mode is primarily used to insert or update data in one or more tables. The inserted data is usually sourced from a message flowing through Rhapsody, using either message properties, or fields directly from the message. The configuration is able to iterate over repeating fields in a message, thus inserting multiples rows into a table if necessary. All the queries run by this communication point may be dynamic; that is, they can be parameterized based on values from a message.

Out->In Mode

The Database communication point in Out->In mode operates in exactly the same manner as the Database Lookup filter. It is recommended that it be used in preference to the database lookup filter if any changes to the database are being made. There is no way to customize the SQL that is executed by this communication point, as it generates it internally based on the configuration.