You can deploy a RuleApp directly to a Rule Execution Server or generate a .jar file for later deployment.
The Configuration Manager creates RuleApps, as described in Managing RuleApps.
When you deploy a RuleApp you can create a baseline for the deployment. The deployment baseline identifies the version of all the rule project elements contained in the set of rules that make up the RuleApp. Then, to redeploy the RuleApp at some later time, you can choose whether the state of the rules corresponds to the initial deployment or to a subsequent redeployment. The baseline for the deployment is the same as for a standard baseline in that you can consult it in the list of baselines, but it is created from the ruleset extraction and handles project dependencies differently.
When you deploy to a Rule Execution Server, you must set the versioning policy and choose the correct server from the list of available servers:
To handle the versioning of the deployed RuleApps, specify whether to increment the major or minor versions of the RuleApp or the rulesets it contains, or whether to replace theme. For more information, refer to the Rule Execution Server online help.
The Configuration Manager manages the list of available servers.
To deploy a RuleApp:
Details of the deployment are given at the end, with the version numbers assigned by Rule Execution Server indicated.