Migration

This topic lists the closed issues related to Migration.

Release 2.10.0

Key Description
BWCE-7106 Post migration, an inconsistent behavior of migration utility with TIBCO BusinessWorks Container Edition 2.9.0 on Windows is observed where the process is not migrated correctly.
BWCE-6090 Post migration, the link between shared module and the application module is broken leading to incorrect/missing mappings inside a few of the activities.
AMBW-51328 Post migration, unable to display output schema for JDBC Query activity.
AMBW-50219 Post migration from ActiveMatrix BusinessWorks 5.x to ActiveMatrix BusinessWorks 6.x, to avoid conflict of having similar namespace names while updating the namespaces, perform the following steps:
  1. In the Project Explorer pane, right-click the schema for which the namespace is to be updated, and select Refactor > Rename XSD Schema namespace.

  2. Click OK.

    This triggers the namespace change in all the connected process dependencies and even the mappings get updated without error.

Release 2.9.2

Key Description
BWCE-7551 A process migrated as an empty process, post migration leads to inconsistent behavior.
BWCE-7348 The TIBCO ActiveMatrix BusinessWorks 5.x projects are unable to migrate to the TIBCO BusinessWorks Container Edition 2.9.2 build.
AMBW-50806

The TO_CHAR() function fails after migrating from ActiveMatrix BusinessWorks version 6.6.0 to 6.10.0.

A Boolean value of "true" must be provided for the following flag:

-Dbw.application.activity.jdbc.keep.colname.compatibility

AMBW-33688 Post migration, unable to display output schema for JDBC Query activity.

Release 2.9.0

Key Description
AMBW-49083 The Migration utility fails with an error while migrating a project containing DTD.
AMBW-48400 The HTTP Client Name field is blank in the SOAP Binding post migration.
AMBW-48367 The SOAP endpoint URI field displays the value from the concrete WSDL instead of the value in the global variable.
AMBW-33063 The schema location value is missing in the WSDL Inline Schema post migration from the import statement.

Release 2.8.3

Key Description
AMBW-48154 Mapping on a transition is broken, which leads to validation error post migration.

Release 2.8.2

Key Description
AMBW-48159 The RV publisher activity does not honor special keyword characters like "_plus_" and "_sp_" in the element name post Migration.
AMBW-47732

GV mapped to the JDBC activity timeout and Maximum rows are not showing up in ActiveMatrix BusinessWorks 5.x to 6.x migrated code.

The "Timeout (secs)" and "Maximum rows" fields in the JDBC Call Procedure activity do not display the mapped module property value post migration but display the default literal values.

AMBW-32780 The REST Dispatch and Reply activity in TIBCO BusinessWorks Container Edition 5.x is migrated to the Invoke Rest API activity instead of the REST Service Binding.

Release 2.7.2

Key Description
BWCE-4343 When TIBCO ActiveMatrix BusinessWorks™ 5.x projects are migrated using the Migrate as shared moduleoption in the migration wizard, the module properties are migrated incorrectly.
AMBW-44538 After migration, the element inside the Catch all > error_variables are not resolved correctly when a process with more than one fault element is configured in the End activity.

Release 2.7.0

Key Description
BWCE-3873 After migration, the "or " operator migrated as a "|" character throws a warning in design time and an error at runtime.
AMBW-43791 Post-migration, the mapper input is empty when the schema is referenced from data format shared resource.
AMBW-43501

The migration tool migrates processes with the REST-Dispatch-and-Reply activity to a REST resource. In TIBCO ActiveMatrix BusinessWorks™ 5.x, the service processing logic is delegated to a subprocess as per operation. Normally the subprocess is migrated. To supplement this, a call process is created to invoke that subprocess in the REST resource.

You may need to fix the mapping for the newly created call process manually. This could fix the mapping itself, or the input and output schemas for the called subprocess.

Note: The REST Service descriptor supports both internal and external WADL references. However, we do not support multiple resources pointing to the same resource path and having the same HTTP method.
AMBW-42280 After migration, the Mapper activity was migrated as an empty activity.
AMBW-41353 Post-migration, if the variable list XPath expression of an Iterate group is linked to multiple schemas then the iterator schema does not get resolved.
AMBW-33641 Getting "Coercion error: Can't find substitution for ""." at design time after migrating a project.