Rule Builder > Introduction to the Rule Builder > User Roles and the Rule Builder > Developer Tasks and Section Links |
Developer Tasks and Section Links |
PREVIOUS NEXT |
Developers have access to the complete functionality of the Rule Builder and may be involved in any of the tasks described in this online help. However, the tasks that are specific to developers are shown in Table 1.4:
Debugging and testing the execution of the rulesets. | Debugging. |
Debugging ruleset execution on a BRE Server. | Debugging a Ruleset on a BRE Server. |
Profiling the execution of the rules to provide performance statistics on business objects and rules during the execution of a ruleset. | Profiling. |
Setting up and maintaining the CVS repository for management of concurrent repository access. | Working with Repositories in CVS. |
Setting up the objects in the Execution Object Model. | Setting Up the Execution Object Model. |
Deploying rulesets in the traditional way or on a Business Rule Execution (BRE) Server using a RuleApp. | Exporting a Ruleset and Deployment. |
Migrating a repository from an earlier version of JRules to the current one. | Migrating a Repository. |
Setting ruleset parameters to exchange data between a client application and a ruleset. | Ruleset Parameters. |
Creating a set of functions whose code is evaluated when the rule engine is initialized. | Functions and Adding Functions to a Top-Level Package. |
Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |