Product

Kodak^® Prinergy^® Connect^™, version 4.x or later

Operating system

Microsoft Windows Server^® 2003

Symptoms

You are reluctant to upgrade from a Prinergy 3.x system to a Prinergy 4.x system because of concern over the compatibility of your rule sets with the new Prinergy version.

Solution

You can verify that the Prinergy 3.x rule sets will compile when migrated to the Prinergy 4.x system by exporting them to an existing Prinergy 4.x system.

Note: This procedure will only show whether a rule set from a 3.x system will compile on a 4.x system. It does not guarantee that the rule set will run in the new environment. See Other Considerations.

1. On the Prinergy 3.x server, create a folder on the hard drive named Export.
2. Start Prinergy Workshop, and in the Job Finder window, select Tools > Rule Set Manager.
3. Export the rule sets that you want to verify:
1. In the Rule Set Library list, right-click a rule set that you want to verify and select Export.
   If you want to export all the rule sets, right-click the root Rule Sets folder.

Note: If you export all the rule sets, the process may take several minutes to complete.
2. In the Export dialog box, locate the Export folder you created and click Save.
3. Repeat for each rule set that you want to verify.

The system stores a zipped file of the rule sets (called x_rulesets.zip or all_rulesets.zip) in the Export folder.

4. Locate the \Program Files\Kodak\RBA\bin\Rules\Extensions folder, and copy any custom dll files to the Export folder.
5. Copy the Export folder to the hard drive of the Prinergy 4.x server that you are using to test the compilation.

Important: The Prinergy 4.x version and build installed on the server must be identical to the version and build that the customer intends to upgrade to.
6. On the Prinergy 4.x server, open the Export folder and copy any custom dll files to the \Program Files\Kodak\RBA\bin\Rules\Extensions folder.
7. Start Prinergy Workshop, and in the Job Finder window, select Tools > Rule Set Manager.
8. Import the rule sets:
1. Select File > Import.
2. In the Import dialog box, locate the rule sets stored in the Export folder on the server's hard drive, and click Import.

The system automatically extracts the zipped files and places them in the Rule Set Library.
9. In the Rule Set Library, locate the rule sets that you imported. If the Disabled Rule Set icon appears beside a rule set, it has compiled correctly.

If the red Incomplete Rule Set icon appears, it has not compiled correctly. Double-click the rule set to open it, click an operator, move it slightly, and then save the rule set. The system recompiles the rule set.

If the rule set still doesn't compile correctly, do the following steps:

• Locate \Program Files\Kodak\RBA\bin\, and look for the ruleset dll file.
• Manually delete the file while the Prinergy service is running.
• Restart Prinergy.
• Open Task Manager and confirm that the AutomationApp and WebServerApp processes are running.
• Start Prinergy Workshop and open the Rule Set Manager (Tools > Rule Set Manager). Locate the rule sets that you imported and confirm that the Disabled Rule Set icon appears beside each rule set.
10. Double-click each imported rule set to open it, and confirm that all the connectors are gray, not red.
11. Right-click an imported rule set and select Enable. Right-click the rule set again and select Get Info. The State should be Complete.

Other Considerations

The Prinergy team takes special care to ensure rule set compatibility, but if changes occur in the customer's network environment, the rule sets may be affected. Factors that may disable rule sets include the following:

• The rule set refers to a file name, file path, or server name that has changed or is no longer available.
• The rule set refers to a process template (for example—APA, ICC) that no longer exists or has moved.
• The rule set refers to an XML schema that no longer exists.
• Breaking changes have occurred in the .NET Framework 2.0 software. For details, see Breaking Changes in .NET Framework 2.0.

Keywords

RBA, automation, upgrade

Technical contact(s)

Submitted by

Date submitted

28 Feb 2008