Migrating Adapter Projects Created on TIBCO ActiveMatrix BusinessWorks™ 6.x to Plug-In Projects
You can migrate a Tuxedo Adapter project created on TIBCO ActiveMatrix BusinessWorks™ 6.x to TIBCO ActiveMatrix BusinessWorks™ Plug-in for Oracle Tuxedo project by using option in TIBCO Business Studio™ for BusinessWorks™.
For migrating a project successfully, the project should have at least one process using at least one of the adapter palette activities.
Projects Supported for Migration
-
You can migrate ActiveMatrix® Adapter for Tuxedo projects created on ActiveMatrix BusinessWorks 6.x to ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo. However, vice versa is not possible.
-
Migration supports only those ActiveMatrix® Adapter for Tuxedo projects created on ActiveMatrix BusinessWorks 6.x that have no designtime or runtime errors before refactoring. The projects must be validated and processes must be run successfully end to end before migrating to ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo projects.
- Before migration, the project should be imported into a new workspace and the studio should be restarted.
-
Migration is based on the information received from the AE activities. Invoke an Adapter Request-Response Service activity get migrated to the InvokeOracleTuxedoService activity of the Tuxedo plug-in.
- If all ActiveMatrix® Adapter for Tuxedo 6.x projects are not migrated to ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo projects, then export the adapter projects, import it to a new workspace or TIBCO_HOME, and then perform the migration of the project.
- Due to the structure of ActiveMatrix® Adapter for Tuxedo project created on ActiveMatrix BusinessWorks 6.x and the migration process, there are some files in the project migrated to ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo, but are not used and must be ignored. For example, - ae folder and ae2xsd.xsd under AESchemas folder, and so on.
- An EMF validation error occurs in the migrated ActiveMatrix BusinessWorks Plug-in for Tuxedo project when a ActiveMatrix® Adapter for Tuxedo project created on ActiveMatrix BusinessWorks 6.x is saved with another name and these two projects are migrated to the plug-in. To resolve this issue, delete the Namespaces or Imports from .
- If the tuxedo activity has For-Each or Copy-of, the user needs to do One-to-One mapping.
- Migration supports the schema migration, which means it creates the input and output schemas by using Oracle Tuxedo header files provided in the JSON configuration file or in the adapter service. The JSON configuration file has the highest preference.
