"Rule model extensions are different" warning at synchronization after upgrading to V7.1.x
After migrating to v7.1.x, synchronization between Rule Studio and Rule Team Server fails because the model extensions are not the same, even though the default model extensions are being used.
The warning "Rule model extensions are different" is displayed when connecting Rule Studio to Rule Team Server:
The default extension file in Rule Studio has annotations for effectiveDate:
<property extractable="true" name="effectiveDate" type="Date">
<annotation id="validator-compared-property" value="expirationDate" />
<annotation id="validator-constraint" value="LESSTHAN" />
In RTS, the default model extension does not have the above annotations : it is possible that when migrating to RTS V7.1.x, the model extension files were not updated.
However, since the Rule Studio model extension files were updated as expected, the synchronization with RTS fails.
Resolving the problem
Update the model extensions in Rule Team Server:
- Navigate to the "Configure" tab and click on "Installation Manager" .
- Go to "Step 1: Configure Database".
- Under "Select the extension files you want to use:" choose "Custom extensions" and navigate to the default extensions used by Rule Studio, which can be found under <JRulesInstallDir>\studio\eclipse\plugins\ilog.rules.commonbrm.extension_18.104.22.168\resources\, if working with JRules v22.214.171.124.
- Select "Upload Only".
- Click on "Apply".
- This should take you to a "Processing" view, and then back to the "Configure Rule Team Server database" page with a message that says "Step execution successful".
- Click on "Exit".
This will upload the v7.1.x extensions, and you should be able to synchronize with Studio properly.
For any additional synchronization issues, please refer to this document.
More support for:
WebSphere ILOG Rule Team Server
Software version: 7.0, 7.1
Operating system(s): Platform Independent
Reference #: 1587770
Modified date: 08 February 2013