JOnAS features

EJB 1.1: Enterprise JavaBeans containers are provided by a set of Java classes and a tool to generate interposition classes

JTA 1.0.1: a Transaction Manager provides Java Transaction API support and distributed transaction coordination

JDBC 2.0: a Database Manager providing Java DataBase Connectivity support

JMS 2.0.1: Java Messaging Service is provided by JORAM, a technology from ScalAgent

JMX: JOnAS contains the Java Management Extension technology. Management and monitoring is available through a Web interface

JCA 1.0: JOnAS supports the J2EE Connector Architecture that defines a set of mechanism that enable the integration of Enterprise Information Systems (EIS)

Security management

ejb: this is the EJB container service. This service is usually mandatory, it can only be disabled if you want to run a standalone jtm service (jtm without any other services).

jtm: this is the distributed Transaction Manager. This service is mandatory even if you use a single jtm for several JOnAS server, every server must start the jtm server (for more information about running multiple JOnAS servers, see the section called Running multiple JOnAS servers in the chapter called Getting started with JOnAS)

dbm: the DataBase Manager provides database access through JDBC. You must turn it on if you want to access a database from your beans (bean or container managed persistence).

jms: the Java Messaging Service must be started if you use message-driven beans. Note that the jms must be started before the ejb service.

security: this is the security service.

jmx: this service allows to manage and monitor JOnAS through a Web interface using JAdmin. Note that if you want to use jmx, it must be the first service to be started.

resource: the resource service is an optional service that must be started as soon as EJB components have to access an external Enterprise Information System. Yhe standard way of doing this is to use a third party software component called Resource Adapter.