Before you configure Rule Execution Server on Java SE

Some limitations affect the configuration of Rule Execution Server on Java™ SE.

If you use Java SE embedded in your application server, you can use the standard Java Management Extensions (JMX) notification mechanism, provided that the Rule Execution Server console is deployed in the same Java virtual machine (JVM). If you use Rule Execution Server in a Java SE environment on a stand-alone JVM, you must enable the TCP/IP management mode to manage Java SE notification. See Configuring execution units (XU) to connect to a TCP/IP management server.

Typically, you configure Rule Execution Server in the following steps:
  1. Setting the class path for Java SE.
  2. Changing the persistence mode. If necessary, create your database and SQL table, and JDBC access, with JNDI lookup.
The following limitations apply to rule sessions:
  • The execution unit (XU) is not shared. Therefore, it consumes more memory.
  • Connection pools are configured only through the ra.xml deployment descriptor.
  • Only Java SE rule sessions are available. This restriction has the following consequences:
    • Remote calls such as Java Message Services (JMS) or EJB are not possible.
    • No transaction support: you must implement your own transaction management logic as EJB does.

Database driver issues

The JDBC Not Bound error message is issued when an error occurs during the creation of the data source.

Refer to the traces to locate the original cause. In the vast majority of cases one of the following is likely:
  • A directory does not exist or cannot be read or written to (H2).
  • There is a missing schema or table.
  • There are missing privileges to access the database resource.