Differences between TIBCO ADB Adapter and JDBC Pallet?
Lets go through a comparison between ADB Adapter & JDBC palette, which will give you a fair idea on when and where you need to use this.
| FEATURE | ADB Adapter |
JDBC Palette |
| Ease of Integration | Design time and run time environments, which are to be managed separately. | JDBC palette for both run-time and design-time operates in the same way. |
| Completeness | Very scalable component to handle both inbound and outbound messages. | BW JDBC does not have a mechanism to detect database changes in a push environment. |
| Consistent error viewing and handling | Adapter are written using SDK and strictly adhere to standard error viewing and handling. Thereby making monitoring easy. | JDBC provides error objects and rules have to be written for error viewing and handling. |
| Transactions Volume | Adapters are useful in high-to-medium load situations for both real-time and batch-updates. Adapter can be run on the application machine using native lib. | BW palette are useful in medium-to-low level load real-time situation |
| Connectivity Design Time | JDBC | JDBC |
| Connectivity Run-Time | ODBC | JDBC |
| Transaction Support | When asynchronous operations are acceptable. | Useful when dealing with synchronous model and you need to take explicit action on transaction failure |
| SQL Statements | Useful when you are using straight forward and simple SQL statements | Useful when the database operations are not straight forward i.e. the operations depend on a lot of “if..then..else” data dependent clauses. |
| Ease of Data Transformation, parsing and mapping | Data is transformed to desired protocol format (JMS etc) at the source. Parsing and mapping takes place in process flow. | Data transformation, Parsing and mapping takes place in process flow. |
| Result-set format | ADB result-set | JDBC result-set, useful if integrating with any 3rd party database custom application. |
| Exception Handling | If a subscriber adapter cannot write data to its destination table, it will write the data to the exception table | You have to implement exception handling in the process. |
| Database Support | Oracle, MS-SQL, Sybase, DB2 | Embedded drivers are: •tibcosoftwareinc.jdbc.oracle.OracleDrive •tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver •tibcosoftwareinc.jdbc.sybase.SybaseDriver There are additional supported drivers, please see release doc for details |
| Ease of Monitoring | Adapter enabled with Hawk framework (admin) deployed as a service has much fine grain monitoring, configuration & management than JDBC activity. | Palette monitoring can be handled as embedded component in the process. |
| Component Management | Adapter is deployed as separate component from the process and requires management. | Palette is embedded in the process along with data parsing, mapping etc. and does not require separate deployment |
| Protocol support | TIBCO EMS | TIBCO EMS |
| Loop Detection | Adapter has embedded provision to switch Loop detection on when trying to sync data between source and target applications. | Depending upon implementation may or may not require Loop Detection implementation. |