WebSphere applications features



Search Tips   |   Advanced Search



WAS ND v7.0 has the following aspects...


Single appserver installation

See also: Product architecture.


Java EE application components

Web apps run in the Web container and are comprised of one or more related servlets, JSP and HTML files managed as a unit.

Each appserver runtime has one logical Web container, which can be modified, but not created or removed.

Each Web container provides the following.

EJB applications run in the EJB container, which provides all of the runtime services needed to deploy and manage enterprise beans. It is a server process that handles requests for both session and entity beans.

Enterprise beans are Java components that typically implement the business logic of Java EE applications, as well as accessing data. The enterprise beans, packaged in EJB modules, installed in an appserver do not communicate directly with the server. Instead, the EJB container is an interface between EJB components and the appserver. Together, the container and the server provide the enterprise bean runtime environment.

The container provides many low-level services, including threading and transaction support. From an admin perspective, the container handles data access for the contained beans. A single container can host more than one EJB JAR file.


Client applications and other types of clients

In a client-server environment, clients communicate with applications running on the server. Client applications or application clients generally refers to clients implemented according to a particular set of Java specifications, and which run in the client container of a Java EE-compliant appserver.

Other clients in the WAS environment...

Web clients Web apps
Web services clients Clients of Web services programs
Administrative clients Clients of WAS ND systems administration


Web services

The diagram shows the Web services engine, part of the Web services support in the appserver runtime. Web services are self-contained, modular applications that can be described, published, located, and invoked over a network. They implement a service-oriented architecture (SOA), which supports the connecting or sharing of resources and data in a flexible and standardized manner. Services are described and organized to support their dynamic, automated discovery and reuse.

WAS ND v7.0 acts as both a Web services provider and as a requestor. As a provider, it hosts Web services that are published for use by clients. As a requester, it hosts applications that invoke Web services from other locations. The diagram shows the Web services engine in this capacity, contacting a Web services provider or gateway.


Data access, messaging, and Java EE resources




Additional services for use by applications


WebSphere extensions

WebSphere programming model extensions are the model benefits you gain by purchasing this product. They represent leading edge technology to enhance application capability and performance, and make programming and deployment faster and more productive.

In addition, the applications can use the Eclipse extension framework. Your applications are extensible as soon as you define an extension point and provide the extension processing code for the extensible area of the application. We can also plug an application into another extensible application by defining an extension that adheres to the target extension point requirements.

The extension point can find the newly added extension dynamically and the new function is seamlessly integrated in the existing application. It works on a cross Java EE module basis. The application extension registry uses the Eclipse plug-in descriptor format and APIs as the standard extensibility mechanism for WebSphere applications. Developers who build WebSphere application modules can use WAS extensions to implement Eclipse tools and to provide plug-in modules to contribute functionality such as actions, tasks, menu items, and links at predefined extension points in the WebSphere application.

The various WebSphere programming model extensions, and the corresponding application services that support them in the appserver runtime, can be considered in three groups...


Extensions pertaining to the Business Object Model

Business object model extensions operate with business objects, such as EJB applications.


Extensions pertaining to the Business Process Model

Business process model extensions provide process, workflow functionality, and services for the appserver. Use them in conjunction with business integration capabilities.


Extensions for creating next generation applications

WebSphere programming extensions......


Specifications and API documentation
Web apps
Learn about Web apps
Introduction: Web apps
Introduction: Portlet applications
Learn about portlet applications
Introduction: SIP applications
Learn about SIP applications
EJB applications
Introduction: EJB applications
Learn about EJB applications
Client modules
Introduction: Client applications
Learn about client applications
Web services
Introduction: Web services
Learn about Web services
Data access resources
Introduction: Data access resources
Learn about data access resources
Messaging resources
Introduction: Messaging resources
Messaging: Links
Mail, URLs, and other J2EE resources
Introduction: Mail, URLs, and other Java EE resources
Learn about mail, URLs, and other Java EE resources
Introduction: Security
Introduction: Naming and directory
Learn about naming and directory
Learn about Object Request Brokers (ORB)
Introduction: Object Request Broker
Introduction: Transactions
Learn about transactions


Related concepts

Object Request Brokers
Learn about WebSphere programming extensions