WBI JDBC Adapter Migration sample

This sample recreates a scenario in which a message flow with a JDBC Adapter and MQInput node is migrated to a message flow that uses a DatabaseInput node. It demonstrates how to:

Replace an MQInput node with a DatabaseInput node
Create ESQL code that matches the following WBI JDBC Adapter functionality:
- Selecting updated events from the event table based on the status column
- Creating RFH2 Headers with message metadata
- Creating output message of different types and namespaces depending on the changed Application Table
- Creating output messages with a tree structure based on the foreign keys of the table

You don't need to have WBI Adapters installed to run this sample; all of the required database tables, message queues, and flows are included. The objective is to demonstrate the difference between a typical WBI JDBC Adapter deployment and the equivalent flow in which IBM Integration Bus performs all of the work. To use a more complex schema for the database, you can extend the sample.

NOTE: In WebSphere Message Broker Version 8.0, IBM Integration Bus 9.0 and later, message model schema files contained in libraries are the preferred way to model messages for most data formats, including the new DFDL domain. Message sets continue to be supported, and are required if you use the MRM or IDOC domains. You can continue to import and deploy message sets for use in message flows. However, if you need to create one or more message sets, message definitions, or message categories when using this sample, you must first enable message set development in the IBM Integration Toolkit. For more information, see Enabling message set development in the IBM Integration Bus documentation.

Click the following links to find out more about the sample and about how to get the sample to run by using the wizards.

Import and deploy: 5 minutes

Read about the sample

Set up the database

You can set up the sample in one of the following ways:

Import and partially deploy the sample
This option imports the sample files into your workspace, and also creates an integration server and WebSphere MQ queues. Use this option if you are not familiar with setting up database tables. An SQL script to set up the tables is imported into your workspace; see Setting up the database tables by using SQL scripts. Run this script before deploying the broker archive (BAR) file to the integration server.
Import the sample
This option imports the sample files into your workspace. Additional manual steps are required to configure the sample for testing.

You can import or import and deploy a sample only when you use the information center that is integrated with the IBM Integration Toolkit.

Run the sample

Extend the sample

When you have finished with the sample, you can remove the database. See Cleaning up the database.

When you have finished with the sample, you can remove it in one of the following ways: