IBM DB2
Connect IBM DB2 tables, views and stored procedures to Engini workflows for record operations and reviewed SQL execution.
Book a demoIBM DB2 integration with Engini
Use Engini’s IBM DB2 connector to retrieve operational records, maintain table data and invoke existing database procedures. The guide documents direct-access and DSN connection methods, plus Cloud and On-Premises Agent communication choices. Match the setup to your database environment and start with a small, read-only operation before expanding the workflow.
Connect and prepare your workflow
You need IBM DB2 database access with a username and password permitted to perform the intended operations. For direct access, prepare the server address, port and database name; for DSN access, prepare the configured data source name. Review the database time zone and, for direct Cloud communication, its CCSID.
- In Engini Connections, choose New Integration and IBM DB2. Name the connection and select Direct Access or DSN, then enter the required connection details and credentials.
- Choose Cloud or OPA to match the deployment. When using OPA, select the intended On-Premises Agent. Check the time zone so date and time values are interpreted appropriately.
- Save the connection and use Select database objects to choose the entities and actions needed for the process. Confirm the returned fields with a limited Get Records query.
Documented connector actions
Read and maintain records
Get Records reads a table or view with Top N, Offset, filters and sorting. Writes use the selected table and mapped field values; deletion uses filters to identify its targets.
- Create Record
- Get Records
- Update Record
- Delete Records
Process lists of records
These activities iterate over a selected data list and perform the configured operation for its items. Validate the list’s field mappings and target table before processing.
- Create Batch of Records
- Get Records Batch
- Update Batch of Records
Run database logic
Run a reviewed SQL query or command, or select an existing stored procedure and provide its fields. The database user’s permissions remain important for both operations.
- Execute Customized SQL
- Execute Procedure
Workflow triggers
The IBM DB2 connector guide does not document a dedicated database-change trigger. These are workflow actions, so configure a separate start condition rather than assuming inserts or updates will automatically launch an Engini workflow.
Two workflows to build
Prepare an exception list from operational data
Use Get Records against an appropriate table or view, with filters, sorting and a deliberate result limit. Pass the returned identifiers and fields to a separately configured review step. Check pagination before treating the result as a complete exception list.
Apply reviewed updates from a data list
Validate an incoming list, then use Update Batch of Records with a precise filter and explicit field mappings. Retrieve the relevant records afterward to verify the changes. Configure a review step before writes if the update affects important operational data.
Choose agent tools deliberately
Discover the tools available through your current Engini connection and inspect their input and output schemas. Documented workflow actions are not automatically exposed as agent tools. Bind the intended connection to an explicit tool allow-list, then test representative inputs and results before rollout. These workflow ideas are proposed starting points; configure the surrounding steps, permissions and review process for your organization.
Frequently asked questions
Which IBM DB2 editions are covered?
The guide names IBM DB2 but does not provide an edition or version compatibility matrix. Confirm your particular database environment and connection method before committing to a rollout.
How many rows does Get Records return by default?
The documented Top N default is 100 and Offset defaults to zero. Set a deliberate limit and pagination strategy when your workflow needs more than the initial result set.
Does object selection restrict customized SQL?
Object selection configures the entities and actions offered in the connection. Do not use it as a substitute for database permissions that constrain SQL or procedure execution. Keep the allowed operations narrow and review custom statements.
Start with your connection
Create an Engini account and follow the official IBM DB2 connector guide to configure your first workflow.
Sources reviewed November 4, 2026: connector documentation, toolset configuration and tool schemas.