Welcome to ILOG JRules > About ILOG JRules 6.7 > Migration from JRules 5.1 > How to Migrate RuleApps

The res-migrate Ant task migrates a RuleApp archive created in JRules 5.1 to a JRules 6.x compatible RuleApp archive.

Warning
This Ant task will be removed in the next major release.

images/resant.png

To perform a RuleApp archive migration from a running application server where the BRE Server has been installed:

  1. Use the JRules 5.1 res-fetch-all Ant task to backup all your RuleApps in a single RuleApp archive. Or use res-fetch Ant task to backup a specific RuleApp.
  2. Install JRules 6.x and Rule Execution Server on your application server.
    Warning
    Uninstall all BRE Server components of previous versions before installing new versions.
  3. Use the res-migrate Ant task to migrate your RuleApp archives
  4. Deploy your RuleApp archives on the new management console with the JRules 6.x res-deploy Ant task.

Table 35 res-migrate Element Attributes 
Element Attribute 
Description 
Required 
file 
The JRules 5.1 RuleApp archive to migrate. 
Yes 
destfile 
The destination of the stored JRules 6.x RuleApp archive file. 
Yes 

classpath Subelement

Not required. The classpath subelement declares the global classpath used to parse rulesets of the JRules 5.1 RuleApp archive. For more information on the classpath subelement, see the Ant documentation and in particular path-like values.

include Subelement

Not required. The include subelement specifies the rulesets that will be migrated. This is useful if there is a XOM incompatibility problem between rulesets. By default all rulesets are migrated.

Table 36 include Subelement Attributes 
Element Attribute 
Description 
Required 
name 
A canonical ruleset path, or an ant regexp to match several canonical ruleset paths. For more information on the regexp syntax, see the Ant documentation and in particular the regexp core type. 
Yes 

exclude Subelement

Not required. The exclude subelement specifies what rulesets will not be migrated.This is useful if there is a XOM incompatibility problem between rulesets.

Table 37 exclude Subelement Attributes 
Element Attribute 
Description 
Required 
name 
A canonical ruleset path, or an ant regexp to match several canonical ruleset paths. For more information on the regexp syntax, see the Ant documentation and in particular the regexp core type. 
Yes 

Examples

To migrate all rulesets of a RuleApp:

      <res-migrate file="myruleappV5.jar" destfile="myruleappV6.jar">
          <classpath>
              <pathelement location="myxom.jar" />
          </classpath>
      </res-migrate>

After the execution, myruleappV6.jar contains all the RuleApp/rulesets of myruleappV5.jar in the new format.

Using the include subelement to solve a static XOM incompatibility problem:

      <res-migrate file="ruleappV5.jar" destfile="ruleappV6.jar">
          <classpath>
              <pathelement location="myxomV1.jar" />
          </classpath>
          <include name="/myruleapp/1.0/myruleset/1.0" />
      </res-migrate>

After the execution, myruleappV6.jar contains only the RuleApp "/myruleapp/1.0" with the ruleset "myruleset/1.0" in the new format.

Related Concepts

JRules 5.1 Execution Artifacts and Code Migration

Related Tasks

How to Migrate Standard Repository Elements
How to Migrate IRL Ruleset Files
How to Migrate RuleApps
How to Migrate Business Rules that Use Custom Value Editors
How to Migrate Rule Projects Containing Multiple BOMs
How to Migrate Projects that use BOM Extensions
How to Migrate Translation Properties
Administering Rule Execution Server