Migration Tool for Sun Java System Application Server 8.2

The Migration Tool for Sun Java System Application Server 8.2 (hereafter called Migration Tool) migrates J2EE applications from other server platforms to Application Server 8.2.

The following source platforms are supported for Application Server 8.2:

• Sun ONE Application Server 6.x

• Sun Java System Application Server 7

• Sun Java System Application Server 8.0/8.1

• J2EE Reference Implementation Application Server (RI) 1.3, 1.4 Beta1

• WebLogic Application Server (WLS) 5.1, 6.0, 6.1, 8.1

• WebSphere Application Server (WAS) 4.0, 5.x

• Sun ONE Web Server 6.0

• JBoss Application Server 3.0

• TomCat Web Server 4.1

Migration Tool automates the migration of J2EE applications to Application Server 8.2, without much modification to the source code.

The key features of the tool are:

• Migration of application server-specific deployment descriptors

• Runtime support for selected custom JavaServer Pages (JSP) tags and proprietary APIs

• Conversion of selected configuration parameters with equivalent functionality in Application Server 8.2

• Automatic generation of Ant based scripts for building and deploying the migrated application to the target server, Application Server 8.2

• Generation of comprehensive migration reports after achieving migration

Download the Migration Tool from the following location:

http://java.sun.com/j2ee/tools/migration/index.html

For detailed information on how to install and use the tool, see online help.

The Migration Tool specifications and migration process change from time to time, so the sample migration using the tool is not included in this guide. The migration process of a sample application is discussed in the documentation for this tool.

Redeploying Migrated Applications

Most of the applications that are migrated automatically through the use of the available migration tools utilize the standard deployment tasks described in the Sun Java System Application Server 8.2 Administration Guide.

In some cases, the automatic migration is not able to migrate particular methods or syntaxes from the source application. When this occurs, a message displays describing the steps needed to complete the migration. Once these steps are completed, the administrator is able to deploy the application in the standard manner.