Using the CA Rule Engine › Construction of Java Client Applications

Construction of Java Client Applications

This chapter presents the general principles for constructing the Java client application. On the client side, CA Rule Engine makes the following extensions to the JSR‑94 specification:

• Additional features, beyond standard bean features, are required for constructing Java classes that map instances between the client side and the inference engine.
• If the rulebase contains two or more appshared domains, the inference engine must be informed about which domain will be used by the client.

For more information, see CA Technologies Extensions to the JSR‑94 Specification and Special Considerations.

The following major points must be understood when constructing the Java client application:

• There are CA Rule Engine specific rules for constructing Java classes so that CA Rule Engine can coordinate instances on the client side with instances on the rulebase/inference engine side.
• Once the application classes are constructed correctly, the Java client application must include JSR-94 specific coding to acquire a rule execution set and rule session.
• The application must add objects from the client application to the inference engine and retrieve the results of inferencing following JSR-94 specification. For more information, see Addition and Retrieval of Inference Engine Objects. The JSR‑94 specification also provides a way for the client application to filter results of inferencing by supplying filter objects.

Note: For an existing rulebase, the supplied WrapperMaker tool can be used to automatically construct the Java classes that wrap the rulebase classes. The Java source code for the sample applications can be found in samples folder inside the CA Rule Engine distribution. The sample applications also provide client test applications.

More information

Rules for Constructing Java Classes

Specify a Shared Domain

Acquire the RuleExecutionSet and RuleSession

Using the WrapperMaker Tool