This page describes configuration and usage of the kmodules included with PXE. A kmodule is an MBean that is configured and deployed by the PXE Microkernel. Each kmodule is registered at a different ObjectName and includes a set of attributes used to configure the kmodule before it is started.

Order of deployment is very important, since some kmodules rely on availability of other services at start up time. MBeans are deployed in the order described in the kernel deployment descriptor.

• ModBpelEventLogger Kmodule — creates a JMX notification listener that appends the BPEL execution event stream to the system log in the pxe.bpel.event.log category.
• ModDeployer Kmodule — polls a filesystem directory for SAR or JAR files to deploy as systems.
• ModFsNaming Kmodule — provides a lightweight JNDI naming service.
• ModHibernateDao Kmodule — configures and deploys a Hibernate-based implementation of the DAO layers for both the [service framework] and the BPEL Service Provider.
• ModJdbcDS Kmodule — deploys a [minerva]-wrapped JDBC datasource for use by other kmodules.
• ModJetty Kmodule — launches an instance of the Jetty servlet container.
• ModJmxRemote Kmodule — starts a JMX remoting JMXConnectorServer.
• ModJOTM Kmodule — deploys JOTM as a JTA transaction manager for use by other kmodules.
• ModMemDAO Kmodule — configures and deploys a in-memory implementation of the DAO layers for both the [service framework] and the BPEL Service Provider.
• ModRmiRegistry Kmodule — starts an RMI registry.
• ModSvcProvider Kmodule — binds a service provider factory into JNDI.