Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

1 Summary of the Java EE Upgrade Process

• 1.1 Flow Chart of the Java EE Upgrade Process
• 1.2 Table Describing the Steps in the Java EE Upgrade Process

Part I Preparing for a Java EE Upgrade

2 Supported Starting Point for Java EE Upgrade

3 Introduction to Oracle WebLogic Server for OC4J Users

• 3.1 Key Oracle WebLogic Server Concepts for OC4J Users
  • 3.1.1 Comparing the OC4J and Oracle WebLogic Server Architectures
    • 3.1.1.1 Standalone OC4J and Standalone Oracle WebLogic Server
    • 3.1.1.2 OC4J and Oracle WebLogic Server Integrated With a Web Server
    • 3.1.1.3 OC4J and Oracle WebLogic Server Clustering Features
  • 3.1.2 Comparing OC4J and Oracle WebLogic Server Directory Structures
  • 3.1.3 Understanding Oracle WebLogic Server Domains for OC4J Users
    • 3.1.3.1 Basic Content and Organization of a Domain
    • 3.1.3.2 Additional Facts About Oracle WebLogic Server Domains
      • 3.1.3.2.1 A WebLogic Server Installation Can be Used to Configure Multiple Domains
      • 3.1.3.2.2 A WebLogic Server Instance Is Always Associated With a Single Java Virtual Machine Process
      • 3.1.3.2.3 A WebLogic Server Instance Processes All Application Requests on the Same Port by Default
      • 3.1.3.2.4 A WebLogic Server Instance Is Always Configured With an HTTP Listener and Does Not Support AJP
• 3.2 Oracle WebLogic Server Installation and Configuration Tools for OC4J Users
• 3.3 Oracle WebLogic Server Administration Tools for OC4J Users
  • 3.3.1 Comparison of OC4J and Oracle WebLogic Server Administration Tools
  • 3.3.2 Typical Oracle WebLogic Server Administration Tasks for OC4J Users
    • 3.3.2.1 Starting and Stopping Servers
    • 3.3.2.2 Performing Diagnostics on a Domain
    • 3.3.2.3 Viewing Log Files for a Domain
    • 3.3.2.4 Configuring and Tuning Thread Pools
• 3.4 Standards Support for OC4J and Oracle WebLogic Server

Part II Upgrading Your Java EE Applications and Environment

4 Upgrading Your Java EE Applications

• 4.1 Task 1: Verify that Your Application Deploys and Works Successfully on OC4J
• 4.2 Task 2: Select Your Development Tools
  • 4.2.1 General Guidelines for Selecting Your Development Tools
  • 4.2.2 Using the SmartUpgrade Oracle JDeveloper Extension and Command-Line Tool
• 4.3 Task 3: Verify That Your Application Supports Java Development Kit (JDK) 6
• 4.4 Task 4: Upgrade the Application Deployment Descriptors
  • 4.4.1 Comparison of OC4J and Oracle WebLogic Server Deployment Descriptors
  • 4.4.2 Guidelines and Resources for Upgrading Deployment Descriptors for Oracle WebLogic Server
  • 4.4.3 About Security Elements in Deployment Descriptor Files
  • 4.4.4 Upgrading Deployment Plans
• 4.5 Task 5: Review Oracle WebLogic Server API Support
  • 4.5.1 APIs Available With the Java Required Files (JRF) Domain Template
  • 4.5.2 Other Oracle WebLogic Server API Requirements
• 4.6 Task 6: Upgrade the Application Web Services
  • 4.6.1 General Guidelines for Upgrading to Oracle WebLogic Server JAX-RPC and JAX-WS Web Services
  • 4.6.2 Generating Oracle WebLogic Server Web Services From an OC4J WSDL
  • 4.6.3 Web Services Specifications Supported by OC4J and Oracle WebLogic Server

5 Upgrading Your Java EE Environment

• 5.1 Task 1: Install and Configure an Oracle WebLogic Server Development Domain
  • 5.1.1 Differences Between a Development Environment and a Test or Production Environment
  • 5.1.2 Installing and Configuring a Development Domain with Oracle JDeveloper
  • 5.1.3 Installing and Configuring a Development Domain with Oracle SOA Suite, WebCenter, or Application Developer
    • 5.1.3.1 Advantages of Installing an Oracle SOA Suite, WebCenter, or Application Developer Development Environment
    • 5.1.3.2 Selecting an Oracle Fusion Middleware Software Suite
    • 5.1.3.3 Steps Required to Install and Configure an Oracle SOA Suite, WebCenter, or Application Developer Domain
  • 5.1.4 Using the Java Required Files (JRF) Domain Template
    • 5.1.4.1 Creating a New Domain With the JRF Template
    • 5.1.4.2 Extending an Existing Domain With the JRF Template
• 5.2 Task 2: Verify the New Oracle Fusion Middleware 11g Environment
• 5.3 Task 3: Configure Oracle WebLogic Server Resources to Support Your Applications
  • 5.3.1 Configuring JDBC Data Sources on Oracle WebLogic Server
    • 5.3.1.1 General Information About Defining Data Sources for OC4J and Oracle WebLogic Server
    • 5.3.1.2 Upgrading Application-Level OC4J Data Sources
    • 5.3.1.3 Upgrading Instance and Group-Level OC4J Data Sources
    • 5.3.1.4 JDBC Connection Pools and Managed Data Sources in OC4J and Oracle WebLogic Server
  • 5.3.2 Configuring OC4J JMS Resources on Oracle WebLogic Server
    • 5.3.2.1 Overview of JMS Support in OC4J and Oracle WebLogic Server
    • 5.3.2.2 Creating and Managing JMS Resources in OC4J and Oracle WebLogic Server
  • 5.3.3 Configuring OC4J Remote JMS Resources on Oracle WebLogic Server
  • 5.3.4 Using Shared Libraries and Class Loading on Oracle WebLogic Server
  • 5.3.5 Configuring Startup and Shutdown Classes
  • 5.3.6 Configuring Security on Oracle WebLogic Server
  • 5.3.7 Configuring Logging on Oracle WebLogic Server
• 5.4 Task 4: Redeploy the Application on Oracle WebLogic Server
• 5.5 Task 5: Verify the Redeployed Applications

6 Upgrading Application Clients

• 6.1 Impact of Upgrade on Java Server Pages and Servlet Clients
• 6.2 Impact of Upgrade on Java Naming and Directory Interface Clients
  • 6.2.1 Modifying Clients to Use the Oracle WebLogic Server JNDI Provider
  • 6.2.2 Understanding the Scope of the Oracle WebLogic Server JNDI Namespace
• 6.3 Impact of Upgrade on Enterprise Java Bean Clients
  • 6.3.1 Impact on Remote Standalone EJB Clients
  • 6.3.2 Impact on Clients That Use OC4J-Based EJB Interfaces
• 6.4 Impact of Upgrade on JMS Clients
  • 6.4.1 Changes Required When the JMS Provider is Upgraded to WebLogic Server
  • 6.4.2 Changes Required When the JMS Provider Remains in OC4J

7 Upgrading a Java EE and Web Server Environment

• 7.1 Task 1: Understand the Differences Between Using Oracle HTTP Server with OC4J and Oracle WebLogic Server
  • 7.1.1 Configuring Web Sites and AJP Connections in Oracle WebLogic Server
  • 7.1.2 Installing and Configuring Oracle HTTP Server for Oracle WebLogic Server
    • 7.1.2.1 How Oracle HTTP Server Is Configured for OC4J
    • 7.1.2.2 How Oracle HTTP Server is Configured for Oracle WebLogic Server
  • 7.1.3 Using Web Servers Other than Oracle HTTP Server with Oracle WebLogic Server
  • 7.1.4 Understanding Oracle HTTP Server Interoperability Issues When Upgrading to Oracle Fusion Middleware 11g
• 7.2 Task 2: Install and Configure an Oracle Fusion Middleware Web Tier
  • 7.2.1 Deciding Upon a Location for Your Web Tier Components
  • 7.2.2 Associating the Web Tier Components with an Oracle WebLogic Server Domain
  • 7.2.3 Locating the Web Tier Installation and Configuration Documentation
• 7.3 Task 3: Upgrade Your Oracle Application Server 10g Web Tier Components to Oracle Fusion Middleware 11g
  • 7.3.1 Task 3a: Start the Upgrade Assistant for an Web Tier Upgrade
  • 7.3.2 Task 3b: Use the Upgrade Assistant to Upgrade the Web Tier Components
    • 7.3.2.1 Upgrading the Web Tier Components
    • 7.3.2.2 Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance
• 7.4 Task 4: Configure the Web Tier To Route Requests to Your Oracle Fusion Middleware Environment
• 7.5 Task 5: Perform Any Required Post-Upgrade Tasks for the Web Tier Components
  • 7.5.1 Verifying the Location of the Oracle HTTP Server and Oracle Web Cache Wallets After Upgrade
  • 7.5.2 Verifying and Updating the Oracle HTTP Server and Oracle Web Cache Ports After Upgrade
• 7.6 Task 6: Verify the Web Tier Upgrade

A orion-web.xml and orion-ejb-jar.xml Upgrade Reference

• orion-web.xml
  • <classpath>
  • <contextParamMappingFinding>
  • <mimeMappings>
  • <virtual-directory>
  • <access-mask>
  • <servlet-chaining>
  • <request-tracker>
  • <session-tracking>
  • <session-tracker>
  • <resource-ref-mapping>
  • <lookup-context>
  • <resource-env-ref-mapping>
  • <env-entry-mapping>
  • <ejb-ref-mapping>
  • <service-ref-mapping>
  • <expiration-setting>
  • <jazn-web-app>
  • <security-role-mapping>
  • <web-app-class-loader>
    • search-local-classes-first
    • include-war-manifest-class-path
    • autojoin-session
    • default-buffer-size
    • default-charset
    • default-mime-type
    • development
    • directory-browsing
    • enable-jsp-dispatcher-shortcut
    • file-modification-check-interval
    • jsp-cache-directory
    • jsp-cache-tlds
    • jsp-print-null
    • jsp-taglib-locations
    • jsp-timeout
    • persistence-path
    • schema-major-version
    • schema-minor-version
    • servlet-webdir
    • simple-jsp-mapping
    • source-directory
    • temporary-directory
• orion-ejb-jar.xml
  • <session-deployment>
    • copy-by-value
    • idletime
    • min-instances
    • max-instances
    • max-instances-threshold
    • max-tx-retries
    • resource-check-interval
    • passivate-count
    • persistence-filename
    • pool-cache-timeout
    • timeout
    • transaction-timeout
  • <ejb-ref-mapping>
  • <resource-ref-mapping>
  • <resource-env-ref-mapping>
  • <message-destination-ref-mapping>
  • <session-type>Stateful</session-type>
  • <message-driven-deployment>
    • connection-factory-location
    • dequeue-retry-count
    • dequeue-retry-interval
    • destination-location
    • listener-threads
    • max-delivery-count
    • resource-adapter
    • subscription-name
    • wrapper-class
  • <config-property>