IBM Db2 is a database that is built to power low-latency transactions and real-time analytics at scale. It provides a single engine for DBAs, enterprise architects, and developers to keep critical applications running, store and query anything, and power faster decision-making and innovation across your organization. IBM App Connect supports IBM Db2 for i for use in event-driven flows and API flows.
Connecting to IBM Db2 for i
To create an integration flow that passes key data between your database server and other applications, you must connect App Connect to each application in the flow. You can add an account to connect to the database either from the App Connect Catalog page, or when you add an IBM Db2 for i action to a flow in the flow editor.
For detailed information on connection fields, how to generate connection field values, and how to use the Templates gallery, see How to use IBM App Connect with IBM Db2 on the IBM Documentation page.
Once you have connected to the IBM Db2 for i, 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 - Example of a list of available tables and views when connected to the IBM Db2 for i
Using IBM Db2 for i with App Connect
The following scenarios demonstrate how you can use IBM Db2 for i in App Connect to perform automation tasks.
Use case scenario - Store the issue data in IBM Db2 whenever a new issue gets created in Jira
A software development company utilizes Jira as its primary issue tracking and project management tool. The company wants to synchronize the issue data from Jira with an IBM Db2 database. To seamlessly integrate the two systems and keep the data synchronized, the company leverages IBM App Connect with its Jira and IBM Db2 connectors. Whenever a new issue is created in Jira, all the details get synced to the IBM DB2 database. The issue details fetched from the IBM DB2 database will be further used to facilitate better tracking, analysis, and decision-making processes for the software development projects.
Figure 2 displays an event-driven flow called Store the issue data in IBM Db2 whenever a new issue gets created in Jira. This flow uses a Jira New issue trigger node and an IBM Db2 Create JIRA_ISSUES record action node. This flow syncs issue data from Jira to the IBM Db2 database. So every time a new issue is created, all the relevant issue data are stored in the IBM Db2 Database.
Figure 2 - Event-driven flow to capture Jira issues.
Figure 3 displays the creation of the issue from the Jira website that will trigger the event flow on App Connect.
Figure 3 - Issue creation from Jira website
Figure 4 displays the JIRA_ISSUES table in IBM Db2 Database with the data adhering to the new issue created and ready to be used by the software development projects.
Figure 4 - Updated IBM Db2 Database table with issue details
This scenario demonstrates how you can use App Connect to automatically capture issue details from Jira and add it to the IBM Db2 Database to update relevant teams as soon as the information has been retrieved.
For more information about other supported connectors, see Connectors.
Resources
Try out our templates
You can view the following use cases in the Templates gallery in your App Connect Designer instance.
-
Store the issue data in IBM Db2 whenever a new issue gets created in Jira
Template URL: https://<your-instance-id>/templates/Store%20the%20issue%20data%20in%20IBM%20Db2%20whenever%20a%20new%20issue%20gets%20created%20in%20Jira.yaml
You must enable the Designer AI features in your containerized environment in order to access the App Connect templates. For more information, see The preloaded IBM App Connect templates.
You can also import these use cases directly into your App Connect Designer. These templates are added to a public GitHub repository at https://github.com/ot4i/app-connect-templates/tree/cp4i-templates/resources. For more information about the supported connectors, see App Connect Connectors.