This section covers all aspects of migration, coexistence, and interoperability. Migrating is copying the configuration from a previous release of this product into a new release. Coexisting is running a new release of WebSphere® Application Server on the same machine at the same time as you run an earlier release or running two installations of the same release of WebSphere Application Server on the same machine at the same time. Interoperating is exchanging data between two different systems, such as coexisting product installations.
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.
This page provides a starting point for finding information about asynchronous beans.
The Bean Validation API is introduced with the Java Enterprise Edition 6 platform as a standard mechanism to validate 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.
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.
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 JavaServer Pages (JSP) files.
This page provides a starting point for finding information about enterprise beans.
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere 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 Platform, Enterprise Edition (Java EE) programming model.
This page provides a starting point for finding out how to migrate from the OSGi Applications Feature Pack in WebSphere Application Server Version 7, and how to use OSGi applications with different versions of the product.
This page provides a starting point for finding information about the scheduler service, a WebSphere programming extension responsible for starting actions at specific times or intervals.
This page provides a starting point for finding information about service integration.
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.
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:
This page provides a starting point for finding information about web services.