|Skip Navigation Links|
|Exit Print View|
|Oracle Java CAPS Database Binding Component User's Guide Java CAPS Documentation|
This runtime component is available as a sun-database-binding component. The design-time components still leverage the org-netbeans-modules-wsdlextensions-jdbc.nbm. NetBeans Modules help create artifacts for the sun-database-binding. The artifacts that the new version of these components generate are deployed to the Database BC instead of the JDBC Binding Component or SQL Service Engine.
Database BC (DB BC) is a Java Business Integration (JBI) runtime component that provides a comprehensive solution for configuring and connecting to databases. Database BC provides data operations as Services. It supports the JDBC from within a JBI environment. Other JBI components invoke these Web Services acting as consumers. Database BC considers both Data Manipulation Language (DML) and Data Definition Language (DDL) operations as Web Services.
The services that the Database BC exposes are actually SQL operations on Table, Prepared Statements, and Procedures. The Database BC supports the following database artifacts to be exposed as Services.
The Database BC can assume the role of either a JBI consumer (polling inbound requests) or a JBI provider (sending outbound messages).
Once installed, the Database BC can be used to design, deploy, and run the Service Units. The most important part of a Service Unit is the WSDL that describes the Database services. Database BC provides a set of extension elements specific to Database BC for connecting to the Database.
Database BC acts as a provider in case of outbound message flow. Database BC acts as an external service provider when other engines and components 'invoke' it. In this role, when it receives a normalized message as part of the message exchange, it converts and extracts the SQL operation. The SQL operation is then executed on the specified database. In other words, when the Database BC acts as a JBI provider, it extracts the SQL query from a JBI message received from the JBI framework. It then executes the query on a specified database. It converts the reply from the database into a JBI message that other JBI components can service.
Database BC also acts as a consumer incase of inbound functionality where Database BC polls for records from a particular table, converts them into normalized message, and sends to the Normalized Message Router (NMR). This process is analogous to the inbound connections implemented in CAPS 6. In other words, When the Database BC acts as a JBI consumer, it polls a specified database for updates to a table in the database. When a new record is stored in the table, the database polls for the record for the specified time interval and the Database BC picks up that record, constructs a JBI message, and sends the message to the JBI framework so it can be serviced by other JBI components.
The Database BC WSDL extensibility element is a template used to construct an instance of a Database BC WSDL. The Database BC WSDL extensibility elements contains information for constructing the Database BC message. These messages are constructed using the message parts, message formats, properties mapping, and other message related information necessary for the Database BC to properly map message exchanges to Database BC messages and vice versa. The Database BC WSDL extensibility elements also contain information about the database to which it connects.