Migration

This topic lists the Known Issues related to Migration.

Key Description
BWCE-3763 Summary: After migration, an element of simple type is not supported.

Workaround: In the existing schema create an element reference for all WSDL messages which are referring type references.

First create an element reference in inline or externalized schema and then update WSDL message to refer the element (newly created one for complex or simple type definition) and remove the reference of type definition.

AMBW-40387 Summary: After migration, a path is not executed that leads to the difference in output.

Workaround: In TIBCO BusinessWorks Container Edition 5.x the transition condition $Map-Data/ConditionType[last()] is treated as boolean but not in TIBCO BusinessWorks Container Edition 6.x as TIBCO BusinessWorks Container Edition 6.x has strict validations.

In order to resolve this, please update the condition as follows:

count($Map-Data/ConditionType[last()])>0

AMBW-40187 Summary: Migration of custom icon for the Call Process activity is not supported

Workaround: After migration, manually browse the custom icon field value for the Call Process activity.

AMBW-39231 Summary: While migrating a project using XPATH language for transitions option, which is set to XPATH 1.0 by default, on the Migration Wizard, the Process inline namespace schema collision issue occurs intermittently after migration is complete.

Workaround: Navigate to the faulted process and add the missing schema location field next to the namespace.

AMBW-39230 Summary: While migrating a project using the XPATH language for transitions option, which is set to XPATH 1.0 by default, the service agent process migrates as an empty process thereby throwing the Argument Cannot Be Null exception upon trying to view that process post Migration.

Workaround: Migrate that project in a different workspace, because the issue is intermittent.

AMBW-36094 Summary: Post migration, a schema cannot refer the .WSDL file in it and if you try to run the project, the Schema not found error is displayed at the run time.

Workaround: Copy the inline schema that gets created post migration of the project and paste it into the .WSDL file.

Remove the inline schema dependency from the dependencies section and in the input editor of the inline schema activity, re-map the point to the inline element. After this remove the inline schema that is empty and execute the project.

AMBW-36077 Summary: After migration, if the migrated project contains any SOAP service or client binding that uses SOAP RPC Encoded arrays, the following WSDL validation error occurs:

WSDL In-line schema SOAP encoded array type error. In-line schema in WSDL file contains SOAP encoded array type which requires a fix pattern.

Workaround: Download the SOAP Encoding schema from 'http://schemas.xmlsoap.org/soap/encoding/', and put it into the TIBCO BusinessWorks Container Edition project.

AMBW-35926 Summary: The migration tool does not support external schema for multi-part message in the bindings.

Workaround: Create wrapper schemas for all multi-part messages of WSDL.

AMBW-35899 Summary: Currently, only copy-of mapping is supported for context mapping of headers.

Workaround: You can either create One-to-one mapping manually or use a copy-of option for context mappings.

AMBW-33749 Summary: After migration, additional round brackets in the names of the folder for externalized schema creates issues at run time.

Workaround: Remove the special characters after migration in the folder names.

AMBW-30656 Summary: A schema cannot contain two global components with the same name.

Workaround: Modify one of the schema namespaces or element names, so that the names are unique.

AMBW-30476 Summary: After migration, the input mapping for the End activity that refers to a multi-part WSDL message displays validation errors.

Workaround: A WSDL message is not supported by a mapper. Create a new .xsd schema element with the structure similar to associated WSDL message, and then map the schema element in place of WSDL message.

AMBW-26746 Summary: The TransformXML activity from TIBCO BusinessWorks Container Edition 5.x did not migrate correctly if the Input/Output style of the activity was set to TREE in the TIBCO BusinessWorks Container Edition 5.x project.

Workaround: None

AMBW-14547 Summary: When you migrate an TIBCO ActiveMatrix BusinessWorks 5.x project containing in-built functions in the JDBC Query activity, an Invalid Column name error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the TIBCO BusinessWorks Container Edition 5.x project.

AMBW-14295 Summary: After migration, the output of project with Rest and JSON activities does not match with the input of the other activities in the migrated project.

Workaround: None

AMBW-13683 Summary: Shared resource module property references in the migrated TIBCO ActiveMatrix BusinessWorks 5.x projects do not show up correctly on non-Windows platforms.

Workaround: Close and reopen the project.

AMBW-9969 Summary: ActiveMatrix BusinessWorks 5.x projects with SOAP headers configuration in SOAP activities are not properly migrated to TIBCO BusinessWorks Container Edition .

Workaround: SOAP functionality in TIBCO BusinessWorks Container Edition is achieved through SOAP Binding where its detail configuration is outside of TIBCO BusinessWorks Container Edition Process. The SOAP headers definition are defined at the Binding configuration and configured as generic context parameters for the Process. In the Process, you can use the Get Context activity (from Basic Palette) to retrieve and process the headers as context data. You can do this manually to complete the migrated project.