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

You can migrate a Tuxedo Adapter and TIBCO ActiveMatrix BusinessWorks 5.x project created in TIBCO Designer™ to Plug-in for Oracle Tuxedo 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. Only Invoke an Adapter Request-Response Service activity is supported. All the Invoke an Adapter Request-Response Service activities are migrated.

Projects Supported for Migration

Migration is provided for the following project specifications:
Project Specification Supported for Migration To
Projects created in TIBCO ActiveMatrix® Adapter for Tuxedo
  • TIBCO ActiveMatrix BusinessWorks 6.x
  • TIBCO BusinessWorks Container Edition

TIBCO ActiveMatrix BusinessWorks 5.x projects created in TIBCO Designer

Migration Restriction
  • You can migrate TIBCO ActiveMatrix Adapter for Tuxedo projects created on ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo. However, vice versa is not possible.
  • The TuxSchemaResource needs to be created manually, if required.

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.
  • If there is a TIBCO ActiveMatrix BusinessWorks 5.x generic activity that uses outputs from preceding activities in TIBCO ActiveMatrix BusinessWorks 5.x projects, then use One-to-One mapping only while mapping from preceding activities to Invoke an Adapter Request-Response Service activity.
    Note: If the tuxedo activity has For-Each or Copy-of, the user needs to do One-to-One mapping.
  • An EMF validation error occurs in the migrated TIBCO ActiveMatrix BusinessWorks™ 6.x project when one TIBCO ActiveMatrix BusinessWorks™ 5.x project is saved with another name and these two projects are migrated to the plug-in. 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 Tuxedo adapter AE schema in the TIBCO ActiveMatrix BusinessWorks™ 5.x project, after migration the TIBCO ActiveMatrix BusinessWorks 6.x generic activities must be fixed by running post-migration feature.
  • After migration, in TIBCO ActiveMatrix BusinessWorks™ 6.x project the shared resource created is always present at the root level even if it is at a resource folder level in TIBCO ActiveMatrix BusinessWorks™ 5.x project
  • For migration the command line data option should 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>.
  • Migration supports the schema migration, which means it creates the input and output schemas by using Oracle Tuxedo header files provided in JSON configuration files or in adapter service. The JSON configuration file has the highest preference.
  • 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 and it must be referred in JSON file.