Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Migrating Projects from Earlier Versions : Clean and Validate 3.x Projects

Clean and Validate 3.x Projects
This section explains how to clean and validate a 3.x project, and how to fix errors. Also see Project Migration Overview for none-release-specific information.
Clean and Validate the Project
After you import the 3.x project into TIBCO BusinessEvents Studio Explorer, do the following:
1.
All build problems and build states are discarded. The project is rebuilt from scratch.
2.
You may see some common validation errors that are addressed in the following sections. If you see additional errors that you cannot resolve, contact your TIBCO representative for assistance.
Fixing Ambiguous Reference Errors (Unqualified References)
During migration, duplicate name references can cause issues. If the project contains unqualified references to rules, rule functions, or ontology types, and any of the rules, rule functions, or ontology types have the same simple name, duplicate name validation errors will result.
In the TIBCO BusinessEvents Studio Problems tab, you may see listings for these issues, such as the following:
Ambiguous reference. Reference must be qualified, as multiple elements exist with the same name [/sharedResources/Element, Rules/Element, Concepts/Element]
One source of this issue is that beginning with the 4.0.0 release, rules are separate resources, whereas in the 3.x product, they exist within ruleset resources.
To Resolve the Issue  Qualify all such ambiguous references.
Fixing XSLT Mapper Errors
If you have used the XPath (XSLT) mapper in TIBCO Designer, there could be errors that prevent a clean validation of the project after it is imported.
In 3.x, XSLT Mapper errors were not reported during project validation. This validation has been added, beginning with the 4.0.0 release. Therefore, any mapper errors must be fixed before project validation can be successful. These errors existed in the 3.x product, though they may not have caused any runtime problems.
To Resolve the Issue  In TIBCO BusinessEvents Studio double-click those items in the Problems view. The rule editor displays the corresponding rule or rule function. In the editor. Check for red error indicators on lines containing function mapping. Where you see an error indicator on a line containing Mapper code, Ctrl-click the underlined argument text to open the Function Argument Mapper dialog. Click the Mapper Check and Repair (check-mark icon) button.
Some errors can be auto-fixed: Click the validate option (the check mark) in the mapper. You see the Mapper Check and Repair dialog. Select the items you want to fix and click OK. (Using auto-fix is harmless even if the errors cannot be auto-fixed.) Then manually fix any errors that cannot be autofixed. For example, errors such as undefined variable errors cannot be fixed automatically.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved