Skip Headers
Oracle® Application Server Upgrade and Compatibility Guide
10
g
Release 3 (10.1.3)
Part No. B25585-01
Home
Solution Area
Index
Next
Contents
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Understanding the Upgrade to 10g Release 3 (10.1.3)
1.1
What Is Oracle Application Server 10g Release 3 (10.1.3)?
1.2
What Does It Mean to Upgrade to 10g Release 3 (10.1.3)?
1.3
Documentation Road Map for Previous Oracle Application Server Users
2
Step-By-Step Upgrade Examples
2.1
Upgrading FAQApp on a Single Oracle Application Server Instance
2.1.1
Starting Point for the FAQApp Upgrade
2.1.2
Overview of the FAQApp Upgrade Procedure
2.1.3
The FAQApp Upgrade Procedure
2.1.3.1
Step 1: Install 10g Release 3 (10.1.3)
2.1.3.2
Step 2: Apply Any Site-Specific Oracle HTTP Server Configuration Settings
2.1.3.3
Step 3: Configure the FAQApp Data Source in the 10g Release 3 (10.1.3) Instance
2.1.3.4
Step 4: Rebuild the FAQApp EAR File With Required JSP Library Archives
2.1.3.5
Step 5: Deploy the Modified FAQApp EAR File on 10g Release 3 (10.1.3)
2.1.3.6
Step 6: Test the FAQApp Sample Application on 10g Release 3 (10.1.3)
2.2
Upgrading FAQApp in a Clustered Environment
2.2.1
Starting Point for Upgrading FAQApp in a Clustered Environment
2.2.2
Overview of Upgrading FAQApp in a Clustered Environment
2.2.3
The FAQApp Upgrade Procedure in a Clustered Environment
2.2.3.1
Step 1: Install and Configure a 10g Release 3 (10.1.3) Cluster
2.2.3.2
Step 2: Apply Any Site-Specific Oracle HTTP Server Configuration Settings
2.2.3.3
Step 3: Create an FAQApp Group
2.2.3.4
Step 4: Configure the FAQApp Data Source for the Group
2.2.3.5
Step 5: Rebuild the FAQApp EAR File With Required JSP Library Archives
2.2.3.6
Step 6: Deploy FAQApp and Configure Application Clustering
2.2.3.7
Step 7: Test the FAQApp Sample Application on 10g Release 3 (10.1.3)
3
Redeploying J2EE Applications on 10g Release 3 (10.1.3)
3.1
Overview of Redeploying Applications on 10g Release 3 (10.1.3)
3.2
General Considerations
3.2.1
Classloading and Shared Library Support
3.2.2
New Location for JavaServer Pages (JSP) Standard Tag Libraries (JSTL)
3.2.3
Oracle JSP Markup Language (JML) Tag Library No Longer Supported
3.3
Data Source Considerations
3.3.1
New Features for Data Sources in 10g Release 3 (10.1.3)
3.3.2
Converting data-sources.xml to the New 10g Release 3 (10.1.3) Format
3.3.3
Using Oracle JDBC-OCI Drivers with 10g Release 3 (10.1.3)
3.4
Web Services Considerations
3.4.1
New Web Services Assembler (wsa.jar)
3.4.2
Assembling Web Services From Java Classes in 10g Release 3 (10.1.3)
3.4.3
Developing Database Web Services in 10g Release 3 (10.1.3)
3.5
Java Messaging Service (JMS) Considerations
3.5.1
Nomenclature Changes for 10g Release 3 (10.1.3) JMS Support
3.5.2
Using the JMS Connector Provided by 10g Release 3 (10.1.3)
3.5.3
Using the Application Server Control Console to Configure OEMS JMS
3.5.4
Changes to the jms.xml Configuration File
3.5.5
List of JAR Files Required for OEMS JMS Lookup
3.5.6
Database Version Support for OEMS JMS Database
3.6
Java Transaction API (JTA) Considerations
3.6.1
Using the New Middle-Tier Two-Phase Commit (2PC) Coordinator Instead of the Database Transaction Coordinator
3.6.2
New Support for Transaction Propagation
3.7
Remote Method Invocation (RMI) Considerations
3.7.1
Applying Compatibility Patches for 10g (9.0.4) and 10g Release 2 (10.1.2)
3.7.2
New System Property for Configuring ORMI Request Load Balancing
3.7.3
New Implementation of ORMI Tunnelling through HTTP
3.7.4
Configuring Secure Connections with RMIS and SSL
3.8
Java Naming and Directory Interface (JNDI) Considerations
3.8.1
New Package Names for Initial JNDI Context Factories
3.8.2
JNDI-Related MBeans Now Available in the Application Server Control Console
3.8.3
Performing Inter-Application JNDI Lookups
3.8.4
Browsing the JNDI Context in the Application Server Control Console
3.9
Security Considerations
3.9.1
List of Significant Changes in OC4J Security for 10g Release 3 (10.1.3)
3.9.2
Converting principals.xml to the New JAAS Security Model
3.9.3
Using Oracle Internet Directory as a Security Provider
3.10
Oracle TopLink and EJB Considerations
3.10.1
Configuring CMP Entity Beans to Use Oracle TopLink Persistence Manager
3.10.2
Upgrading TopLink Workbench Projects
4
Integrating 10g Release 3 (10.1.3) into Your Existing Environment
4.1
Installing 10g Release 3 (10.1.3) Middle Tiers in an Existing Oracle Application Server Environment
4.2
Using Existing OracleAS Infrastructure Components
4.3
Using Existing Oracle HTTP Server Instances
4.4
Using an Existing OracleAS Web Cache Installation As a Reverse Proxy
5
Differences Between 10g Release 3 (10.1.3) and Previous Releases
5.1
Using the Cluster Topology Instead of an OracleAS Farm
5.2
Using Groups Instead of OracleAS Clusters
5.2.1
How Are Groups Similar to OracleAS Clusters?
5.2.2
How Are Groups Different from OracleAS Clusters?
5.2.2.1
Configuration Changes Are Not Propogated Automatically to Other Members of the Group
5.2.2.2
Groups Are Not Always Identical
5.2.2.3
Groups Are Created Automatically Based on the Instance Name
5.3
Using Application Clustering for State Replication
5.3.1
Clustering Features and Concepts That Are No Longer Supported
5.3.2
About 10g Release 3 (10.1.3) Application Clustering
5.4
Creating New OC4J Instances With the createinstance Command
5.5
Using the admin_client.jar Utility to Manage OC4J Instances and Clusters
5.6
Summary of Equivalent Features in 10g Release 3 (10.1.3)
6
10g Release 3 (10.1.3) Version Compatibility
Index
