Migrating Adapter Projects Created on TIBCO ActiveMatrix BusinessWorks™ 5.x to Plug-In Projects

You can migrate a Siebel Adapter and TIBCO ActiveMatrix BusinessWorks 5.x project created in TIBCO Designer™ to Plug-in for Siebel on ActiveMatrix BusinessWorks™ 6.x or TIBCO BusinessWorks™ Container Edition by using the migration tool in TIBCO Business Studio™ for BusinessWorks™.

Note:
  • In addition to the notes mentioned, it is a good practice to review the TIBCO ActiveMatrix BusinessWorks 6.x Migration guide for additional information such as naming conventions, and more.
  • Migration is based on the information received from the AE activities.

Projects Supported for Migration

Migration is provided for the following project specifications.

Project Specification Supported for Migration To
Projects created in ActiveMatrix® Adapter for Siebel
  • ActiveMatrix BusinessWorks 6.x
  • TIBCO BusinessWorks Container Edition
ActiveMatrix BusinessWorks 5.x projects created TIBCO Designer
Migration Restriction

You can migrate ActiveMatrix® Adapter for Siebel projects created on ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks Plug-in for Siebel. However, vice versa is not possible.

Considerations when migrating projects
  • Due to TIBCO ActiveMatrix BusinessWorks 5.x project structure and the migration process, there are some files in the TIBCO ActiveMatrix BusinessWorks 5.x project migrated to TIBCO ActiveMatrix BusinessWorks 6.x, but are not used and must be ignored. For example, - ae folder and ae2xsd.xsd under Schemas folder, AESchemas folder, etc.
  • A Process configuration error occurs when in the migrated ActiveMatrix BusinessWorks Plug-in for Siebel project a schema with the namespace is imported by the process but not found in module or dependent modules (not getting used). To resolve this issue, delete the Namespaces/Imports from Process > Dependencies.

  • If there is a TIBCO ActiveMatrix BusinessWorks™ 5.x generic activity that uses the Siebel adapter AE schema in TIBCO ActiveMatrix BusinessWorks™ 5.x project, after migration the TIBCO ActiveMatrix BusinessWorks 6.x generic activities must be fixed by running the Post-migration feature. If the schema issue still persists, it must be manually fixed.

  • For migration the command line data option must be used and the user workspace directory and TIBCO ActiveMatrix BusinessWorks™ 6.x target directory should be the same. For example, bwmigrator.exe -data <user workspace> -projectDir <BusinessWorks 6.x target directory> <BusinessWorks 5.x project location>.
    Note: The CLI migration is not supported for Invoke Request Response AE Activity migration, if the mapperEnabled is not set to false in JSON preference file.
  • Migration supports online schema migration, which means it retrieves the schema from the Siebel server during migration for the respective activity. Before migrating a project, ensure that the connection parameters provided are correct in the project or in JSON reference file, otherwise errors might occur post migration.
  • Module property is migrated to TIBCO ActiveMatrix BusinessWorks 6.x project only if it is created in TIBCO ActiveMatrix BusinessWorks 5.x project and is referred in one of the TIBCO ActiveMatrix BusinessWorks 5.x projects or it must be referred in JSON file.
  • An XSLT out of Sync error occurs in the migrated TIBCO ActiveMatrix BusinessWorks™ 6.x project. To resolve this issue, Right-click the input mapping and select Show Check and Repair.