WAS v8.5 >Migrate, coexist, and interoperate
This section covers all aspects of migration, coexistence, and interoperability. Migrating is copying the configuration from a previous release WAS v8.5 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 WAS on the same machine at the same time. Interoperating is exchanging data between two different systems, such as coexisting product installations.
This section focuses on migrating to a new release of the WAS full profile. If we are using the Liberty profile, see Migrating applications to the Liberty profile.
Subtopics
- Liberty profile: migrating applications
This page provides a starting point for migrating applications from the WAS full profile to the Liberty profile.- Migrating 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.- Migrating Asynchronous beans
This page provides a starting point for finding information about asynchronous beans.- Migrating applications that use the Bean Validation API
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.- Migrating 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.- Migrating Dynamic caching
The dynamic cache service, which improves performance by caching the output of servlets, commands, web services, and JSP (JSP) files.- Migrating EJB applications
This page provides a starting point for finding information about enterprise beans.- Migrating 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.- Migrating OSGi applications
This page provides a starting point for finding out how to migrate your OSGi application environment from previous versions of WAS Version to the current version, and how to use OSGi applications with different versions of the product.- Migrating Scheduler service
The scheduler service, a WebSphere programming extension responsible for starting actions at specific times or intervals.- Migrating Service integration
This page provides a starting point for finding information about service integration.- Migrating 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.- Migrating web applications
This page provides a starting point for finding information about web applications, which are comprised of one or more related files managed as a unit, including:- Migrating web services
This page provides a starting point for finding information about web services.
Related information:
WebSphere product lifecycle dates