Certain resources are compatible with one or both engine versions. This topic describes these resources.
Some resources must be first converted in order to work with the new engine, while some will work with both versions. Others are no longer necessary in the new engine, due to additional version 2 Ruleset functionality. The list below describes objects and compatibility status as it relates to the new transformation engine.
|Business Process||The Business Process object is unique among most other resources in that is backwards compliant with the new engine; a Business Process that works with the current engine can also support the new engine, as long it is converted. Once converted, it still can support the current engine.|
|Code Table||This object is compatible with the new engine. No conversion is necessary.|
|Ruleset Data Object||This object is compatible with the new engine by default; however if previously referenced from an older Ruleset, it must be converted before it can work with the newer Ruleset.|
|Application Interface||This object is compatible with the new engine by default; however if previously referenced from an older Ruleset, it must be converted before it can work with the newer Ruleset.|
|SQL Access||This object is compatible with the new engine by default; however if previously referenced from an older Ruleset, it must be converted before it can work with the newer Ruleset.|
|Formula||Instead of using the Formula object, users can now write their own actions in Java. This object is no longer used in the new transformation engine. See Using Custom Actions in the New Engine.|
|External Java Program||This object is no longer used in the new transformation engine. This object was a binding between a Ruleset and Java Code. Now you can call Java directly from a Ruleset. See Using Custom Actions in the New Engine.|
|Database Adapter||The Database Adapter is unique among most other resources in that it can support both versions of the transformation engine. See How Database Adapters work with the New Engine for more information.|
Note: Validation of Java keywords may require changes to variables in certain resources that are converted. These include the Business Process, Application Interface, and SQL Access.
Upgrading Older (pre-4.6) Projects
Once you’ve successfully upgraded to Cleo Clarify v4.6, please take the following steps to upgrade Project settings for all existing Workspaces and Projects.
- Projects must be open in the Project Explorer view in order for the upgrade to complete.
- If using multiple workspaces, the upgrade steps described here must take place for each workspace in your environment.
- New Projects created in v4.6 do not require the upgrade.
To upgrade: From the Clarify Studio’s main menu, select Project>Upgrade project configurations. All open Projects will be upgraded.
Result: Clarify performs the following for each Project in your workspace.
- Rebuilds the Project. This generates required Java code for all resources.
Note: Please let this process complete; you may wish to reserve sufficient time for this process, based on number of Projects you have.
- Creates the ebi-gen directory (if one does not already exist). This folder contains Java representations of the Clarify objects per Project.
- Updates MANIFEST.MF and build.properties Java Environment to 1.7.
Your workspace is now up-to-date with the Clarify v4.6 release.
Please sign in to leave a comment.