This section describes the process you must follow to clone rule sets
included with the application so that you can customize the cloned rule
sets to meet your product's needs.
If you need to customize any rules element in a rule set included with
the application, or if you rely on the current functionality of the
version of a rule set included with the application, then you must clone
the rule set and all of its dependencies, in terms of application derived
data/business logic rules classes (but not infrastructure rule
classes).
CAUTION:
Please refer to the Rule Set Interdependencies developer documentation
located alongside the Data Dictionary for more information on which rule
sets are Application (clone-able) and which are Infrastructure (not clone-able).
Follow these steps to clone rule sets:
- Identify the rule set(s) that is your entry point into the rules
(typically from a rule class).
- For each of these rule sets, follow the arrows on the ruleset inter-dependency documentation,
to find any other Application rule sets on which those to
customize depend. Repeat this step recursively until there are no more
links to Application rule sets.
- For each of the Application rule sets found in the above steps, follow the arrows backwards to pick up any
additional Application rule sets that depend on the rule sets found so far. Repeat this step recursively until there
are no more links to follow backwards.
- Each of the Application rule sets found during the above steps must
now be cloned. Follow the steps below.
- For each rule set to be cloned, copy its rule set source XML
file from EJBServer/components/ component name
/CREOLE_Rule_Sets/ someruleset.xml to EJBServer/components/custom/CREOLE_Rule_Sets/ someruleset Custom.xml
.
- For each cloned rule set, create an entry in
EJBServer/components/custom/data/initial/CREOLERuleSet.dmx
(which you must create if it does not already exist). The contents of this entry should be a copy of the entry for the original rule set, with the exception of the 'ruleSetDefinition' attribute. This should be updated to the new location of the cloned rule set in the custom component.
- Similarly, for each cloned rule set, create an entry in
EJBServer/components/custom/data/initial/AppResource.dmx
(which you must create if it does not already exist). The contents of this entry should be a copy of the entry for the original rule set, with the exception of the 'content' attribute. This should be updated to the new location of the cloned rule set in the custom component.
On completion of rule set cloning, if you wish to add further propagator configuration for your cloned rule sets, you should complete these in the custom directory:
- Propagator configurations should be added to: EJBServer/components/ custom /data/ directory
/RuleObjectProapgatorConfig.dmx
- Propagator configuration XML files should be located in the blob/clob
directories within the custom data directories.