Use this section as a starting point to investigate the technologies used in and
by applications that you deploy on the application server.
- Web applications
- 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.
- Portlet applications
- This page provides a starting point for finding information about portlet applications, which are special reusable Java™ servlets that appear as defined regions on portal pages. Portlets provide access to many different applications, services, and Web content.
- SIP applications
- This page provides a starting point for finding information about SIP applications, which are Java programs that use at least one Session Initiation Protocol (SIP) servlet. SIP is used to establish, modify, and terminate multimedia IP sessions including IP telephony, presence, and instant messaging. "Presence" in this context refers to user status such as "Active," "Away," or "Do not disturb."
- EJB applications
-
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 Platform,
Enterprise Edition (Java EE) applications as well as access data.
- Client applications
- 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.
- Web services
- This page provides a starting point for finding information about Web services. Web services are self-contained, modular applications
that can be described, published, located, and invoked over a network. They implement a
services oriented architecture (SOA), which supports the connecting or sharing of resources
and data in a very flexible and standardized manner. Services are described and organized to
support their dynamic, automated discovery and reuse.
- SCA composites
-
This page provides a starting point for finding information about Service Component Architecture (SCA)
composites, which consist of components that implement business functions in the form of services.
You can develop components that use Web services and Enterprise JavaBeans™ (EJB) sessions
and define bindings that enable the components to run on product servers. You typically do not
deploy SCA composites directly onto a product server. To deploy SCA composites, you import SCA
composites as assets to the product repository and add the assets to business-level applications.
- Service integration
-
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.
- Data access resources
- 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
Java EE 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.
Service Data Objects (SDO) simplify the programmer experience with a universal abstraction
for messages and data, whether the programmer thinks of data in terms of XML documents or Java
objects. For programmers, SDOs eliminate the complexity of the underlying data access and message transport
technology choices.
- Messaging resources
- This page provides a starting point for finding information about messaging resources.
- Mail, URLs, and other Java EE resources
- This page provides a starting point for finding information about resources
that are used by applications that are deployed on a Java EE-compliant application server.
- Security
- This section discusses all aspects of security.
- Naming and directory
-
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 EE programming model.
- Object Request Broker (ORB)
-
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 EE standard services are relevant to the ORB:
Remote Method Invocation/Internet Inter-ORB Protocol (RMI/IIOP) and Java Interface
Definition Language (Java IDL).
- Transactions
- 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.
- WebSphere extensions
- This page provides a starting point to investigate the WebSphere® programming
model extensions for enhancing your application development and deployment.