How IBM WebSphere Application Server uses EJB technology
This table illustrates how IBM WebSphere Application Server, Advanced Edition 2.0, uses various aspects of EJB technology.
| Specification | Role in WebSphere Application Server Advanced Edition 2.0 |
| EJB | The Enterprise JavaBeans engine is one of the main WebSphere Application Server components. Through the manager interface, WebSphere Application Server supports definition of EJB containers and deployment of EJBs. Container-managed persistence is provided natively using DB2. Both session and entity beans are supported. |
| JDBC | JDBC technology provides cross-DBMS connectivity to a wide range of SQL databases, each of which requires a specific driver. JDBC-based database access is a typical way of providing EJB persistence. WebSphere Application Server ships with native support for DB2, but can use other JDBC-compliant databases. The Connection Manager component increases efficiency of database access. |
| JNDI | The Java Naming and Directory Interface is independent of any specific directory service. The JNDI architecture consists of an API (Application Programming Interface) and an SPI (Service Provider Interface). Java applications use the JNDI API to access a variety of naming and directory services. The SPI enables naming and directory services to be plugged in transparently, allowing the Java application to access their services. The Directory Management page in the manager application allows the user to specify settings for a directory server, for example, an LDAP server. |
| JTA | The Java Transaction API supports invocation of transaction methods provided by JTS. The transaction attribute value in an EJB deployment descriptor, such as
TX_MANDATORY, indicates the type of transaction support required by the EJB.
|
| JTS | The Java Transaction Service is a Java implementation of the OMG Object Transaction Service, and provides underlying transaction support requested through JTA. |
| JSP | Java Server Pages is the Java platform technology for building applications with dynamic Web content such as HTML, DHTML, and XML. WebSphere supports applications using JSPs, including automatic compilation of JSPs into servlets. |
| Servlet | The HttpServlet class provides an abstract class to be subclassed to create an HTTP servlet suitable for a Web site. Along with EJBs, the servlet engine forms one of the main WebSphere Application Server components. Servlets, analogous to applets on a client, allow development of server-side Java applications that are easier, more portable, and faster than equivalent CGI applications. |
| RMI | Remote Method Invocation enables clients to run methods on objects residing on remote servers. EJBs use RMI; for example, the EJBHome and EJBObject interfaces extend
java.rmi.Remote. RMI is the transport mechanism used by WebSphere Application Server.
|
Return to the article.