Oracle9i Application Server Migrating from Oracle Internet Application Server 1.0.0 Release 1.0.2 for Sun SPARC Solaris Part Number A86723-01 |
|
OracleJSP and Apache JServ are application platforms. They allow developers to customize the configuration to suit their applications. Unlike some tools included with Oracle9i Application Server, migration of JSP and servlet applications can be more complicated. It requires working knowledge of JavaServer Pages, the servlet API, Apache Web Server configuration, HTTP, and the applications that are being migrated.
This chapter explains the process of migrating JSP applications from OracleJSP version 1.0 (1.0.0.6.1) to 1.1 in Oracle9i Application Server 1.0.2.
The following sections provide an overview of the differences between OracleJSP version 1.0 and version 1.1.
OracleJSP 1.1 is a Sun Microsystems JavaServer Pages 1.1 compliant implementation. It is different from OracleJSP 1.0 in the following ways:
<jsp:param>
in <jsp:include>
and <jsp:forward>
.
<jsp:include>
and <jsp:forward>
tags on Apache JServ so you can include and forward to a static HTML file, not just to a JSP file.
Enhancements in OracleJSP 1.1 are backward compatible. You can migrate your JSP applications from OracleJSP 1.0 to OracleJSP 1.1 without any code changes.
The Oracle9i Application Server 1.0.2 installation turns on the alias_translation
parameter explicitly in NEW_HOME/Apache/JServ/etc/zone.properties with the following line:
servlet.oracle.jsp.JspServlet.initArgs=alias_translation=true
If you put your JSP files under an aliased directory, please remember to retain this option.
For details of OracleJSP functionality, please refer to Oracle JavaServer Pages Developer's Guide and Reference in the Oracle9i Application Server Documentation Library.
In Oracle Internet Application Server 1.0.0, all OracleJSP files are installed under the directory:
In Oracle9i Application Server 1.0.2, most of the OracleJSP files are installed under the directory:
while the file ojsp.conf is under the NEW_HOME/Apache/jsp/conf directory.
Also, Oracle9i Application Server 1.0.2 uses JDK 1.2. Therefore, the tools.jar from JDK is now included in the CLASSPATH for JSP javac compilation. Additionally, the JDBC and SQLJ related zip files used in jserv.properties are also updated to the versions that correspond to JDK 1.2.
The following sections explain pre-migration steps. These instructions must be followed before beginning any migration work. Pre-migration consists of two steps:
Before you start any migration, you should first verify whether your new Oracle9i Application Server 1.0.2 installation is working correctly. To verify that OracleJSP 1.1 has been installed correctly, perform these steps:
Most of the samples should work without extra configuration changes or deployment steps, except for the CORBA and EJB samples. These two samples require you to first deploy the corresponding CORBA and EJB components.
The OracleJSP samples which work without extra configuration changes include:
|
Some samples require that you have a database up and running.
After you have verified that OracleJSP has been installed correctly, you are ready to back up your configuration files.
Before making any changes to the configuration files, you should back up all the configuration files in your new installation that you are going to change. Then, if you make a mistake during migration, you can restore the old configuration files and perform the migration steps again.
Typically, the following files are changed when you migrate your JSP and servlet applications after installing Oracle9i Application Server 1.0.2:
<NEW_HOME>/Apache/Apache/conf/httpd.conf
<NEW_HOME>/Apache/Jserv/etc/jserv.conf
<NEW_HOME>/Apache/JServ/etc/jserv.properties
<NEW_HOME>/Apache/JServ/etc/zone.properties
<NEW_HOME>/Apache/jsp/conf/ojsp.conf
Most of these configuration files of the old installation should be just under the directory with the same path under OLD_HOME. For example, jserv.conf should be in OLD_HOME/Apache/JServ/etc/jserv.conf, if the files have not been moved.
No environment migration tasks are necessary.
Anyone performing the OracleJSP 1.1 migration should have working knowledge of the applications and the JSP/servlet environment. First, you must identify what environment settings are made by the Oracle9i Application Server 1.0.2 installation and what environment settings are used for your applications.
The environment settings typically used include (but are not limited to) those listed in Table 6-1:
After backing up the configuration files, we recommend that you compare the old with the new configuration files using a tool like the diff command. Check the differences line-by-line to determine whether the difference is due to the new Oracle9i Application Server 1.0.2 installation or it is due to prior configuration customizations. If the difference in configuration settings is required for an application, then apply the changes to the new configuration.
Examples of changes in the new Oracle9i Application Server 1.0.2 installation include (but are not limited to):
Keep these changes in your new configuration because they provide faster performance and a richer set of functionality for your JSP applications.
Follow these steps as a general guideline for applying changes to the new configuration files:
For general troubleshooting, see the Oracle JavaServer Pages Developer's Guide and Reference and other Oracle reference manuals in the Oracle9i Application Server Documentation Library.
OracleJSP 1.1 provides a very good backward compatibility with 1.0. Therefore, you do not need to change your JSP source code to run it on OracleJSP 1.1.
However, the new version of OracleJSP uses Java 1.2. Since your existing applications use Java 1.1.8, you will need to recompile all JSP pages to fully utilize the benefits of Java 1.2.
OracleJSP 1.1 supports a JSP 1.1 standard runtime tag extension mechanism. If you are using JML tags from OracleJSP 1.0, then we suggest that you migrate tags in your JSP files from the OracleJSP 1.0 compile time mechanism to the new runtime version.
For more information, see the Oracle JavaServer Pages Developer's Guide and Reference in the Oracle9i Application Server Documentation Library.
OracleJSP 1.1 has an updated ojspc, the OracleJSP translator command line tool found in ORACLE_HOME/bin. It allows you to compile JSP files in the file system without a web server. In OracleJSP 1.1, this tool has a few new options, and the name of the option -includePath has been changed to -appRoot.
For more information, see the Oracle JavaServer Pages Developer's Guide and Reference in the Oracle9i Application Server Documentation Library.
|
![]() Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|