Migrating product technologies
Learn how to migrate to technologies that are available in the newest release of WebSphere® Application Server.

For more information and to download the toolkit, see the Migration Toolkit on WASdev.
Subtopics
Migrating administrative scripts
You can migrate administrative scripts to Version 9.0 from Version 7.0 or later by using scripting and the wsadmin tool.Migrating Apache Derby databases
The migration tools migrate any Apache Derby instances to the new configuration, and they copy any Apache Derby instances that are stored in the previous release's WebSphere Application Server configuration tree to the new release's configuration tree. After you use the migration tools, verify the results of the database migration and manually migrate any database instances or copy any Derby database instances that the tools do not automatically migrate or copy.Migrating APIs and specifications
Migrating application programming interfaces (APIs) and specifications involves moving to the current Java level as well as to other technologies that WebSphere Application Server Version 9.0 supports. If your existing applications currently support different specification levels than are supported by this version of the product, you might have to update at least some aspects of the applications to comply with the new specifications.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 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 concurrency
This page provides a starting point for finding information about concurrency.Migrating data access resources
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 EJB applications
Find information about migrating enterprise beans.Migrating OSGi applications
This page provides a starting point for finding out how to migrate your OSGi application environment from previous versions of WebSphere Application Server Version to the current version, and how to use OSGi applications with different versions of the product.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 that you can manage as a unit, including:- Migrating web server configurations
You can migrate a web server so that it supports the latest version of WebSphere Application Server. Migrating web services
This page provides a starting point for finding information about web services.


File name: welcome_migrating_tech.html