About This Guide

This Migrating and Redeploying Server Applications Guide describes how J2EE applications are migrated from earlier versions of the Sun ONE Application Server to Sun ONE Application Server 7 product line.

This manual is intended for system administrators, network administrators, application server administrators and web developers who have an interest in migration issues.

---

What You Should Know

Before you begin, you should already be familiar with the following topics:

HTML
Application Servers
Client/Server programming model
Internet and World Wide Web
Windows 2000 and/or Solaris™ operating systems
Java programming
Java APIs as defined in specifications for EJBs, Java Server Pages (JSP)
Java Database Connectivity (JDBC)
Structured database query languages such as SQL
Relational database concepts
Software development processes, including debugging and source code control

---

How This Guide is Organized

This guide is organized as follows:

Chapter 1, "Migration Considerations," describes the enhancements available in Sun ONE Application Server 7, Enterprise Edition.
Chapter 2, "Migrating to Sun ONE Application Server 7, Enterprise Edition Overview," describes the architecture of the Sun ONE Application Server 7 and the differences between J2EE standards and application components implemented with this version of the Sun ONE Application Server versus previous versions.
Chapter 3, "Migrating from Sun ONE Application Server 6.x to Sun ONE Application Server 7," describes considerations and strategies for migrating applications from Sun ONE Application Server 6.x to 7 Standard Edition and Enterprise Edition. There are also sample migration applications included that provide an end-to-end description of the migration process.
Chapter 4, "Installation, Administration, and Deployment," describes the difference between installing and administering Sun ONE Application Server 7, Enterprise Edition and Sun ONE Application Server 6.x Enterprise Edition. Also includes a brief description of the deployment topologies.
Chapter 5, "Migrating iBank Application - Walkthrough," describes the process for migrating the main components of a J2EE application to Sun ONE Application Server 7 Enterprise Edition. Uses iBank sample application as the example to demonstrate the steps.
Chapter 6, "Importing 6.5 Applications in Sun ONE Studio," describes the steps to import a Sun ONE Application Server 6.x application to Sun ONE Application Server 7 Enterprise Edition and deploy the same to the Application Server.
Appendix A, "iBank Application Specification," describes the modifications required to migration from EJB 1.1 specification to EJB 2.0.
Appendix B, "Migration Resources," describes the resources that helps in migrating the J2EE applications to Sun ONE Application Server 7, EE.
Appendix C, "Migrating from the Enterprise Java Beans 1.1 Specification to Enterprise Java Beans 2.0," describes the iBank specification that is used throughout this guide.

---

Using the Documentation

The Sun ONE Application Server manuals are available as online files in Portable Document Format (PDF) and Hypertext Markup Language (HTML) at:

http://docs.sun.com/db/prod/s1appsrv

The following table lists tasks and concepts described in the Sun ONE Application Server 7, Enterprise Edition manuals. The left column lists the tasks and concepts, and the right column lists the corresponding manuals.

Table 0-1  Sun ONE Application Server 7, Enterprise Edition Documentation Roadmap.

For information about	See the following
Late-breaking information about the software and the documentation.	Release Notes
Comprehensive, table-based summary of supported hardware, operating system, JDK, and JDBC/RDBMS.	Platform Summary
Sun ONE Application Server 7 overview, features available with each product edition.	Product Overview
Diagrams and descriptions of server architecture, benefits of the Sun ONE Application Server architectural approach.	Server Architecture
New enterprise, developer, and operational features of Sun ONE Application Server 7.	What’s New
How to get started with the Sun ONE Application Server 7 product. Includes new features, architectural overview, and sample application tutorial.	Getting Started Guide
Installing the Sun ONE Application Server software and its components, such as sample applications, the Administration interface, and the high-availability components. Instructions for implementing a basic high-availability configuration are included.	Installation Guide
Evaluating your system needs and enterprise to ensure that you deploy Sun ONE Application Server in a manner that best suits your site. General issues and concerns that you must be aware of when deploying an application server are also discussed.	System Deployment Guide
Best practices for HTTP session availability that application architects and developers can use.	Application Design Guidelines for Storing Session State
Creating and implementing Java™ 2 Platform, Enterprise Edition (J2EE™ platform) applications intended to run on the Sun ONE Application Server 7 that follow the open Java standards model for J2EE components such as servlets, Enterprise JavaBeans™ (EJBs™), and JavaServer Pages™ (JSPs™). Includes general information about application design, developer tools, security, assembly, deployment, debugging, and creating lifecycle modules. A comprehensive Sun ONE Application Server glossary is included.	Developer’s Guide
Creating and implementing J2EE web applications that follow the Java™ Servlet and JavaServer Pages (JSP) specifications on the Sun ONE Application Server 7. Discusses web application programming concepts and tasks, and provides sample code, implementation tips, and reference material. Topics include results caching, JSP precompilation, session management, security, deployment, SHTML, and CGI.	Developer’s Guide to Web Applications
Creating and implementing J2EE applications that follow the open Java standards model for enterprise beans on the Sun ONE Application Server 7. Discusses Enterprise JavaBeans (EJB) programming concepts and tasks, and provides sample code, implementation tips, and reference material. Topics include container-managed persistence, read-only beans, and the XML and DTD files associated with enterprise beans.	Developer’s Guide to Enterprise JavaBeans Technology
Creating Application Client Container (ACC) clients that access J2EE applications on the Sun ONE Application Server 7.	Developer’s Guide to Clients
Creating web services in the Sun ONE Application Server environment.	Developer’s Guide to Web Services
Java™ Database Connectivity (JDBC™), transaction, Java Naming and Directory Interface™ (JNDI), Java™ Message Service (JMS), and JavaMail™ APIs.	Developer’s Guide to J2EE Services and APIs
Creating custom NSAPI plug-ins.	Developer’s Guide to NSAPI
Information and instructions on the configuration, management, and deployment of the Sun ONE Application Server subsystems and components, from both the Administration interface and the command-line interface. Topics include cluster management, the high-availability database, load balancing, and session persistence. A comprehensive Sun ONE Application Server glossary is included.	Administrator’s Guide

---

Documentation Conventions

This section describes the types of conventions used throughout this guide:

General Conventions
Conventions Referring to Directories

General Conventions

The following general conventions are used in this guide:

File and directory paths are given in UNIX^® format (with forward slashes separating directory names).
URLs are given in the format:

http://server.domain/path/file.html

In these URLs, server is the server name where applications are run; domain is your Internet domain name; path is the server’s directory structure; and file is an individual filename. Italic items in URLs are placeholders.

Font conventions include:
The monospace font is used for sample code and code listings, API and language elements (such as function names and class names), file names, pathnames, directory names, and HTML tags.
Italic type is used for code variables.
Italic type is also used for book titles, emphasis, variables and placeholders, and words used in the literal sense.
Bold type is used as either a paragraph lead-in or to indicate words used in the literal sense.
Installation root directories for most platforms are indicated by install_dir in this document. Exceptions are noted in "Conventions Referring to Directories".

By default, the location of install_dir on most platforms is:

Solaris™ 8 non-package-based Evaluation installations:

user’s home directory/sun/appserver7

Solaris unbundled, non-evaluation installations:

/opt/SUNWappserver7

The directories, default_config_dir and install_config_dir are identical to install_dir. See "Conventions Referring to Directories", for exceptions and additional information.

Instance root directories are indicated by instance_dir in this document, which is an abbreviation for the following:

default_config_dir/domains/domain/instance

Conventions Referring to Directories

By default, when using the Solaris™ 8 and 9 installation, the application server files are spread across several root directories. These directories are described in this section.

For Solaris 8 and 9 installations, this guide uses the following document conventions to correspond to the various default installation directories provided:
install_dir refers to /opt/SUNWappserver7, which contains the static portion of the installation image. All utilities, executables, and libraries that make up the application server reside in this location.
default_config_dir refers to /var/opt/SUNWappserver7/domains which is the default location for any domains that are created.
install_config_dir refers to /etc/opt/SUNWappserver7/config, which contains installation-wide configuration information such as licenses and the master list of administrative domains configured for this installation.

---

Product Support

If you have general feedback on the product or documentation, please send this to appserver-feedback@sun.com.

If you have problems with your system, contact customer support using one of the following mechanisms:

The online support web site at:

http://www.sun.com/supportraining/

The telephone dispatch number associated with your maintenance contract

Please have the following information available prior to contacting support. This helps to ensure that our support staff can best assist you in resolving problems:

Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps

Previous      Contents      Index      Next

---

Copyright 2003 Sun Microsystems, Inc. All rights reserved.