Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Developer's Guide to J2EE Services and APIs

> ## Chapter 1
> Overview of J2EE Services and APIs

> The Java™ 2 Platform, Enterprise Edition (or J2EE™ Platform) includes services and APIs that are available as resources to all J2EE applications and modules. The Sun Java™ System Application Server 7, a J2EE 1.3 compliant server, provides access to these resources. This guide describes the following services and APIs:

> - Java Database Connectivity (JDBC) API
> - Transaction Service
> - Java Naming and Directory Interface (JNDI) API
> - Java Message Service (JMS) API
> - JavaMail API

> ##

> Java Database Connectivity (JDBC) API

> The standard way to connect to a database from a J2EE application or module is through a Java™ Database Connectivity (JDBC™) driver. Sun Java System Application Server supports the core JDBC 3.0 API and the JDBC 2.0 extensions and works with a wide range of JDBC Compliant™ drivers. A JDBC resource associates a JDBC driver and database to a JNDI name that applications and modules can reference.

> For information about the JDBC API in the Sun Java System Application Server, see Chapter 2, “Using the JDBC API for Database Access.”

> ##

> Transaction Service

> The purpose of a transaction is to ensure that data is updated in an all-or-nothing fashion in order to preserve data integrity. The transaction service provides transactional resource managers for the JDBC API, the JMS API, and resource adapters (connector modules). In the Sun Java System Application Server, you can configure transactions and reference them using the JNDI API.

> For information about transactions in Sun Java System Application Server, see Chapter 3, “Using the Transaction Service.”

> ##

> Java Naming and Directory Interface (JNDI) API

> The Java Naming and Directory Interface™ (JNDI) API allows application components and clients to look up distributed resources, services, and EJB™ components. The J2EE resources described in this guide are made available through the JNDI API. External JNDI resources and custom resources are also configurable in the Sun Java System Application Server.

> For information about the JNDI API in the Sun Java System Application Server, see Chapter 4, “Using the Java Naming and Directory Interface.”

> ##

> Java Message Service (JMS) API

> The Java™ Message Service (JMS) API provides a common way for J2EE applications and modules to create, send, and receive messages in a distributed environment. The fully integrated JMS provider for Sun Java System Application Server is the Sun Java™ System Message Queue software. JMS connection factory and destination objects are made available through the JNDI API.

> For information about the JMS API in the Sun Java System Application Server, see Chapter 5, “Using the Java Message Service.”

> ##

> JavaMail API

> The JavaMail™ API allows J2EE applications to create, send, receive, and read mail messages. The JavaMail API includes support for the IMAP4, POP3, and SMTP mail protocols. JavaMail sessions are made available through the JNDI API.

> For information about the JavaMail API in the Sun Java System Application Server, see Chapter 6, “Using the JavaMail API.”

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.