Network Deployment (Distributed operating systems), v8.0 >
Learn about WebSphere applications
Use this section as a starting point to investigate the technologies used in and by applications that you deploy on the application server.
- Learn about WebSphere applications: Overview and new features
Use the Learn about WebSphere applications section as a starting point to study the programing model, encompassing the many parts used in and by various application types supported by the application server.
- ActivitySessions
This page provides a starting point for finding information about ActivitySessions, a WebSphere extension for reducing the complexity of commitment rules and limitations that are associated with one-phase commit resources.
- Application profiling
This page provides a starting point for finding information about application profiling, a WebSphere extension for defining strategies to dynamically control concurrency, prefetch, and read-ahead.
- Asynchronous beans
This page provides a starting point for finding information about asynchronous beans.
- Batch applications
This page provides a starting point for finding information about batch applications.
- Bean Validation
The Bean Validation API is introduced with the Java Enterprise Edition 6 platform as a standard mechanism to validate Enterprise JavaBeans in all layers of an application, including, presentation, business and data access. Before the Bean Validation specification, the JavaBeans were validated in each layer.
To prevent the reimplementation of validations at each layer, developers bundled validations directly into their classes or copied validation code, which was often cluttered. Having one implementation that is common to all layers of the application simplifies the developers work and saves time.
- Communications Enabled Applications
Communications Enabled Applications (CEA) is a functionality that provides the ability to add dynamic web communications to any application or business process. The product provides a suite of integrated telephony and collaborative web services that extends the interactivity of enterprise and web commerce applications. With the CEA capability, enterprise solution architects and developers can use a single core application to enable multiple modes of communication. Enterprise developers do not need to have extensive knowledge of telephony or Session Initiation Protocol (SIP) to implement CEA. The CEA capability delivers call control, notifications, and interactivity and provides the platform for more complex communications.
- 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.
- Data access resources
This page provides a starting point for finding information about data access. Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.
- Dynamic caching
This page provides a starting point for finding information about the dynamic cache service, which improves performance by caching the output of servlets, commands, web services, and JSP files.
- EJB applications
This page provides a starting point for finding information about enterprise beans.
- 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 Enterprise Edition (Java EE)-compliant application server. They include:
- Managed beans
This page provides a starting point for finding information about Managed beans.
- Messaging resources
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WAS.
- 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 ORB 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.
- ORB
This page provides a starting point for finding information about the 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).
- OSGi applications
This page provides a starting point for finding information about OSGi applications.
- 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.
- 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.
- Service integration
This page provides a starting point for finding information about service integration.
- Session Initiation Protocol (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 written to the JSR 116 specification.
- Spring applications
This page provides a starting point for finding information about how to develop Spring applications that can run successfully in a WAS environment.
- Transactions
This page provides a starting point for finding information about Java Transaction API (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.
- Work area
This page provides a starting point for finding information about work areas, a WebSphere extension for improving developer productivity.
- 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:
- Web services
This page provides a starting point for finding information about web services.
- XML applications
This page provides a starting point for finding information about XML applications.