Sun ONE Application Server 7, Enterprise Edition Migrating and Redeploying Server Applications Guide |
Appendix B
Migration ResourcesThis appendix briefly describes the resources that helps in the migration of J2EE application components to Sun ONE Application Server 7 Enterprise Edition.
This appendix contains the following topics:
Migrating Applications From Competitive Application ServersApplications built with J2EE technology can be moved from one application server to another without much modification to the source code. This section gives information about the resources that helps you migrate applications built on competitive application servers to Sun ONE Application Server 7 Enterprise Edition.
Migrating from BEA WebLogic to Sun ONE App Server 7
To migrate your applications built on J2EE technology from BEA Web Logic Application Server 5.1 or 6.x to Sun ONE Application Server 7, refer to the guides located at the following URL:
http://www.sun.com/migration/ResourceGuides_BEA5.1wpr1a.pdf
http://www.sun.com/migration/ResourceGuides_BEA6.1r1awp.pdf
These guides provide an overview of the migration strategy, migration process, migration considerations and also the actual migration of a sample application.
Migrating from IBM WebSphere to Sun ONE App Server 7
To migrate your applications built on J2EE technology from IBM Web Sphere Application Server to Sun ONE Application Server 7, refer to the instructions provided in the guide at the following URL:
http://www.sun.com/migration/ResourceGuides_WAS4.0r1wp.pdf
This guide provides an understanding of the target and source application server in terms of architecture and features. This guide also discusses about the migration issues and actual migration of a sample application.
Migration ToolsSun ONE Application Server supports various migration tools that automates the migration of various J2EE application components. This section provides resource information on the supported tools.
Sun ONE Studio Enterprise Edition for Java, Release 4.1
The Sun ONE Studio for Java Development Environment is used to migrate various components of J2EE application to Sun ONE Application Server 7.
For information on how to use the tool to migrate your applications, see Chapter 6, "Importing 6.5 Applications in Sun ONE Studio."
For general information about the tool and its features, see Sun ONE Studio documentation at the following URL:
http://docs.sun.com/db/coll/790.3
Sun ONE Migration Tool for Application Server
Sun ONE Migration Tool 3.x/4.x for Application Servers automates the migration of J2EE applications to Sun ONE Application Server 7, 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 PagesTM (JSPTM) tags and proprietary APIs
- Conversion of selected configuration parameters with equivalent functionality in Sun ONE Application Server
- Automatic generation of Ant based scripts for building and deploying the migrated application to the target Application Server
- Generation of comprehensive migration reports after achieving migration
You can download the Sun ONE Migration Tool for Application Server from the following location:
http://www.sun.com/migration/sunonetools.html#1
For detailed information on how to install and use the tool, consult its online help.
Sun ONE Migration Toolbox for Applogic and NetDynamics
Sun ONE Migration Toolbox is used to migrate applications built on NetDynamics or Kiva/NAS platforms to Sun ONE Application Server or any J2EE compatible containers. The main interface for the Sun ONE Migration Toolbox is the Toolbox application. This application can be invoked by running the %MIGTBX_HOME%/bin/toolbox.bat script (provided the setenv.bat file has been customized appropriately, see README.txt for more information).
The following source platforms are supported for migration using the Toolbox:
Although it is expected that the application can be run on other Windows platforms (Windows 95/98/Me), these platforms have not been tested and may require additional configuration beyond that is specified in the Sun ONE Migration Toolbox installation documentation.
The Toolbox requires the JDK 1.2.2 (JDK 1.3.1 has been tested) to run successfully.
Sun ONE Connector Builder
The Connector Builder is a set of tools, components, and libraries that allows you to build resource adapters compliant with the J2EE Connector Architecture 1.0 for Enterprise Information Systems (EIS) and legacy applications. The resource adapters built using Connector Builder provide J2EE applications an easy-to-use and standards-based way to access these external systems. The generated resource adapters are accessed using the Common Client Interface (CCI) API as described in the J2EE CA. Optionally, Connector Builder generated resource adapters can also be accessed using Simple Object Access Protocol (SOAP) services thus providing a web services solution to application integration.
You can download the trail version of the tool from the following location:
http://wwws.sun.com/software/products/connector_builder/home_connector_builder.html
For information about how to use the tool, see the Connector Builder tool documentation at the following URL:
http://docs.sun.com/db/coll/s1.conbldr
Native Connector Toolkit
This topic covers the details of how to build the Resource Adapter using Connector Builder for your legacy C/C++ API.
Connector Builder requires the API to be in Java, however, most of the legacy EISs or Applications only provide a C/C++ API. This section describes how you can build the Resource Adapter using Connector Builder for those legacy APIs.
You need to first create a Java (JNI) wrapper to the C/C++ API. Connector Builder recommends using the Native Connector Toolkit (NCT) tool available from the IDE. NCT is an easy to use tool that quickly generates Java wrappers for C/C++ applications using JNI. The output Java wrapper files generated by the NCT Tool become the input while defining the EIS API in the Connector Builder.
More information on the Native Connector Toolkit is available from the Toolkit’s help, and Connector Builder tool documentation at the following URL:
http://docs.sun.com/db/coll/s1.conbldr
J2EE Application Verification Kit
The Java Application Verification Kit (AVK) for the Enterprise helps you build and test your applications for correct use of J2EE APIs and migrate to other J2EE compatible application servers using specific guidelines and rules.
You can download the Java Application Verification Kit (AVK) from the following location:
http://java.sun.com/j2ee/verified/
ReferencesThis section gives you references to the Migration Documents of Sun ONE Application Server 6.x.
Migrating to Sun ONE Application Server 6.0
For information about migrating your KIVA/NAS/NetDynamics applications to Sun ONE Application Server 6.0, see the Sun ONE Application Server Migration Guide at the following URL:
http://docs.sun.com/db/doc/816-5780-10
Migrating to Sun ONE Application Server 6.5
For information about migrating your KIVA/NAS/NetDynamics applications to Sun ONE Application Server 6.5, see the Sun ONE Application Server 6.5 Migration Guide at the following URL:
http://docs.sun.com/db/doc/816-5793-11
Migrating to Sun ONE Application Server 7
For information about migrating your KIVA/NAS/NetDynamics applications to Sun ONE Application Server 7, see Sun ONE Application Server 7 Migrating and Redeploying Server Applications Guide at the following URL:
http://docs.sun.com/db/doc/817-2158-10
Redeploying Migrated ApplicationsMost of the applications that are migrated automatically through the use of the available migration tools will utilize the standard deployment tasks described in the Sun ONE Application Server Administrator’s Guide.
In some cases, the automatic migration will not be able to migrate particular methods or syntaxes from the source application. When this occurs in the case of the Sun ONE Migration Tool for Application Servers, you are notified of the steps that will be needed to complete the migration. Once you complete the post-migration manual steps, you will be able to deploy the application in the standard manner described in the Sun ONE Application Server Administrator’s Guide.