EAServer implements the Java 2 Enterprise Edition (J2EE) 1.3 specification, with support for EJB 2.0 components, J2EE applications, J2EE Web applications, object caching, the JavaMail electronic mail API, the connector architecture, Java API for XML Parsing, and the Java Authentication and Authorization Services.
“Component support” describes EAServer’s supported component models, including EJB.
A Web application is a unit of deployment for interrelated Web content, JavaServer Pages (JSPs), and Java servlets. The Web application contains static files, servlet and JSP implementation classes, and a deployment descriptor that describes how the files, servlets, and JSPs are configured on the host server. See Chapter 21, “Creating Web Applications,” in the EAServer Programmer’s Guide.
J2EE applications allow you to group related EJB 2.0 components and Web applications into a single entity. In this way, you can deploy related business logic components, Java servlets, JavaServer Pages, and Web pages as a single unit between servers. Using the J2EE Application Client model, you can create clients that call the components and Web pages in the application. For more information, see these chapters in the EAServer Programmer’s Guide:
EAServer supports EJB 2.0 container-managed persistence (CMP) for EJB entity bean components, as well as supporting an automatic persistence model for components of other types. EAServer also supports entity instance and finder-query caching, which can improve performance by minimizing the number of database select queries required to execute business logic. For information on entity components, automatic persistence, and object/query caching, see Chapter 27, “Creating Entity Components,” in the EAServer Programmer’s Guide.
The JavaMail API provides a standard Java interface to the most widely-used Internet mail protocols. See Chapter 35, “Creating JavaMail,” in the EAServer Programmer’s Guide for more information.
The J2EE connector architecture enables you to write portable Java applications that can access multiple transactional enterprise information systems. A connector is a specialized connection factory that provides connections for EJBs, Java servlets, JSPs, and CORBA-Java components. For more information, see Chapter 4, “Database Access,” in the EAServer System Administration Guide.
EAServer can host Web applications in popular Web servers such as Apache, iPlanet, and Netscape. For more information, see the EAServer Installation Guide for your platform.
EAServer implements J2EE version 1.3 security requirements including Java and C++ ORB support and CORBA Secure Interoperable version 2 protocol (CSIv2). For more information, see the EAServer Security Administration and Programming Guide.
EAServer includes support for the Java API for XML Parsing 1.1. You can configure the parser and transformer implementations for servers, components, Web applications, and application clients.
Java Authentication and Authorization Services (JAAS) provide a framework and standard programming interface for authenticating users and assigning privileges. JAAS is based on the Pluggable Authentication Module standard, which extends the access-control architecture of the Java 2 platform to support user-based authentication and authorization. For more information, see the EAServer Security Administration and Programming Guide.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|