IBM DB2 is a relational database management system which brings data governance and security, low-latency transactions, and continuous availability to mission critical apps and operations. You can use IBM App Connect to build flows that integrate with IBM DB2 on-Cloud or Client Managed on LUW or IBM i and other applications.

Connecting to IBM DB2 on Cloud

To create an integration flow that passes key data between your database server and other applications, you must connect IBM App Connect to each application in the flow. You can add an account to connect to the database either from the IBM App Connect Catalog page or when you add an IBM Db2 on Cloud action to a flow in the flow editor.

For more information on connection fields, see How to use IBM App Connect with IBM Db2.

Once you have connected to the IBM DB2 on Cloud, you can create an event through events by polling on new or updated records, and from the action side you can discover tables available on the database endpoint and perform CRUD (Create, Retrieve, Update, and Delete) operations ( Views are also supported but for the Retrieve operation only) as well as custom Select operation on them.

• Figure 1 - IBM DB2 event and action nodes

Figure 2 - Example of a list of available tables when connected to the IBM Db2 on Cloud

Using IBM DB2 on Cloud with App Connect

The following scenarios demonstrate how you can use IBM DB2 on Cloud in App Connect to perform automation tasks.

Use case scenario - Create an incident in ServiceNow whenever a new customer issue record is added to IBM Db2

• A customer support system of XYZ company is built on IBM Db2 to manage customer information and handle reported issues. To improve their incident management process and ensure the timely resolution of critical issues reported by customers, the issues are immediately escalated and tracked in ServiceNow as incidents.

• On IBM App Connect, the IBM Db2 connector allows polling for any new or updated events. For the above scenario, we use a configurable polled event called the New CUSTOMER ISSUES record from the IBM Db2 connector.

Figure 3: A list of configurable polled events

• Figure 4 displays the overview of an event-driven flow called Create an incident in ServiceNow whenever a new customer issue record is added to IBM Db2. This flow uses an IBM Db2 New CUSTOMER ISSUES record (event poller) as the trigger node and ServiceNow Create incident action node. This flow syncs customer issues from the IBM Db2 database to ServiceNow. So, every time a new customer issue is added to the database, the issue details are used to create an incident in ServiceNow.

Figure 4: Event-driven flow to store the issue details in ServiceNow when a new customer issue record is added to the IBM DB2 connector

• Figure 5 displays the ServiceNow Create incident action node and how the data pulled from the database is mapped to various fields in the ServiceNow incident.

Figure 5: ServiceNow action node and its data mapping

• Figure 6 displays the insertion of the customer issue record using an SQL query that will trigger the event-driven flow on App Connect.

Figure 6: Inserting a record in IBM DB2 database

• Figure 7 displays the customer issue details in ServiceNow with the data adhering to the new incident record in the database.

Figure 7: Synced ServiceNow incident record with the new customer issue details

This scenario demonstrates how you can use IBM App Connect to automatically sync incident information between IBM Db2 and ServiceNow to update relevant teams when the information has been retrieved.

For more information about other supported connectors in IBM App Connect, see Connectors.