Frequently Asked Questions

What to do... Resolution
When migrated process shows mapping errors?
  1. Go to Menu > Project > Clean and click Clean All Projects.
  2. Go to the Activity Input with the Mapping Error. Click Show Check and Repair and fix existing errors. Click Fix Type Casting Errors.
  3. If the error still persists, check the expression and do the necessary corrections.
When processes have unresolved WSDL references?
  1. Close and reopen the project.
  2. If this does not fix the references, then check the WSDL Interface value on the General tab of the Process Service.
When Java Invoke activities show Input Configuration Error after migration?
  1. Go to the General tab of the Java Invoke activity and check whether the Class Name is available in the workspace. If available, re-select the Java class.
  2. If the class is not available, check whether the JAR file packaging the Java class is available. Otherwise, copy the JAR file to the "lib" folder and reselect the Java class.
When activities in the Catch block show Mapping errors? The Catch Block activities does not have the visibility to the output of the activities from the main process.

Re-map the activity input accordingly. This is similar to the Java try or catch constructs.

When Variable not defined error for Iterate Group Index variable is used outside the Iterate scope?
  1. In TIBCO BusinessWorks™ Container Edition the Iterate Group Index Variable does not have the visibility outside the Iterate scope.
  2. Define a Process Variable of Type integer and map it to the Iterate Group Index variable. You can now you can use this variable in the Process scope.
When a TIBCO BusinessWorks Container Edition activity migrates as Empty or Rescue activity ?
  1. The TIBCO ActiveMatrix BusinessWorks 5.x activity migrates as Rescue activity, if the migration framework fails to migrate.
  2. Check the TIBCO ActiveMatrix BusinessWorks 5.x project and add the corresponding activity in the TIBCO BusinessWorks Container Edition project and redo the mappings.
After migrating a project using the tib:concat-sequence-format() the output returns errors. The function tib:concat-sequence-format() does not accept string as return value for node set. Post-migration, replace tib:concat-sequence-format() with string-join() function.

When a group is around the activities and the XPath condition over the group is not satisfied after migration, the error, Expected Non Repeating got repeating is displayed.

  1. Verify the XPath condition and resolve issues of the group (for example, iterator, for-each...)

  2. Re-map the same from the group.

When the Variable not defined error is displayed post migration for multiple variables created in the input of any activity and each variable is created with the condition on another variable.

  1. Remove all the variables and recreate the variables and add the mappings again. In this case the back-end references are also removed.
  2. Delete the XPath on the variables one by one and re-correct them. This also resolves the issue sometimes.
When the error Unresolved reference schema is displayed. Reconfigure the broken module variables. Redo all the mappings as they break due to reconfiguration.
When the Catch-All End error is not configured. When a Catch All fault handler is used in a TIBCO BusinessWorks Container Edition project, on migration the fault handler is converted as expected but an End activity is created in place of a Catch All activity. An End activity without any input is created. Delete the end activity and to resolve the issue.

Schema references issues post migration

References of schemas that are imported in another schema are not found. Delete the import and add it again. The references are updated with the correct namespace and the namespace issues will be resolved.
When you map an integer value, for example 1, to a decimal field, expecting the output in the decimal field to be 1, but, instead, the decimal field result is 1.0. Create a new mapper activity, which needs to be a replica, in terms of naming and mappings, of the existing mapper activity. Once all the inwards and outwards mappings are done, delete the old mapper activity, which is already migrated, and point the transitions to the newly created mapper activity.
There is no tokenize-allow-empty() function in TIBCO BusinessWorks Container Edition . After migration to TIBCO BusinessWorks Container Edition , the tokenize() function can yield the same results as the tib:tokenize-allow-empty() and tib:tokenize() functions of 5.x.
When a mapper activity which has tokenize function inside a for-each expression, throws a Null Input at run-time? Post migration, convert the XSLT version in the activity from 1.0 to 2.0 since in 1.0, the for-each expression requires things to be evaluated to a node-set. Tokenize function creates sequence of string atoms, which is not node-set. In 2.0, for-each expression requires to be evaluated to sequence, which covers the sequence of atoms and sequence of node scenario.
Post migration, boolean always evaluates to false with XSLT 1.0 and validation off.
  1. Navigate to Windows > Preferences > Mapper and select the Assume all inputs untyped check box and click Apply, and then OK.
  2. Clean the project. The errors related to untyped input are displayed, and you can overcome these errors by performing a Quick Fix.
  3. Execute the project.