IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > FTP > Plan for adapter implementation > Migrating to version 7.5.0.3 > Performing the migration

Migrating databases

With WebSphere Adapter for FTP, version 7.5, the schema of the event persistence table is modified. Hence, after completing the adapter migration, you must update the structure of the event table to work with the adapter version 7.5. Use the sample database scripts available at "<IID_HOME>\Resource Adapters\FTP_7.5.0.2\Scripts" to update the structure of the event table.

Before updating the structure of the event table, ensure that only the failed events are available in the event table. Ensure that you process or delete the unprocessed events before performing this task.

The database migration is required for both single and HA Active-Active instance of adapter configuration. After migrating the adapter, if you use an existing event table with the adapter version 7.5, then a runtime exception is thrown.

Perform the following steps to run the scripts and update the structure of the event table.


Procedure

  1. Go to the "<IID_HOME>/Resource Adapters/FTP_7.5.0.2/Scripts" folder.
  2. Double-click one of the following scripts corresponding to your database:

    • scripts_db2_upgrade.sql – for DB2 and Derby database
    • scripts_mssql_upgrade.sql – for Microsoft SQL Server database
    • scripts_oracle_upgrade.sql – for Oracle database

  3. The selected script performs the following actions:

    1. A temporary event table with the same structure of the existing event table is created.

      Ensure that the name of the temporary event table (mentioned in the script) is not already in use for any existing table. If the name is already in use, then change the name of the temporary event table in the database script accordingly.

    2. The event data from the existing event table is copied to the temporary event table.

    3. If the default name of the event table (FTPTABLE) is not used in your application or project, ensure that you specify the name of the existing event table in the database script.

    4. An event table with the new structure is created.

    5. After the data from the temporary table is copied to the new event table, the temporary table is deleted from the database.


Results

The updated event table can now be used in your project.

Performing the migration