Creating a client for Rule Execution Server

To execute rulesets in Rule Execution Server, you must create session-type-specific client projects for RuleApps. You can modify the provided execution code generators and create your own. You can also call rulesets through stateless rule sessions or through message-driven rule beans.

Creating a POJO client project for RuleApps
You generate a POJO (Plain Old Java™ Object) client project for RuleApps by using the POJO generator. The POJO generator generates files that make it possible to execute a ruleset in Java SE with a file or database persistence.
Creating a web service or monitored transparent decision service project for RuleApps
You can create a web service or a monitored transparent decision service project for RuleApps by using the Web Service generator. With the generated file, you can execute a ruleset and create a monitored transparent decision service class.
Generating an SCA archive for Rational Application Developer
In Rule Designer, you can generate an SCA archive to import into Rational® Application Developer and deploy to WebSphere® Application Server.
Adding RuleApp execution artifacts to an existing project
You can add execution artifacts to an existing Rule Execution Server client project to execute RuleApps.
Creating a message body
If your client calls message-driven rule beans (MDB) for asynchronous message processing, you can create a message body that sets ruleset parameters in a hash map.
Using Java SE factories
To develop and package a client with Java rule sessions for Java SE, you write and compile the calling execution code, then ensure that all the files and the rule session JAR are accessible at run time.
Using POJO factories
To develop and package a client with Java rule sessions for Java EE, you write and compile the calling execution code, edit the deployment descriptors, then put all the files in the appropriate archives.
Using EJB factories
To develop and package a client with EJB rule sessions, you write and compile the calling execution code, edit the deployment descriptors, then put the rule session JAR and other files in the appropriate archives.
Calling a ruleset asynchronously
To set asynchronous ruleset execution, your code must create a stateless session and an execution request, specify the canonical ruleset path, pass input parameters, and create an observer.
Using message-driven rule beans
To develop and package a client using message-driven rule beans (MDB), write and compile the calling execution code, edit the deployment descriptors, then put the MDB JAR and all your other files in the appropriate archives.
Adding a decision identifier
You can identify the results of a ruleset execution by adding a decision identifier to the decision service request.
Customizing execution code generators
You can add new generators to the list of proposed project generators and modify existing project generators.

Parent topic: Developing client applications