Comparison between Adapter and Plug-In
For users who have previously used the ActiveMatrix® Adapter for Database, this topic explains the differences in the plug-in where supported features have overlap with adapter.
| Feature | ActiveMatrix® Adapter for Database | ActiveMatrix BusinessWorks™ Plug-in for Database |
|---|---|---|
| Services Provided | Publication service, Subscription service and RPC service, and Alerter Service | The plug-in is a replacement of the ADB Adapter and AE Palette available in
ActiveMatrix BusinessWorks.
Data Event Poller activity is equivalent to the adapter's Publication service with an Adapter Subscriber activity. Data Merger activity is equivalent to the adapter's Subscription service with a TIBCO BusinessWorks™ Adapter Publication activity. The Data Requester activity is equivalent to the adapter's Request-Reply service. It allows an application to submit one or more SQL statements, stored procedures, and functions to be processed. |
| Transport Type | JMS and Rendezvous | The plug-in is native to ActiveMatrix BusinessWorks and does not require messaging. |
| Message Format | The ADB Adapter is developed by using Adapter SDK libraries and outputs the message by using AE Schema. | The plug-in is native to ActiveMatrix BusinessWorks and outputs the message as XML based on a XSD. |
| Support for Load Balancing | Configurable | Supported by default but can be configured by the user. |
| TRA Properties | TRA properties are maintained in TIBCO Administrator | TRA properties are not applicable in plug-in. |
| UseBetweenClause | Default is false | Default is true |
| Referencing an external schema | Yes | Yes |
| Storage Mode | Publish by value/reference | Publish by value/reference |
| Stage Table | Yes | Yes |
| Triggers Generation | Direct apply/SQL statement generated
or save generated SQL into file |
Direct apply/SQL statement generated
or save generated SQL into file |
| DB reconnection attempts | DB JDBC connection recovery/reconnect attempts | Reconnection is tried at every polling interval or by every activity invocation. |
| Polling Batch size | Supported | Supported |
| Group messaging | Supported | Renamed as "record per event" |
| MS SQL Windows Authentication | Yes | Yes |
| Auto Re-Publish (Oracle_failed_rePublish) | Yes | Yes |
| Look back | Yes | No |
| Publishing by Reference Object | Yes | Yes |
| Polling performance enhancement hint | Yes | Yes |
| Database vendors | ||
| Database Driver support | ||
| Set Database client information | Yes | Yes |
| Publish Batch confirm size/timeout | Yes | No |
| Database Connection | JDBC-based adapter connection | JDBC connection |
| Database Configuration | Adapter Configuration | ADB Configuration Shared resource |
| Refresh the existing schema | Refind Schema option | The Refind Schema option is renamed as Refresh Schema. |
| Multithreading (multiple processing stream) | Message session based | Multithreading is provided through ActiveMatrix BusinessWorks engine job thread, each job thread has a Data Merger activity instance. |
| Separate sessions | Message session based | Not applicable |
| UseSerial (Messages processed in order) | Yes | Yes with a single ActiveMatrix BusinessWorks engine and ActiveMatrix BusinessWorks process thread count = 1 |
| Use Exception table (Error inserted in the exception table) | Yes | This is optional for the plugin, as you might choose to correct the data and reprocess it. The status of the output always shows the status of each record if it is not a one way process. |
| Use Child Exception table (Error related to child table data inserted in the child exception table) | Yes | Yes |
| User Opaque Exception table (when no exception table or insertion in the exception table fails) | Yes | Yes |
| Subscriber Precommit Stored Procedure call | The subscriber can be configured to call a stored procedure after a database insert, update, or delete operation and before committing a transaction. | Yes |
| Batch processing | The adapter provides processing of subscription requests in batches at two operation levels: | The plugin supports batch processing if number of data rows in the activity input is more than 1, but does not support this globally, that is, no accumulation of the messages processed by different
ActiveMatrix BusinessWorks process jobs or
ActiveMatrix BusinessWorks process nodes are packed as batches.
For each process, one database operation each, as a single record or batch operation, can be configured. |
| Bulk Insert Error Handling feature:
Batch commit (size, timeout) (The number of messages to be put in a batch before invoking a commit operation. The default value is 0.) |
Error Handling by subscription service
When Subscription Service inserts data into a database and an error occurs, the subscriber endpoint rolls back all previous operations on the database to the original status. Subscription Service handles error data in two ways: normal error handling and bulk insert error handling. The Batch Commit Size field is displayed only when the Use Separate Session check box is selected on the Configuration tab. |
No explicit setting is required. Plugin commits all the successful operations, and un-successful processed records are sent to be handled by the exception logic. For example, operation results returned as result of the activities and/or insertion in the exception tables.
For more information about Bulk insert error handling, see Bulk Insert Error Handling |
| One way upsert operation request | Yes | No, as there is no messaging middleware involved. |
| JMS Durable Subscriber Name | The JMS Subscriber Name can take the deployment time global variable value. | Not applicable. |
| Runtime Schema | In the case where the schema name of the table objects is different in the development and the production environments. | Yes |
| Bulk Insert Size | Design-time setting | Is part of the palette's configuration and related ActiveMatrix BusinessWorks process. |
| Request Reply | A request can contain one or more SQL statements, stored procedures, functions, or packages to be executed as a transaction. The text of the SQL statement follows the conventions for JDBC SQL syntax. All SQL statements supported by the DBMS are allowed and placeholders, represented by a question mark (?), are permitted in the SQL statement. The SQL statements conform to the JDBC rules. For performance reasons, it is good practice to use a SQL statement. The ‘?’ convention must only be used to bind binary data or call stored procedures.
A response from the adapter to a client application has a result code and one or more result sets. Each result set contains nested self-describing messages. Each of these messages encodes a result row that returned after executing a query. A response can also return an error code and error description if the request is not successful. |
Yes |
| Remote Procedure Call (RPC) | The adapter can be configured to act as a remote procedure call (RPC) server on behalf of a client. | Yes |
| RPC Standard Operation (SQL_EXECUTE) | SQL_EXECUTE takes a single SQL statement and processes it. | Yes |
| RPC Standard Operation (SQL_BATCHEXECUTE) | SQL_BATCHEXECUTE takes a sequence of SQL statements and processes them. | Yes |
| RPC one way messaging | Yes | No |
| Maximum rows | Specifies the maximum number of rows to be fetched at the service level. This can be used to limit the memory usage of the adapter. The unfetched rows are ignored by the adapter. | Yes |
| Statement Cache | The number of cache statements for a generic RPC request/reply service.
The number of statements cached by the adapter is executed directly for repeated requests. If the cache is full, the adapter removes the oldest message from the cache and adds the new statement. The default value is 1. |
The size of the cache depends on the number of statements provided as input. |
| Timeout exception for Invoke Adapter Service activity | Supported in ActiveEnterprise Adapter palette in ActiveMatrix BusinessWorks 5.x . | Supported by Data Merger and Data Requester activities in ActiveMatrix BusinessWorks 6.x. |