WebSphere Adapter for JDBC

Performing the migration

Migration to Adapter for JDBC version 6.0.2 requires that you edit the Inbound Service description by updating some of the Activation specification properties. You also need to set properties if you want to do event filtering. You must change the event table to add the transaction id (xid) column.

Before you begin

Replace the previous version of the resource adapter archive (RAR) file with the latest adapter RAR file.

How to perform this task

  1. Edit the Inbound Service description by updating properties

    After you have imported the project interchange (PI) file generated using version 6.0.0.x of the Adapter for JDBC, use the assembly editor to edit the Inbound service description by updating only the Activation specification properties listed in the following table.

    Table 1. Activation specification properties to update during migration
    Property Type Description Default value Globalized
    AssuredOnceDelivery Boolean If this property is set to true, an xid value is set for each event in the event store. Each event is then delivered to its corresponding endpoint and subsequently deleted from the event table. true No
    CustomDeleteQuery String The custom delete query that is run after each event is processed. This is enabled for use with bidirectional languages. None Yes
    CustomEventQuery String The SQL query, stored procedure, or stored function for custom event processing. This query is run during each poll cycle when the EventQueryType is set to Dynamic. This is enabled for use with bidirectional languages. None Yes
    CustomUpdateQuery String The custom update query that is run after each event is processed so that the same event does not get picked up for processing in the subsequent event cycle. This is enabled for use with bidirectional languages. None Yes
    DataSource
    JNDIName
    String Name used by the adapter to establish the connection to the database. If UserName and Password are also set, they are also used when establishing the connection. If not, just the DataSourceJNDIName property is used. None Yes
    EventFilterType String The adapter can filter the events to be processed by business object type. EventFilterType has a comma delimited list of business object types, and only the types specified in the property are picked up for processing. If no value is specified for the property, no filter is applied, and all the events are picked up for processing. null Yes
    EventQueryType String Determines whether to use the standard event store or custom query. The valid values are Standard, for standard event store, and Dynamic, for custom event processing. None No
    FilterFutureEvents Boolean If this property is set to true, the adapter filters events based on timestamp. The adapter compares the system time in each poll cycle to the timestamp on each event. If an event is set to occur in the future, it is not picked up for processing until that time. false No
    SPAfterPoll String Any stored procedure that you want to be run after each poll cycle. It takes one input parameter for PollQuantity. This is enabled for use with bidirectional languages. None Yes
    SPBeforePoll String Any stored procedure that you want to be run before the actual poll query is called. It takes one input parameter for PollQuantity. This is enabled for use with bidirectional languages. None Yes
  2. Optional: Set properties if you want to filter events

    You can use two Activation specification properties to enable event filtering: FilterFutureEvents (for event filtering by timestamp) and EventFilterType (for event filtering by business object type).

    FilterFutureEvents is set to false by default. Change the setting if you want to filter events by timestamp.

    To filter by business object type, set a comma-delimited list of business object types in the EventFilterType property, otherwise, leave it blank.

  3. Add the xid column to the event table
    Note: Before you alter the event table, ensure that no events are in the Event Distribution Table (EDT). The Adapter for JDBC, version 6.0.2 does not use the EDT, but uses a different mechanism to provide assured once delivery of events. Also ensure no events are being added to the event table while the migration is in progress.

    Use the following sample SQL statement to alter the event table:

    ALTER TABLE <tablename> ADD COLUMN xid VARCHAR(255);


Terms of use |

Last updated: Tue 12 Dec 2006 03:32:39

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)