Rule Builder > Deployment > Introduction to Deployment > Deployment Types |
Deployment Types |
PREVIOUS NEXT |
Deployment is making the ruleset or RuleApp available to an engine or BRE Server, typically through an external data source (file or archive). The result can be either an extracted ruleset or an extracted RuleApp.
Deployment is the process that takes a project as its input and ends up with one or several running rule engines initialized with the exported ruleset. When you deal directly with deployed rulesets, you have to write the application code and specify all aspects of the deployment, including the way to create and manage the rule engine, the way to parse the ruleset, load it, and execute it. The developer must perform all the steps manually. This has traditionally been the way of deploying a ruleset in a business rule application and is the simplest route to deployment in a J2SE application. A ruleset is extracted and exported as a file containing the ruleset code in IRL or XRL format.
Deployment uses rulesets and the executable (non-Java) resources that rulesets rely on when they are executed by the rule engine. The resources consist of a dynamic XOM, and execution and monitoring configuration data. A RuleApp is extracted for a project and deployed on one or more target BRE Servers. A RuleApp can be exported to an archive as a file or deployed directly on a BRE Server. A RuleApp can also be deployed from an archive file using either Ant scripts or the BRE Server Console.
Exporting a Ruleset | Exporting a RuleApp Archive | Deploying a RuleApp | Opening the BRE Server Console
Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |