Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Upgrade and Migration Guide

- Previous: Chapter 3 Upgrading an Application Server Installation
- Next: Chapter 5 Migrating from EJB 1.1 to EJB 2.0

# Chapter 4 Understanding Migration

This chapter addresses the following topics:

- J2EE Component Standards

- J2EE Application Components

- Migration and Deployment

# J2EE Component Standards

Sun Java System Application Server 8.1 August 22, 2005(hereafter called Application Server) is a J2EE v1.4-compliant server based on the component standards developed by the Java community. By contrast, Sun Java System Application Server 7 (Application Server 7) is a J2EE v1.3-compliant server and Sun ONE Application Server 6.x (Application Server 6.x) is a J2EE v1.2-compliant server. Between the three J2EE versions, there are considerable differences with the J2EE application component APIs.

The following table characterizes the differences between the component APIs used with the J2EE v1.4-compliant Sun Java System Application Server 8.1, the J2EE v1.3-compliant Sun ONE Application Server 7, and the J2EE v1.2-compliant Sun ONE Application Server 6.x.

Table 4–1 Application Server Version Comparison of APIs for J2EE Components

Component API | Sun ONE Application Server 6.x | Sun Java System Application Server 7 | Sun Java System Application Server 8.1
--- | --- | --- | ---
JDK | 1.2.2 | 1.4 | 1.4
Servlet | 2.2 | 2.3 | 2.4
JSP | 1.1 | 1.2 | 2.0
JDBC | 2.0 | 2.0 | 2.1, 3.0
EJB | 1.1 | 2.0 | 2.0
JNDI | 1.2 | 1.2 | 1.2.1
JMS | 1.0 | 1.1 | 1.1
JTA | 1.0 | 1.01 | 1.01

# J2EE Application Components

J2EE simplifies development of enterprise applications by basing them on standardized, modular components, providing a complete set of services to those components, and handling many details of application behavior automatically, without complex programming. J2EE v1.4 architecture includes several component APIs. Prominent J2EE components include:

- Client Application

- Web Application

- Enterprise JavaBean (EJB)

- Connector

- Enterprise Application Archive (EAR)

J2EE components are packaged separately and bundled into a J2EE application for deployment. Each component, its related files such as GIF and HTML files or server-side utility classes, and a deployment descriptor are assembled into a module and added to the J2EE application. A J2EE application is composed of one or more enterprise bean(s), Web, or application client component modules. The final enterprise solution can use one J2EE application or be made up of two or more J2EE applications, depending on design requirements.

A J2EE application and each of its modules has its own deployment descriptor. A deployment descriptor is an XML document with an .xml extension that describes a component’s deployment settings.

A J2EE application with all of its modules is delivered in an Enterprise Archive (EAR) file. An EAR file is a standard Java Archive (JAR) file with an .ear extension. The EAR file contains EJB JAR files, application client JAR files and/or Web Archive (WAR) files.

The migration process is concerned with moving J2EE application components, modules, and files. For more information on migrating various J2EE components, refer to Chapter 6, Migrating from Application Server 6.x/7.x to Application Server 8.1.

For more information on J2EE, see:

- J2EE 1.4 tutorial

- J2EE overview

- J2EE website

# Migration and Deployment

This section describes the need to migrate J2EE applications and the particular files that must be migrated. Following successful migration, a J2EE application is redeployed to the Application Server.

Redeployment is also described in this section.

The following topics are addressed:

- Why is Migration Necessary?

- What Needs to be Migrated

- What is Deployment of Migrated Applications?

## Why is Migration Necessary?

Although J2EE specifications broadly cover requirements for applications, they are nonetheless evolving standards. They either do not cover some aspects of applications or leave implementation details to the application providers.

This leads to different implementations of the application servers, also well as difference in the deployment of J2EE components on application servers. The array of available configuration and deployment tools for use with any particular application server product also contributes to the product implementation differences.

The evolutionary nature of the specifications itself presents challenges to application providers. Each of the component APIs are also evolving. This leads to a varying degree of conformance by products. In particular, an emerging product, such as the Application Server, has to contend with differences in J2EE application components, modules, and files deployed on other established application server platforms. Such differences require mappings between earlier implementation details of the J2EE standard, such as file naming conventions, messaging syntax, and so forth.

Moreover, product providers usually bundle additional features and services with their products. These features are available as custom JSP tags or proprietary Java API libraries. Unfortunately, using these proprietary features renders these applications non-portable.

## What Needs to be Migrated

For migration purposes, the J2EE application consists of the following file categories:

- Deployment descriptors (XML files)

- JSP source files that contain Proprietary APIs

- Java source files that contain Proprietary APIs

### Deployment descriptors (XML files)

Deployment is accomplished by specifying deployment descriptors (DDs) for standalone enterprise beans (EJB JAR files), front-end Web components (WAR files) and enterprise applications (EAR files). Deployment descriptors are used to resolve all external dependencies of the J2EE components/applications. The J2EE specification for DDs is common across all application server products. However, the specification leaves several deployment aspects of components pertaining to an application dependent on product-implementation.

#### JSP source files

J2EE specifies how to extend JSP by adding extra custom tags. Product vendors include some custom JSP extensions in their products, simplifying some tasks for developers. However, usage of these proprietary custom tags results in non-portability of JSP files. Additionally, JSP can invoke methods defined in other Java source files as well. The JSPs containing proprietary APIs needs to be rewritten before they can be migrated.

#### Java source files

The Java source files can be EJBs, servlets, or other helper classes. The EJBs and servlets can invoke standard J2EE services directly. They can also invoke methods defined in helper classes. Java source files are used to encode the business layer of applications, such as EJBs.Vendors bundle several services and proprietary Java API with their products. The use of proprietary Java APIs is a major source of non-portability in applications. Since J2EE is an evolving standard, different products can support different versions of J2EE component APIs. This is another aspect that migration addresses.

## What is Deployment of Migrated Applications?

Deployment refers to deploying a migrated application that was previously deployed on an earlier version of Sun’s Application Server, or any third party application server platforms.

Deploying a migrated application is described in Chapter 3, Assembling and Deploying Applications, in Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer’s Guide. However, when migration activities are performed with automated tools, such as the Migration Tool for Sun Java System Application Server 8.1 (for J2EE applications) or the Sun ONE Migration Toolbox (for Netscape Application Servers), there might be post-migration or pre-deployment tasks that are needed (and defined) prior to deploying the migrated application.

See Chapter 8, Migration Tools and Resources for more information about migration tools that are available.

- Previous: Chapter 3 Upgrading an Application Server Installation
- Next: Chapter 5 Migrating from EJB 1.1 to EJB 2.0

- © 2010, Oracle Corporation and/or its affiliates