Using the Database Filters

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

Which Database Filter Should I Use?

Database Lookup Filter

The Database Lookup filter is used to retrieve values from a database and store them in either message properties or directly in the message itself. Generally it is used to update the message flowing through it with some values from the database. All the queries run by this communication point may be dynamic; that is, they can be parameterized based on values from a message. While this filter can iterate over repeating fields in a message, and can execute the same query multiple times with different parameters, it requires that result sets returned from those queries return a maximum of one row.

Refer to Database Lookup for details.

Database Message Extraction Filter

The Database Message Extraction filter will generate an XML message from a database query, replacing the body of the incoming message. The difference between this filter and the Database communication point (in input mode) is that the query is triggered by an incoming message (compared to a time-based query), and the queries that it runs may be dynamic - that is they can be parameterized based on values from a message. Note that the message body is replaced by the XML message created by querying the database.

Refer to Database Message Extraction for details.

Scenarios

• Database Lookups
  • Conditional Execution for Lookups
  • Lookup Patient Information
  • Retrieving Information From a Database
• Retrieving Patients Contact Details Using a Patient ID

See Also...

• Database Communication Points
• Main Database Configuration