Configuring Javamail Resources; Creating A Javamail Session - Sun Microsystems GlassFish Enterprise Server 2.1 Administration Manual

Hide thumbs Also See for GlassFish Enterprise Server 2.1:
Table of Contents

Advertisement

5
C H A P T E R
5

Configuring JavaMail Resources

The Enterprise Server includes the JavaMail API. The JavaMail API is a set of abstract APIs that
model a mail system. The API provides a platform-independent and protocol-independent
framework to build mail and messaging applications. The JavaMail API provides facilities for
reading and sending electronic messages. Service providers implement particular protocols.
Using the JavaMail API you can add email capabilities to your applications. JavaMail provides
access from Java applications to Internet Message Access Protocol (IMAP) and Simple Mail
Transfer Protocol (SMTP) capable mail servers on your network or the Internet. It does not
provide mail server functionality; you must have access to a mail server to use JavaMail.
The JavaMail API is implemented as a Java platform optional package and is also available as
part of the J2EE platform.
The Enterprise Server includes the JavaMail API along with JavaMail service providers that
allow an application component to send email notifications over the Internet and to read email
from IMAP and POP3 mail servers.
To learn more about the JavaMail API, consult the JavaMail web site at
http://java.sun.com/products/javamail/.
This section contains the following topic:

Creating a JavaMail Session

To configure JavaMail for use in Enterprise Server, create a Mail Session in the Enterprise Server
Admin Console. This allows server-side components and applications to access JavaMail
services with JNDI, using the Session properties you assign for them. When creating a Mail
Session, you can designate the mail hosts, transport and store protocols, and the default mail
user in the Admin Console so that components that use JavaMail do not have to set these
properties. Applications that are heavy email users benefit because the Application Server
creates a single Session object and makes it available via JNDI to any component that needs it.
75

Advertisement

Table of Contents
loading

Table of Contents