| ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Administering Rule Execution Server > Adding Execution Unit (XU) JCA 1.5 Connection Factories > Introducing Connection Factories |
Introducing Connection Factories |
PREVIOUS NEXT |
As stated in the J2EE Connector Architecture (JCA) 1.5 specification, a resource adapter instance may provide bidirectional connectivity to multiple EIS instances. Each ManagedConnectionFactory instance creates connections to a specific EIS instance based on the properties configured on the ManagedConnectionFactory instance.
The configurable properties are specified only once in the deployment descriptor, even though a resource adapter can be used to configure multiple ManagedConnnectionFactory instances that create connections to different instances of the same underlying EIS type.
In other words, JCA 1.5 supports the definition of multiple connection factories for each resource adapter, and ordinarily application servers permit a single dedicated connection pool for each connection factory.
You can create multiple instances of the connection factory by using the application server specific deployment descriptor. The Execution Unit (XU) descriptor (ra.xml) contains the declaration of the connection factory properties (name, default value, and type). The XU plug-in properties must be declared in the connection factory property.
The descriptor registers a management MBean named IlrXUManagementMBean. The Rule Execution Server Console uses the IlrXUManagementMBean to retrieve XU logs, XU statistics, and notify the XU that a ruleset has been modified (added, removed, or just changed in some way).
If there is more than one connection-definition for the XU, one definition must use the default MBean class:
{pluginClass=ilog.rules.bres.xu.management.IlrManagementMBeanPlugin,xuName=managementXU}
and other connection-definitions must use:
{pluginClass=ilog.rules.bres.xu.management.IlrMonitoringMBeanPlugin,xuName=monitoringXU}
A specific application server deployment descriptor of a connector may overwrite the default values of the properties. WebLogic, JBoss, and OC4J use this deployment descriptor file. In WebSphere you have to use a scripting language (JACL) to change the properties.
In WebSphere, WebLogic, and OC4J you can also add an instance of a connection factory and modify the properties of a factory using the administration console.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |