Ant, from Apache, is a Java-based build tool (see http://ant.apache.org/).

The BCEL package, from Apache, is required for correct operation of the Ant build scripts used by JOnAS. BCEL gives users a convenient way to analyze, create, and manipulate (binary) Java .class files. Classes are represented by objects that contain all the symbolic information of the given class: methods, fields, and byte code instructions, in particular.

Bean-managed persistence (BMP) occurs when the entity object manages its own persistence. The enterprise bean developer must implement persistence operations (such as JDBC) in the enterprise bean class methods.

CAROL (Common Architecture for RMI Objectweb Layer) is a library that enables the use of different RMI implementations (see http://carol.objectweb.org). With CAROL, a Java server application can be independent of RMI implementations and accessible simultaneously by RMI clients using different RMI implementations. CAROL allows the design, implementation, compilation, packaging, deployment, and execution of distributed applications compliant with the RMI model.

A new ORB used by JOnAS to provide clustering for load balancing and high availability.

CMP can be used to isolate an application developer from the physical database schema. This is done by creating an abstract schema that matches the needs of the current application, and using CMP to map between the abstract and physical schemas. The use of CMP ensures that applications are portable in the event of vendor or schema changes.

CMP is defined by the Enterprise JavaBeans 2.0 specification (see http://java.sun.com/products/ejb/2.0.html).

CORBA is Object Management Group's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks. Using the standard protocol IIOP, a CORBA-based program can interoperate with any other CORBA-based program. See http://www.omg.org/gettingstarted/corbafaq.htm.

A service used for deploying complete J2EE applications; that is, applications packaged in EAR files, which themselves contain ejb-jar files and/or WAR files.

The Sun Enterprise JavaBeans specification defines an architecture and interfaces for developing and deploying distributed Java server applications based on a multi-tier architecture. See http://java.sun.com/products/ejb/docs.html.

The intent of this specification is to facilitate and normalize the development, deployment, and assembly of application components (called enterprise beans); such components will be deployable on EJB platforms. The resulting applications are typically transactional, database-oriented, multi-user, secured, scalable, and portable. More precisely, this EJB specification addresses the runtime environment, called the EJB server, which provides the execution environment together with the transactional service, the distribution mechanisms, the persistence management, and the security.

IIOP maps GIOP messages to TCP/IP. The GIOP (General Inter-ORB Protocol) is a collection of message requests that ORBs can make over a network.

J2EE Connector Architecture. Sun's J2EE Connector Architecture provides a Java solution to the problem of connectivity between the many application servers and today's enterprise information systems.

JAAS is a set of APIs that enable services to authenticate and enforce user-based authorization.

JOnAS implements the Java Authorization Contract for Containers (JACC 1.0) specification. This enables you to manage authorizations as Java security permissions, and to plug in any security policy provider.

JDBC is an API that provides cross-database connectivity and access to other data sources, such as spreadsheets or flat files. See http://java.sun.com/products/jdbc.

JDO defines interfaces and classes to be used by application programmers when using classes whose instances are to be stored in persistent storage (persistence-capable classes), and specifies the contracts between suppliers of persistence-capable classes and the runtime environment (which is part of the JDO Implementation).

Jeremie is the RMI personality of Jonathan. It can be used in JOnAS to replace the standard RMI implementation and to optimize local calls.

Jetty is a Java HTTP Server and Servlet Container, which means that you do not need to configure and run a separate web server (such as Apache) in order to use java, servlets, and JSPs to generate dynamic content.

The JMS API enables J2EE application components to create, send, receive, and read messages.

JMS is provided by JORAM, a technology from ScalAgent (http://www.scalagent.com). See http://java.sun.com/products/jms.

JOnAS contains the Java Management Extension technology. Management and monitoring is available through a Web interface. See http://java.sun.com/products/JavaManagement.

JNDI provides Java applications with a unified interface to naming and directory services. See http://java.sun.com/products/jndi.

JOnAS (Java Open Application Server) is a distributed platform compliant with the EJB^TM specifications (see http://www.objectweb.org/jonas/index.html). JOnAS provides object distribution, security, distributed transactions, and object-persistence support according to these specifications. JOnAS also provides JMS^TM (Java Message Service) and JCEE^TM CA (J2EE Connector Architecture) support through its integration with JORAM and JORM.

Jonathan is an adaptable, distributed-object platform, that currently provides several personalities, including one compliant with the OMG CORBA specifications and another one with the RMI specification (see http://www.objectweb.org/jonathan/index.html). The RMI personality, called Jeremie, can be used in JOnAS to replace the standard RMI and optimize local calls.

JORAM is an open-source implementation of the JMS (Java Message Service) specification (see http://www.objectweb.org/joram/index.html). JORAM provides a MOM (Message Oriented Middleware) built on top of the ScalAgent distributed-agent technology (see http://www.scalagent.com).

JORM is an adaptable persistence service that offers various personalities, including one compliant with the CMP EJB specification and another with the JDO (Java Data Objects) specification (see http://www.objectweb.org/jorm/index.html). JORM provides object persistency through different secondary storage support, such as file, relational databases, or object-oriented databases. JORM includes an implementation of the JCA (Java Connector Architecture) specifications.

JSP provides a fast, easy way to create server- and platform-independent web applications (see http://java.sun.com/products/jsp/).

JTA specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server, and the transactional applications.

A JVM is a kind of translator that turns general Java platform instructions into tailored commands for devices.

MOM is a specific class of middleware that supports the exchange of general-purpose messages in a distributed application environment. Messages may be synchronous or asynchronous. The MOM system provides the directory, security, and administrative services required to support messaging.

In JOnAS, JORAM provides a MOM built on top of the ScalAgent distributed-agent technology (see http://www.scalagent.com).

The Object Request Broker (ORB) is the component of CORBA that provides all the communication infrastructure needed to identify and locate objects, handle connection management, deliver data, and request communications.

RMI/IIOP delivers CORBA distributed computing capabilities to the Java 2 platform. JOnAS now provides support for RMI/IIOP by integrating the CAROL communication framework.

Java Servlet technology provides Web developers with a simple, consistent mechanism for extending the functionality of a Web server and for accessing business systems. A servlet is like an applet that runs on the server side—but without a face.

A Web Container Service is a servlet/JSP engine in the JVM of the Red Hat Application Server server and the loading of web applications ("WAR files") within this engine. Currently this service can be configured to use Tomcat or Jetty, although only Tomcat is supplied with Red Hat Application Server.

Web application files.

The Web server is responsible for accepting client requests and sending HTML replies back to the client. HTML pages can be static files that reside on the Web server filesystem or dynamically built with Servlets or JSPs from data generated by the beans.

The JDBC Standard Extension API, part of Sun's Enterprise JavaBeans (EJB) technology, enables you to write distributed transactions that use connection pooling. It also makes it possible to connect to virtually any tabular data source, including files and spread sheets.