When to Use the webMethods Adapter for JDBC
You will want to use the Adapter for JDBC in most cases, including the following:
![*](chapterTOC_bullet.png)
Your system is likely to be expanded and modernized. This is typical for enterprise, mission-critical applications.
![*](chapterTOC_bullet.png)
You require better database performance. The performance of the
Adapter for JDBC is superior to that of the WmDB package, particularly for batch operations. For example, to insert data into a database using the WmDB package, you use the
pub.db:insert service; you supply the items to insert using a document list as input, and the
pub.db:insert service processes each item in the document list sequentially without using JDBC standard facilities.
![*](chapterTOC_bullet.png)
You require or plan to use notification features.
![*](chapterTOC_bullet.png)
You need automatic and efficient database connection pool management.
![*](chapterTOC_bullet.png)
You require XA transactionality.
![*](chapterTOC_bullet.png)
You need to use JDBC standard data types, including BLOB and CLOB.
![*](chapterTOC_bullet.png)
You need to be able to configure services rather than hard code them.
![*](chapterTOC_bullet.png)
You need to use role-based security. The
Adapter for JDBC allows the separation of the database administrator and development environments as needed. The WmDB package requires Administrator privileges.
![*](chapterTOC_bullet.png)
You want a configurable and structured user interface.
Adapter for JDBC uses template-based configuration that is more structured and easier to use. The
Adapter for JDBC uses metadata that helps protect the user's investment even if technology changes.
![*](chapterTOC_bullet.png)
You want to manage your database connection using
webMethods Optimize for Infrastructure.