TIBCO ActiveMatrix BusinessWorks Plug-in for Database supports migrating projects from version 7.2.0 to 8.x in TIBCO ActiveMatrix BusinessWorks 6.x environment.

Users need to install the "TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database Adapter to Plugin Migration" feature while installing the plugin.

There are some requirements before installing the above feature as below:
1 If using TIBCO ActiveMatrix BusinessWorks Plug-in for Database 8.4.0, the below products are required:
   TIBCO Adapter Migration 1.7.0 - 1.7.x
   TIBCO ActiveMatrix Adapter Framework 1.6.0 - 1.6.x
2 If using TIBCO ActiveMatrix BusinessWorks Plug-in for Database 8.3.2, the below product is required:
   TIBCO ActiveMatrix Adapter Framework 1.4.0 - 1.4.x

If any of the above is missing, the migration will fail. The symptom is the ADB Configuration shared resource is not generated after the migration.

If the ADB Configuration shared resource is generated, but the tables in the schema page are missing, it could be because of the below reasons:

1 The "SID" is used in the JDBC URL of the adapter project, and the "ServiceName" and "SID" are not the same on the DB side.
The 7.2 adapter project supports both "SID" and "ServiceName" in the JDBC URL, while "SID" is not supported in the JDBC connection in TIBCO ActiveMatrix BusinessWorks 6.x. If the JDBC URL uses "SID" in the 7.2 adapter project, it will be changed to "ServiceName" after the migration. This will work when the "SID" and "ServiceName" have the same value on the DB side. But if the "SID" and "ServiceName" have different values on the DB side. The connection will fail after changing to "ServiceName". Then the migration will fail too.

To avoid this issue, users need to replace the "SID" with "ServiceName" in the 7.2 adapter project before the migration and do "test connection" to make sure the connection is successful.

2 The connection to the DB doesn't work.
During the migration, the plugin retrieves the schema from the database server for the respective activity. Hence, if the connection doesn't work, the migration will fail.

To avoid this issue, users need to make sure the connection to the database server is working during the migration.