Users with the correct access rights can deploy a set of rules directly from the Enterprise console to Rule Execution Server, which is the runtime execution environment that integrates the rule engine.
Typically, Rule Execution Server is deployed to a test platform. The IT department is then responsible for the deployment to a production platform.
You can create the following deployment artifacts in the Enterprise console:
A ruleset is a set of rules and rule artifacts that can be executed by the engine.
A RuleApp is a deployable management unit that contains one or more rulesets.
In this task, you deploy a RuleApp from the Enterprise console to execute it in Rule Execution Server. Then, you see how the new rules affect the Miniloan web application.
This task should take you about 15 to 20 minutes to complete.
In this tutorial, the scenario is based on the web application of an online lender. The application is called Miniloan.
At this point, the Miniloan application uses a ruleset that was deployed to Rule Execution Server and that contains the initial state of the rules.
To start the Miniloan web application:
You take the role of configuration manager in Decision Center to create and deploy a RuleApp containing the rules of the miniloan-rules project. Because the changes that you made to the rule were small, you keep the version of the RuleApp as 1.0 but increase its ruleset version to 1.1. Then you see how Rule Execution Server handles these changes.
To create the RuleApp:
You can now deploy the RuleApp directly to Rule Execution Server.
To deploy the RuleApp:
Finally, you see how the business policy changes that you made are reflected back into the Miniloan application.
To see the effects in Miniloan:
You have now deployed your ruleset to Rule Execution Server. You can stop the tutorial here or continue to the next task which is optional and requires the installation of Rule Solutions for Office.