| Oracle® Application Server Upgrade and Compatibility Guide 10g Release 3 (10.1.3.1.0) B31015-01 |
|
 Previous |
 Next |
| Oracle® Application Server Upgrade and Compatibility Guide 10g Release 3 (10.1.3.1.0) B31015-01 |
|
Previous |
Next |
This chapter describes the general instructions for upgrading from Oracle Application Server 10g (9.0.4) or 10g Release 2 (10.1.2).
|
See Also: Appendix A, "Step-By-Step Upgrade Examples" to review some specific examples of how to upgrade your environment to 10g Release 3 (10.1.3.1.0) |
This chapter contains the following sections:
Task 1: Determine a 10g Release 3 (10.1.3.1.0) Topology to Install and Configure
Task 2: Install and Configure Your New 10g Release 3 (10.1.3.1.0) Environment
Task 4: Redeploy Your Applications on 10g Release 3 (10.1.3.1.0)
Task 5: Verify Your Redeployed Applications on 10g Release 3 (10.1.3.1.0)
Task 6: Decommission the 10g (9.0.4) and 10g Release 2 (10.1.2) Oracle Homes
Before you begin the upgrade to 10g Release 3 (10.1.3.1.0), consider the following steps that will help you prepare for the upgrade:
Review your current Oracle Application Server environment.
You should have a thorough understanding of your current Oracle Application Server environment, including any requirements for clustering, load balancing, or state replication among the middle tier applications.
In addition, you should be aware of any required infrastructure components, such as Oracle Internet Directory or a OracleAS Metadata Repository.
|
See Also: Section 3.3, "Integrating 10g Release 3 (10.1.3.1.0) into Your Existing Environment" for information about integrating 10g Release 3 (10.1.3.1.0) into your existing Oracle Application Server environment |
Review the 10g Release 3 (10.1.3.1.0) recommended topologies, which are described in the Oracle Application Server Installation Guide.
Note in particular the recommended topologies that map to your current environment.
For example, if you are upgrading from 10g Release 2 (10.1.2), and you are deploying and managing your applications in an DCM-Managed OracleAS Cluster, then consider installing multiple 10g Release 3 (10.1.3.1.0) instances as part of a cluster topology.
You can then use 10g Release 3 (10.1.3.1.0) groups to deploy your applications to multiple OC4J instances in the cluster.
|
See Also: Appendix B, "Differences Between 10g Release 3 (10.1.3.1.0) and Previous Releases" for detailed information about the differences you can expect in the 10g Release 3 (10.1.3.1.0) environmentAppendix A, "Step-By-Step Upgrade Examples" for examples of how you can upgrade to a similar environment in 10g Release 3 (10.1.3.1.0) |
After you decide upon a 10g Release 3 (10.1.3.1.0) topology, you can begin the installation. Note the following guidelines when installing and configuring your new 10g Release 3 (10.1.3.1.0) environment:
Refer to the Oracle Application Server Installation Guide for specific instructions for installing each Oracle Application Server instance.
If you are installing multiple Oracle Application Server instances, use the cluster topology options within the installer to configure the members of the cluster--or you can use the Application Server Control Console to configure the cluster later. For more information, see "Configuring the Cluster Topology" in the Application Server Control online help.
Be sure to create any required additional OC4J instances and to organize your OC4J instances into groups before you continue with the upgrade process. The goal should be to configure your environment as much as possible before deploying your 10g (9.0.4) or 10g Release 2 (10.1.2) applications.
Consider taking advantage of the new features available with 10g Release 3 (10.1.3.1.0). For more information, see Appendix D, "Differences Between 10g Release 3 (10.1.3.1.0) and 10g Release 3 (10.1.3.0.0)".
After you install and configure your 10g Release 3 (10.1.3.1.0) environment, perform any OC4J server configuration tasks that are required by your applications or by your organization.
For example, refer to the following sections for more information about some common predeployment tasks:
Most J2EE applications that you develop and deploy will require a backend database or other data source. Before you redeploy your applications on 10g Release 3 (10.1.3.1.0), consider creating any required data sources using the Application Server Control Console. You can create a data source for one OC4J instance or for a group of OC4J instances.
Oracle Application Server 10g Release 3 (10.1.3.1.0) supports managed data sources, which rely upon JDBC connection pools, as well as native data sources.
For more information about defining data sources for 10g Release 3 (10.1.3.1.0), see the following:
"Managing Data Sources and JDBC Connection Pools" in the in the Application Server Control online help
"Data Sources" in the Oracle Containers for J2EE Services Guide
Before you deploy your applications that depend upon data sources, refer to Section C.3, "Data Source Considerations", which describes how Oracle Application Server support for data sources has changed since 10g (9.0.4) and 10g Release 2 (10.1.2).
If your deployed applications rely on any specific resource adapters, you can deploy the resource adapters to a single OC4J instance or to a group of OC4J instances. You can use the Application Server Control Console to deploy standalone resource adpaters or resource adapters that are embedded within an application.
For more information about defining data sources for 10g Release 3 (10.1.3.1.0), see the following:
"Overview of Managing Resource Adapters" in the in the Application Server Control online help
Oracle Containers for J2EE Resource Adapter Administrator's Guide
If made any specific changes to your default 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle Containers for J2EE server properties, consider using the Application Server Control Console to make the same changes to your 10g Release 3 (10.1.3.1.0) OC4J instances before you deploy your applications on 10g Release 3 (10.1.3.1.0).
For example, you can modify the number JVMs assigned for each OC4J instance, modify the port ranges for RMI, RMIS, and JMS, set the protocol to AJP or HTTP for default website, or set a specific set of Java options to process on OC4J startup.
For more information, see:
"Setting OC4J Server Properties" in the Application Server Control online help.
"OC4J Runtime Configuration" in the Oracle Containers for J2EE Configuration and Administration Guide
If you have made any site-specific configuration changes to the Oracle HTTP Server httpd.conf configuration file in the 10g Release 2 (10.1.2) Oracle home, apply those changes to the httpd.conf file in the 10g Release 3 (10.1.3.1.0) Oracle home.
As in 10g (9.0.4) and 10g Release 2 (10.1.2), the 10g Release 3 (10.1.3.1.0) Oracle HTTP Server is based on the on Apache 1.3 Web Server. As a result, you can copy any configuration changes (such as modifications to the httpd.conf file) directly to the httpd.conf file 10g Release 3 (10.1.3.1.0) Oracle home.
The following sections describe how to redeploy your 10g (9.0.4) and 10g Release 2 (10.1.2) applications on your new 10g Release 3 (10.1.3.1.0) environment:
Reviewing the Considerations When Redeploying Applications on 10g Release 3 (10.1.3.1.0)
Using Application Server Control to Redeploy Your Applications
After you have configured the 10g Release 3 (10.1.3.1.0) environment with any configuration settings required by your applications, review the applications themselves, as well as Appendix C, "Things to Consider When Redeploying 10g (9.0.4) and 10g Release 2 (10.1.2) Applications".
If your applications take advantage of any J2EE features or capabilities described in Appendix C, then you might have to make some changes to the application. These changes might be necessary to ensure that the application deploys successfully or to ensure that the all functionality of your application works as expected when deployed on 10g Release 3 (10.1.3.1.0).
After you have configured the new 10g Release 3 (10.1.3.1.0) environment appropriately for your application, and you have reviewed the conderations in Appendix C, you can then deploy your applications either to a single OC4J instance or to a group of OC4J instances.
To deploy an application to a single OC4J instance, navigate to the OC4J Home page and click Applications. From the OC4J Applications page, click Deploy and follow the instructions on the screen.
To deploy an application to an OC4J group, click the name of the group on the Cluster Topology page, and then click Applications on the Group page. From the Group Applications page, click Deploy and follow the instructions on the screen.
|
See Also: "Deploying an Application" in the Application Server Control online helpOracle Containers for J2EE Deployment Guide |
After you deploy the J2EE applications on 10g Release 3 (10.1.3.1.0), be sure to verify that all the features of your applications work as expected. In particular, test any features that were modified due to information available in Appendix C.
The applications you deploy on the 10g Release 3 (10.1.3.1.0) environment can be managed from the 10g Release 3 (10.1.3.1.0) Application Server Control Console. After you deploy your applications, log into the Application Server Control Console and verify that the applications are listed on the Cluster Topology page and that they are up and running. Drill down to the Application Home page to view general information about the applications, or to review performance and configuration information.
|
See Also: "Overview of Managing Applications" in the Application Server Control online help |
If you you were using state replication to maintain state across multiple instances of your applications in the 10g (9.0.4) or 10g Release 2 (10.1.2) environment, refer to "Overview of Application Clustering" in the Application Server Control online help for information about setting up a similar environment in 10g Release 3 (10.1.3.1.0).
Verification of an application also includes making sure that you can access and log into the application, that you can use all the features of the application, and that communications with data sources and other external resources work as expected.
The upgrade process leaves the 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle homes unchanged. Depending on the type of installation you have, and your future needs, you may elect to remove the source Oracle home, or to retain it for specific reasons.
You can continue running the 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle homes for as long as necessary. However, after you cutover to the new 10g Release 3 (10.1.3.1.0) environment and you are sure that you no longer need to support or run the 10g (9.0.4) or 10g Release 2 (10.1.2) environment, you can save disk space and other resources by decommissioning the 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle home.
The following sections provide more information about decommissioning an upgraded source Oracle home:
If there are application files or log files in the source Oracle home that are being referenced or used by your applications or by other Oracle homes, you should move them to another location before you decommission the source Oracle home, and, where necessary, change any references to the files to the new location.
If the 10g (9.0.4) or 10g Release 2 (10.1.2) middle tier instance is a member of an OracleAS Farm, be sure to remove the source instance from the farm before you deinstall the source Oracle home.
For example, after you upgrade an instance that was using an OracleAS Infrastructure, the source instance remains in the list of instances on the 10g (9.0.4) or 10g Release 2 (10.1.2) Application Server Control Console Farm page.
To remove the source instance from the farm and from the Farm page, use the following command in the 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle home:
On Windows systems:
SOURCE_ORACLE_HOME\dcm\bin\dcmctl leavefarm
On UNIX systems:
SOURCE_ORACLE_HOME/dcm/bin/dcmctl leavefarm
In this example, replace SOURCE_ORACLE_HOME with the complete path to the 10g (9.0.4) or 10g Release 2 (10.1.2) Oracle home, and replace OC4J_Instance with the name of the OC4J instance that you used to deploy the FAQApp application.
|
See Also: For more information about thedcmctl command-line utility and the Oracle Application Server Farm page, refer to the following resources in the 10g (9.0.4) or 10g Release 2 (10.1.2) documentation library:
The 10g (9.0.4) and 10g Release 2 (10.1.2) documentation libraries are available from the main documentation page the Oracle Technology Network: http://www.oracle.com/technology/documentation/ |
When you are certain that the upgrade was successful, you have all of the necessary backups, and have no plans to revert to the previous Oracle home, you may elect to remove the files from the source Oracle home. Use the Oracle Universal Installer to deinstall the instance.
|
See Also: The installation guide for your platform in the 10g (9.0.4) or 10g Release 2 (10.1.2) documentation library for instructions on deinstalling Oracle Application Server Oracle homes |
