Use a Database Service to make database operations accessible both within a message flow, and to external applications that call a message flow.
A Database Service defines the interaction between IBM® Integration Bus and a database, and can be used with a message flow node to automatically configure connectivity to that database. A single Database Service can be reused across multiple nodes, simplifying database connectivity within your message flows. You can create as many Database Services as required.
Create a Database Service in the Database Service editor by combining metadata discovered from the database, with information supplied by the flow developer about the required database interaction (for example, which table must be updated and under what circumstances). The Database Service editor uses a database definition file (.dbm file) that contains information about a connection to a database, and typically also includes information about the database contents (for example, the database schemas, tables, and stored procedures). If you do not have a database definition file, it can be created in the Database Service editor.
- Operation-oriented interface definitions about the database interaction (for example, an operation can reflect the changes to make to a particular table). This information is contained in a WSDL file.
- A database connection binding that captures the semantics of the operations on the database. This information is contained in a WSDL file.
- XSD files that describe the inputs and outputs of the database operations.
- A .service file that captures metadata that is used during the discovery process. The IBM Integration Toolkit uses this file to store state information from the Database Service editor, and perform iterative discovery of previously discovered artifacts.