As we continuously deliver Liberty, the Liberty zero migration vision is alive and well. We strive to never break an existing application or configuration by introducing a behavior change.

But sometimes you need to upgrade an application with new server features or move to a different edition. And moving between other servers, like WebSphere Application Server traditional or non-IBM application servers, can require migration. The last thing you want is to be caught by surprise by unanticipated migration difficulties. This is where the WebSphere Application Server Migration Toolkit can help. With static analysis we can scan your application source or application binaries to find those gotchas that can occur between different application servers, different Java SE versions, and between different Java EE levels.

The WebSphere migration toolkit provides a rich set of tools that help you migrate between versions of traditional WebSphere, to Liberty, to cloud platforms such as Liberty for Java on IBM Bluemix Instant Runtimes, and from non-IBM application servers. We do this by scanning your source, binaries, and configurations.

The migration toolkit is updated to help you migrate to traditional WebSphere Application Server V9.0. The traditional V9.0 server is Java EE 7 compliant and shares the same technology updates that were previously only available on Liberty. Both the binary and source scanners will help guide you through differences in the Java EE 7 platform as well as inform you of application-related deprecations and removals. Whether you are using WebSphere V9.0 on-premises or on Bluemix, the migration toolkit can help you get there.

Evaluation Reporting
Configuration Scanning

Source Scanning

Our WebSphere Application Server Migration Toolkit provides an Eclipse-based migration experience. With one easy installation, you can access the following migration tools:

  • Cloud Migration Tool
  • WebSphere Version to Version Application Migration Tool
  • Apache Tomcat to WebSphere Application Migration Tool
  • JBoss to WebSphere Application Migration Tool
  • Oracle to WebSphere Application Migration Tool
  • WebLogic to WebSphere Application Migration Tool
  • Apache Tomcat to Liberty Profile Configuration Migration Tool

These application migration tools are Eclipse features that you install into an existing Eclipse or Rational IDE where you develop your source code. Once installed, the tools can scan your applications for migration issues that you might have to address so that your application can run on the targeted version of WebSphere Application Server. Where possible, the Eclipse-based tools provide quick fixes to programmatically make application changes for you.

Moving to the cloud

When moving an application to a cloud environment, the Cloud Migration Tool has support for the following cloud targets: Bluemix Instant Runtimes, third-party PaaS environments, Docker (IBM Containers), and WebSphere on Cloud (virtual machines). The tools have a set of rules that help you analyze the impact of moving an application to the cloud based on the connections the application uses such as:

  • Databases
  • Enterprise information systems (EIS)
  • Java EE security
  • JavaMail server
  • Java Message Service (JMS)
  • Message-Driven Beans (MDB)
  • Remote EJB lookups
  • Remote EJB providers
  • Remote web services
  • Third-party security
  • Vendor specific messaging

Evaluating the application’s use of connected services helps you consider latency issues, data movement, and the use of cloud services that might be relevant to a cloud migration.

When moving an application to Liberty for Java on IBM Bluemix or to a non-IBM Cloud PaaS environment, the Cloud Migration Tool offers additional advice, suggestions, and best practices to ensure the application will run correctly. For example, it will warn about using the Java File I/O API for storing persistent information on the local file system or suggest using the IBM Bluemix SessionCache service for storing HTTP session data. When migrating an application to a cloud environment running Liberty, we recommend you get the application running on a standalone Liberty server first, then move it to the cloud.

Moving between WebSphere versions

The WebSphere Version to Version Application Migration Tool scans your application source code and highlights Java EE programming model and WebSphere API differences between traditional WebSphere versions (Version 5.1 or later to Version 9.0) and to Liberty. It also informs you about any implementation differences that could affect your applications.

Moving from a non-IBM app server

You can install the migration tools for non-IBM application servers from the WebSphere Application Server Migration Toolkit to help you migrate applications to traditional WebSphere or Liberty from:

  • Apache Tomcat Server
  • Red Hat JBoss Application Server
  • Oracle Application Server
  • Oracle WebLogic Server

Moving between Java versions

The tools include Java migration support for moving up from an earlier version of Java. Our Java 8 migration rules allow you to check your application for Java 8 readiness as it scans for known compatibility issues. The Eclipse interface for Software Analysis Results and Help is shown below.


WAMT Analysis

WebSphere Application Server V9.0 only supports Java SE 8, so use the toolkit to help you understand the differences.

Binary scanning

The Migration Toolkit for Application Binaries is our command-line tool that allows you to scan your application binaries quickly and easily without source code. It contains many of the same rules as the Eclipse-based migration toolkit and provides application technology evaluation, inventory details, as well as detailed migration analysis. It helps you with application migrations between versions of traditional WebSphere (Version 6.1 and later), from traditional WebSphere to Liberty, and to cloud environments such as Liberty for Java on IBM Bluemix.

There are three easy actions, –evaluate, –inventory, and –analyze, to produce the information you need. You can create the reports in HTML by default or switch the format to text or JSON. The JSON files can be imported into a document database, such as MongoDB, for easy analysis.

All you need to start evaluating applications is the installed command-line tool and your application archives, such as EAR, JAR, WAR, or class files. If you have hundreds of applications, you can write a simple script to evaluate each and save the output to separate reports. For the administrator, planner, or developer not using Eclipse, this is a great addition to the toolkit!

Evaluation Report

Both the Eclipse-based migration tools and the binary scanner can examine your application and generate the Application Evaluation Report, which shows which editions of WebSphere Application Server are best suited to run the application. The report provides a list of Java EE programming models that are used by the application, and it indicates whether the application can be supported by traditional WebSphere or Liberty. The report has been updated to indicate the latest levels of Java EE 7 support available on traditional WebSphere and Liberty.



Application Evaluation Report

Inventory Report

The binary scanner has a new inventory report that helps you examine what’s in your application including the number of modules and the technologies in those modules. It also gives you a view of all the utility JAR files in the application that tend to accumulate over time.



Application Inventory Report

Detailed Reports using the binary scanner

The evaluation report primarily scans for Java EE technologies that the application uses. This information gives you a high level view of the platforms that can support your application’s technologies. Use the binary scanner’s detailed migration report to dig deeper to understand the nitty-gritty details of the migration. The detailed report helps with migration issues like deprecated or removed APIs, Java SE version differences, and Java EE behavior differences.


When migrating to a cloud environment, the Connectivity Rules Summary quickly shows your application dependencies on resources such as databases, messaging systems, security services, etc. All connected services need to be evaluated when moving to the cloud for connectivity and latency considerations. This summary is only available in the binary scanner detailed analysis report.

Configuration scanning

Version-to-Version Configuration migration

The traditional WebSphere Application Server WASPreUpgrade, WASPostUpgrade, and createRemoteMigrJar commands and wizards have been updated for Version 9.0 with enhancements to help you move your traditional configuration forward. Visit the IBM Knowledge Center to learn more about Migrating the product. There is also a new clone migration option that allows you to move your configuration without system outages.

Traditional WebSphere to Liberty or third-party configuration migration

The Apache Tomcat to Liberty Profile Configuration Migration Tool helps you move server configuration and application configuration to Liberty by automatically migrating portions of the configuration. The tool supports:

  • Migrating from Apache Tomcat 6.0 or 7.0
  • Migrating to Liberty
  • Migrating Apache Tomcat context, server, and web XML information contained in the server
  • Migrating Apache Tomcat context and web XML information contained in the application

Use the WebSphere Configuration Migration Tool to migrate server configuration from JBoss or WebLogic to traditional WebSphere or Liberty. It also assists in migrating resource configuration from traditional WebSphere to Liberty. When migrating to traditional WebSphere, the tool generates scripts used to manage the configuration. When migrating to Liberty, the tool generates a server.xml configuration file.


wcmtLiberty

 

Check out our downloads, videos, and additional information, and let us know how we can help.

Ask a question on Stack Overflow

2 Comments on "Migration"

  1. […] the October 2015 beta, all of the migration toolkits have been refreshed and combined into fewer […]

Join The Discussion

Your email address will not be published. Required fields are marked *