This page provides a starting point for finding information about Web applications,
which are comprised of one or more related files that you can manage as a unit, including
HTML files, JavaServer Pages (JSP) files, and servlets.
This page provides a starting point for finding information about enterprise beans.
Based on the Enterprise JavaBeans (EJB) specification, enterprise beans are Java
components that typically implement the business logic of Java 2 Platform,
Enterprise Edition (J2EE) applications as well as access data.
This page provides a starting point for finding information about application clients
and client applications. Application clients provide a framework on which application code
runs, so that your client applications can access information on the application server.
This page provides a starting point for finding information about service integration.
A service integration bus is a form of managed communication that supports service
integration through synchronous and asynchronous messaging. A bus consists of
interconnecting messaging engines that manage bus resources. The members of a
service integration bus are the application servers and clusters on which the
messaging engines are defined.
This page provides a starting point for finding information about data access, which includes:
Connection management for access to enterprise information systems (EIS), as defined by the
J2EE Connector Architecture (JCA) specification; Connection management for data sources, as
defined by the Java DataBase Connectivity (JDBC) specification; Other information for establishing
an application serving environment in which applications can access data.
This page provides a starting point for finding information about resources
that are used by applications that are deployed on a Java 2 Platform Enterprise
Edition (J2EE)-compliant application server.
This page provides a starting point for finding information about naming support.
Naming includes both server-side and client-side components. The server-side component
is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The
client-side component is a Java Naming and Directory Interface (JNDI) service provider.
JNDI is a core component in the Java 2 Platform, Enterprise Edition (J2EE) programming
model.
This page provides a starting point for finding information about the Object Request Broker (ORB). The product uses an ORB to manage communication between client applications and server applications as well as among product components. These Java 2 Platform Enterprise Edition (J2EE) standard services are relevant to the ORB:
Remote Method Invocation/Internet Inter-ORB Protocol (RMI/IIOP) and Java Interface
Definition Language (Java IDL).
This page provides a starting point for finding information about transaction (JTA) support.
Applications running on the server can use transactions to coordinate multiple updates to
resources as one unit of work such that all or none of the updates are made permanent.
Use this section as a starting point to investigate the WebSphere programming
model extensions for enhancing your application development and deployment..
This topic familiarizes you with the many Web sites containing technical information
for understanding and using your WebSphere Application Server product. A wealth of online
information is available to complement the product documentation.