Migrating Adapter Projects Created on ActiveMatrix BusinessWorks 6.x to Plug-In Projects

You can migrate a project that is created by using TIBCO ActiveMatrix® Adapter for Database 7.2.0 and the ActiveMatrix BusinessWorks 6.x project to ActiveMatrix BusinessWorks Plug-in for Database on ActiveMatrix BusinessWorks 6.x by using Refactor > Adapter to Plug-in Migration option in TIBCO Business Studio.

Prerequisite
  • For databases using native drivers in ActiveMatrix BusinessWorks 6.x, the JAR files must be added to the <TIBCO_HOME> directory before the migration is initiated.

Projects Supported for Migration

Migration is supported for the following project specifications:

Project Specification Supported for Migration To
ActiveMatrix® Adapter for Database projects created on ActiveMatrix BusinessWorks 6.x in TIBCO Business Studio ActiveMatrix BusinessWorks 6.x
Migration Restrictions
  • You can migrate ActiveMatrix® Adapter for Database projects created on ActiveMatrix BusinessWorks 6.x to ActiveMatrix BusinessWorks Plug-in for Database. However, vice versa is not possible.
  • Migration supports only those ActiveMatrix® Adapter for Database projects created on ActiveMatrix BusinessWorks 6.x that have no designtime or runtime errors before refactoring in the same workspace. The projects must be validated and processes must be run successfully end to end in the same workspace before migrating to ActiveMatrix BusinessWorks Plug-in for Database projects.
  • Migration is based on the information received from the adapter palette activities.
Considerations When Migrating Projects
  • To avoid post migration issues, ensure that correct connection parameters are provided in the project or in the JSON reference file at the time of migration.
  • Global variables are migrated to ActiveMatrix BusinessWorks 6.x project only if they are created in ActiveMatrix® Adapter for Database projects created on ActiveMatrix BusinessWorks 6.x and are referred in one of the processes or are mentioned in the JSON reference file as a global variable.
  • Migration through refactoring requires online schema, which means it retrieves the schema from the Database server during migration for the respective activity.
  • After migration, you might notice some additional files (such as ae folder and ae2xsd.xsd file in the Schemas folder and the AESchemas folder) that you do not require. Ignore such files.
  • A validation error occurs in the migrated ActiveMatrix BusinessWorks 6.x project when one ActiveMatrix® Adapter for Database project created on ActiveMatrix BusinessWorks 6.x is saved with two different names and both the projects are migrated to the plug-in. To resolve this issue, delete the Namespaces/Imports from Process > Dependencies.
  • After migration to ActiveMatrix BusinessWorks Plug-in for Database on ActiveMatrix BusinessWorks 6.x, a project created by using ActiveMatrix® Adapter for Database that is installed on ActiveMatrix BusinessWorks 6.x might display some errors, such as xslt-out-of-sync with schema component properties or input schema with misplaced input data.

    To remove the errors and run the project, on the Input tab in the Properties section of the activity, right-click the input item that displays the error and select the Show Check and Repair option. In the Mapper Check and Repair window, select the items to be fixed and click OK.