1/19
Contents
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Summary of the Oracle SOA Suite, WebCenter, and ADF Upgrade Process
1.1
Flow Chart of the Oracle SOA Suite, WebCenter, and ADF Upgrade Process
1.2
Table Describing the Steps in the Oracle SOA Suite and WebCenter Upgrade Process
Part I Preparing to Upgrade Oracle SOA Suite, WebCenter, and ADF
2
Supported Starting Points for Oracle SOA Suite, WebCenter, and ADF Upgrade
2.1
Summary of Supported Starting Points for Oracle SOA Suite, WebCenter, and ADF
2.2
Information for Oracle SOA Suite 10
g
Release 2 (10.1.2) Users
3
Oracle SOA Suite, WebCenter, and ADF Information for 10
g
Users
3.1
Information for Oracle ADF Users
3.2
Information for Oracle SOA Suite Users
3.2.1
Comparing Oracle SOA Suite on OC4J and Oracle WebLogic Server
3.2.2
Comparing the Oracle SOA Suite Directory Structure on OC4J and Oracle WebLogic Server
3.2.3
Upgrading an Oracle SOA Suite Enterprise Deployment
3.2.4
About Oracle BAM and Oracle B2B in Oracle Application Server 10
g
and Oracle Fusion Middleware 11
g
3.3
Information for Oracle WebCenter Users
3.3.1
Comparing Oracle WebCenter on OC4J and Oracle WebLogic Server
3.3.2
Comparing the Oracle WebCenter Directory Structure on OC4J and Oracle WebLogic Server
4
Special Considerations for Oracle BPEL Long-Running Processes
4.1
What Is an Oracle BPEL Process Manager Long-Running Process?
4.2
Two Approaches to Upgrading Long-Running Processes
4.2.1
Using a Side-by-Side Approach to Long-Running Processes During Upgrade
4.2.2
Using a Grace Period and a Hard Stop of Long-Running Processes
Part II Upgrading the Oracle SOA Suite, WebCenter, and ADF Environment
5
Upgrading an Oracle ADF Environment
5.1
Task 1: Decide Upon an Oracle Fusion Middleware 11
g
Topology for Your ADF Applications
5.2
Task 2: Install and Configure a Oracle WebLogic Server Domain For Your ADF Applications
5.2.1
Installing and Configuring a Development Domain with Oracle JDeveloper
5.2.2
Installing and Configuring a Domain without JDeveloper
5.2.3
Using the Java Required Files (JRF) Domain Template
5.2.3.1
Creating a New Domain With the JRF Template
5.2.3.2
Extending an Existing Domain With the JRF Template
5.2.3.3
Upgrading Existing Oracle WebLogic Server Instances to the 11.1.1.1.0 ADF Runtime
6
Upgrading an Oracle SOA Suite Environment
6.1
Task 1: Decide Upon an Oracle SOA Topology
6.2
Task 2: Verify that Any Required External Partners are Up and Running
6.3
Task 3: If Necessary, Upgrade the Oracle Database That Hosts the Oracle SOA Suite Schemas
6.4
Task 4: Use the Repository Creation Utility to Install the 11
g
SOA Schemas
6.4.1
Running the Repository Creation Utility in Preparation for an Oracle SOA Suite Upgrade
6.4.2
Selecting the Schemas Required for a Oracle SOA Suite Upgrade
6.5
Task 5: Install and Configure the Oracle SOA Middle Tiers
6.6
Task 6: If Necessary, Upgrade the SOA Component Schemas
6.6.1
Task 6a: Start the Upgrade Assistant for an Oracle SOA Schema Upgrade
6.6.2
Task 6b: If Necessary, Upgrade the B2B Schema
6.6.2.1
General Information About the B2B Schema Upgrade
6.6.2.2
Applying the Required Patch Set to the Oracle B2B 10
g
Middle Tier
6.6.2.3
Setting the Maximum Message Size Attribute In the Oracle WebLogic Server Administration Console
6.6.2.4
Performing the B2B Schema Upgrade
6.6.3
Task 6c: If Necessary, Upgrade the BAM Schema
6.6.3.1
Understanding the Oracle BAM Schema Upgrade
6.6.3.2
About Upgrading From Previous Versions of Oracle BAM
6.6.3.3
Applying the Required Patch Set to the Oracle Database That Contains the Oracle BAM Schema
6.6.3.4
Performing the Oracle BAM Schema Upgrade
6.7
Task 7: Configure Any Required Java EE Features to Support Your SOA Applications
6.8
Task 8: Perform Any Required Post-Upgrade Tasks for the SOA Components
6.8.1
Configuring Oracle SOA Suite 11
g
to Use Identity Management Components
6.8.2
About Case Sensitivity in Oracle Human Workflow
6.8.3
Oracle B2B Post-Upgrade Information and Tasks
7
Upgrading an Oracle WebCenter Environment
7.1
Task 1: Decide Upon a Oracle WebCenter Topology
7.2
Task 2: If Necessary, Upgrade the Oracle Database That Hosts the Oracle WebCenter Schemas
7.3
Task 3: Use the Repository Creation Utility to Install the 11
g
Oracle WebCenter Schemas
7.3.1
Running the Repository Creation Utility in Preparation for an Oracle WebCenter Upgrade
7.3.2
Selecting the Schemas Required for a Oracle WebCenter Upgrade
7.4
Task 4: Install and Configure the Oracle WebCenter Middle Tiers
7.5
Task 5: Configure Any Required Java EE Features to Support Your Oracle WebCenter Applications
Part III Upgrading the Oracle SOA Suite and Oracle WebCenter Applications
8
Overview of Upgrading Oracle SOA Suite, WebCenter, and ADF Applications
8.1
Task 1: Review Sample Application Upgrade Procedures
8.2
Task 2: Verify that the Applications Are Up and Running Successfully on Oracle Application Server 10
g
8.3
Task 3: Verify That You Have Upgraded Your 10
g
Environment to 11
g
8.4
Task 4: Install and Start Oracle JDeveloper 11
g
8.5
Task 5: Open and Upgrade the Application in Oracle JDeveloper
8.6
Task 6: Locate Specific Upgrade Information for the Components of Your Application
8.7
Task 7: Review and Recompile the Application
8.8
Task 8: Redeploy the Application
9
Considerations When Upgrading Oracle SOA Applications
9.1
About Using the Oracle JDeveloper 11
g
Migration Wizard for Oracle SOA Suite Applications
9.2
Upgrade Tasks Associated with All Java Applications
9.3
Upgrade Tasks Associated with All Oracle SOA Suite Applications
9.3.1
Understanding Oracle SOA Suite API Changes for Oracle Fusion Middleware 11
g
9.3.1.1
Upgrading to the Oracle Fusion Middleware Java API for Oracle Business Rules
9.3.1.1.1
Overview of the Oracle Business Rules SDK and API Changes for 11
g
9.3.1.1.2
Accessing a Dictionary in the Development Environment
9.3.1.1.3
Accessing a Repository in a Production Environment
9.3.1.1.4
Generating RL Code
9.3.1.2
Upgrading to the Oracle Fusion Middleware Infrastructure Management Java API for Oracle SOA Suite
9.3.2
Reviewing Your Projects for Dependent JAR Files
9.3.3
Upgrading Applications That Require Proxy Settings for Web Services
9.3.4
Recreating build.xml and build.properties Files Not Upgraded by the Migration Wizard
9.3.5
Upgrading Projects That Use UDDI-Registered Resources
9.3.5.1
Verifying that serviceKey Endpoints Are Available Before Upgrade
9.3.5.2
Changing to the orauddi Protocol
9.3.6
Using the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.1
Benefits of Using the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.2
Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11
g
9.3.6.3
Limitations When Upgrading Human Workflow Applications with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.4
Upgrading BPEL Projects with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.5
Combining Multiple BPEL Projects Into a Single Composite with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.6
Upgrading Oracle Enterprise Service Bus (ESB) Projects with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.6.7
Upgrading Domain Value Maps (DVMs) and Cross References with the Oracle SOA Suite Command-Line Upgrade Tool
9.4
Upgrade Tasks Associated with Oracle BPEL Process Manager Applications
9.4.1
Manual Upgrade Steps After Migrating Oracle BPEL Process Manager Applications
9.4.1.1
Providing Missing Binding Information for External References
9.4.1.2
Correcting Problems With Oracle BPEL Process Manager Test Suites
9.4.1.3
Using Oracle BPEL Process Manager Deployment Plans After Upgrade
9.4.1.4
Upgrading Fault Policies in an Oracle BPEL Process Manager Project
9.4.1.5
Upgrading a 10
g
Project With No BPEL Folder
9.4.2
Additional Considerations for Oracle BPEL Process Manager Applications
9.4.2.1
Verifying New and Deprecated Properties in the bpel.xml Deployment Descriptor
9.4.2.2
Upgrading User-Defined (Custom) XPath Functions in an Oracle BPEL Process Manager Project
9.4.2.3
Change in Support for Multiple BPEL Implementations
9.4.2.4
Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service.
9.4.2.5
Upgrading Projects With the transaction=participate Property
9.4.2.6
Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11
g
9.5
Upgrade Tasks Associated with Oracle Enterprise Service Bus
9.5.1
Upgrading Oracle Enterprise Service Bus Routing Rules That Are Not Exposed as Services
9.5.2
Upgrading Oracle Enterprise Service Bus Domain Value Maps (DVMs) and Cross References
9.5.3
Upgrading Oracle Enterprise Service Bus Projects with SOAP Headers to Oracle Mediator 11
g
9.5.4
Upgrading Projects with Multiple Routing Services That Use the Same Namespace
9.5.5
Upgrading Routing Services to Use Asynchronous Routing
9.5.6
Upgrading Filtering or Setting Message Headers in Oracle Enterprise Service Bus
9.6
Upgrade Tasks Associated with Oracle Business Activity Monitoring
9.6.1
Migrating Oracle BAM Users and Other LDAP Information to 11
g
9.6.2
Verifying Oracle BAM Action Form Templates After Upgrade
9.6.3
Upgrading Oracle BAM External Data Sources
9.6.4
Missing Images in Oracle BAM Reports
9.6.5
Using Oracle BAM Web Services in 11
g
9.6.5.1
Using Web Services Clients with Oracle BAM 11
g
9.6.5.2
Invoking Web Services from Oracle BAM Alerts
9.6.5.3
Using the ManualRuleFire Web Service in Oracle BAM 11
g
9.6.5.4
New Support for Web Services in Oracle BAM 11
g
9.6.6
Upgrading Oracle BAM Sensor Actions
9.6.7
Upgrading Enterprise Link Plans to Oracle BAM 11
g
9.7
Upgrade Tasks Associated with Technology Adapters
9.7.1
Verifying Adapters with the Oracle JDeveloper 11
g
Adapter Configuration Wizard
9.7.2
Upgrading Adapter Header Variables
9.7.3
Upgrading Non-Managed Connection Information in the Adapter JCA File
9.7.4
Description Lost After Upgrade of Technology Adapter
9.7.5
Upgrading an Inbound Synchronous Request-Reply Use Case
9.7.6
Upgrading Projects That Use Outbound Dequeue
9.7.7
Upgrading AQ Adapter Headers
9.7.8
Upgrading an AQ Outbound Request-Reply Scenario
9.7.9
Upgrading Database Adapters Used for Stored Procedures
9.8
Upgrade Tasks Associated with Human Workflow Tasks
9.8.1
Upgrading Task Details for an Associated Human Workflow Task
9.8.2
Upgrading Multiple Projects That Share a Common Human Workflow Task
9.9
Upgrade Tasks Associated with Oracle Business Rules
9.10
Upgrading Oracle SOA Suite Client Applications
9.11
Upgrading Oracle Web Services Manager (WSM) Policies
9.11.1
Before You Upgrade
9.11.1.1
A Note About Oracle WSM 10
g
Gateways
9.11.1.2
A Note About Third-party Software
9.11.2
Upgrading Oracle WSM 10
g
Predefined Policies
9.11.3
Upgrading Oracle WSM Custom Policies
9.12
Upgrading Oracle Containers for J2EE (OC4J) Security Environments
9.12.1
Before You Upgrade
9.12.2
Anonymous Authentication with Message Protection (WS-Security 1.0)
9.12.2.1
OC4J 10
g
9.12.2.2
Oracle WSM 11
g
9.12.3
Anonymous Authentication with Message Integrity (WS-Security 1.0)
9.12.3.1
OC4J 10
g
9.12.3.2
Oracle WSM 11
g
9.12.4
Anonymous Authentication with Message Confidentiality (WS-Security 1.0)
9.12.4.1
OC4J 10
g
9.12.4.2
Oracle WSM 11
g
9.12.5
Username Token with Message Protection (WS-Security 1.0)
9.12.5.1
OC4J 10
g
9.12.5.2
Oracle WSM 11
g
9.12.6
ID Propagation Using SAML Token (Sender Vouches) with Message Protection (WS-Security 1.0)
9.12.6.1
OC4J 10
g
9.12.6.2
Oracle WSM 11
g
9.12.7
ID Propagation Using SAML Token (Holder of Key) with Message Protection (WS-Security 1.0)
9.12.7.1
OC4J 10
g
9.12.7.2
Oracle WSM 11
g
9.12.8
Mutual Authentication with Message Protection (WS-Security 1.0)
9.12.8.1
OC4J 10
g
9.12.8.2
Oracle WSM 11
g
9.12.9
Username token over SSL
9.12.9.1
OC4J 10
g
9.12.9.2
Oracle WSM 11
g
9.12.10
ID Propagation with SAML Token (Sender Vouches) over SSL (WS-Security 1.0)
9.12.10.1
OC4J 10
g
9.12.10.2
Oracle WSM 11
g
9.12.11
Log Information
9.12.11.1
OC4J 10
g
9.12.11.2
Oracle WSM 11
g
10
Considerations When Upgrading Oracle WebCenter Applications
10.1
About Migration of WebCenter Applications
10.1.1
About WebCenter Application Templates
10.1.2
About Migration Tasks
10.2
Prerequisite Tasks for Migrating a WebCenter Application
10.3
How To Migrate WebCenter Applications
10.3.1
Preparing Your Applications for Migration
10.3.1.1
Backing Up Your WebCenter Applications
10.3.1.2
Preparing Applications That Rely on Oracle Content DB
10.3.1.2.1
Upgrading Your Application in JDeveloper 10.1.3.4
10.3.1.2.2
Migrating Oracle Content DB Data
10.3.1.3
Preparing Applications That Contain Portlets
10.3.2
Migrating Your WebCenter Application
10.3.3
Performing Post Migration Tasks
10.3.3.1
Migrating Oracle Portal Connections
10.3.3.2
Configuring ADF Security
10.3.3.3
Downloading the Content Integration Suite API
10.3.3.4
Migrating Producer Registrations of Preconfigured Portlet Producers
10.3.3.5
Redeploying Your Applications
10.4
How to Migrate Portlet Producers
10.4.1
Determining WebCenter Consumer Application and Portlet Producer Compatibility
10.4.2
Migrating Your Portlet Producer Applications
10.4.2.1
Migrating Portlet Producers Created in JDeveloper
10.4.2.2
Migrating Portlet Producers Created Outside of JDeveloper
10.4.2.2.1
Creating a JDeveloper Application from an EAR File
10.4.2.2.2
Creating a JDeveloper Application from a WAR File
10.4.2.3
Migrating Preconfigured Portlet Producers
10.4.2.3.1
Migrating Customizations from the Default Location
10.4.2.3.2
Migrating Customizations from a Nondefault Location
10.4.3
Performing Post Migration Tasks for Portlet Producers
10.4.3.1
Migrating Customizations
10.4.3.2
Redeploying a Portlet Producer Application
10.5
How to Migrate Wiki Data
10.5.1
Migrating Content to a File System-Based Repository
10.5.2
Migrating Content to a Database Repository
A
Example: Upgrading and Redeploying SOA Order Booking
A.1
About the SOA Order Booking Application
A.2
Task 1: Verify That the SOA Order Booking and Its External Partners are Up and Running
A.2.1
Task 1a: Verify That the SOA Order Booking Is Successfully Deployed on Oracle Application Server 10
g
Release 3 (10.1.3.4)
A.2.2
Task 1b: Verify That SOA Order Booking Is Currently Running on Oracle Application Server 10
g
Release 3 (10.1.3.4)
A.2.3
Task 1c: Verify That All External Partners Are Available
A.3
Task 2: Install and Upgrade the Oracle Fusion Middleware SOA Suite
A.4
Task 3: Use the Oracle WebLogic Suite Administration Console to Configure Required Resources
A.4.1
Task 3a: Create the SOADEMO Data Source
A.4.2
Task 3b: Configure the DbAdapter Application
A.4.2.1
Creating a New Outbound Connection Pool for the DbAdapter Application
A.4.2.2
Configuring the New Connection Pool for the DbAdapter Application
A.4.3
Task 3c: Create the SOA Order Booking JMS Resources
A.4.3.1
Creating the JMS Queue for the SOA Order Booking Demo
A.4.3.2
Creating a JMS Connection Factory for the SOA Order Booking Demo
A.4.3.3
Creating an Outbound Connection Pool for the JmsAdapter Application
A.4.3.4
Configuring the JmsAdapter Connection Pool
A.4.3.5
Redeploying the Modified JmsAdapter Application
A.5
Task 4: Install Oracle JDeveloper 11
g
A.6
Task 5: Set Up Connections in Oracle JDeveloper Release 11
A.6.1
Task 5a: Start Oracle JDeveloper 11
g
A.6.2
Task 5b: Verify That You Have the Required Oracle JDeveloper Extensions
A.6.3
Task 5c: Create a Connection to the SOADEMO Schema
A.6.4
Task 5d: Create a Connection to Oracle WebLogic Server
A.7
Task 6: Open the SOA Order Booking Application in Oracle JDeveloper 11
g
and Migrate the Application Projects
A.7.1
Opening and Migrating the Application
A.7.2
Viewing the Migration Log Files
A.8
Task 7: Compile and Deploy Each of the Application Projects on Oracle Fusion Middleware 11
g
A.8.1
About the CreditService, RapidService, and CustomerService Projects
A.8.2
SelectManufacturer
A.8.3
DHLShipment
A.8.4
FulfillmentESB
A.8.4.1
Modifying the FulfillmentESB Project in Oracle JDeveloper 11
g
A.8.4.2
Compile and Deploy the FulfillmentESB Project
A.8.5
CreditService
A.8.5.1
Upgrading the CreditService Web Services
A.8.5.2
Compiling and Deploying the CreditService Project
A.8.6
RapidService
A.8.6.1
Upgrade the RapidService Web Service from OC4J JAX-RPC to Oracle WebLogic Server JAX-WS
A.8.6.2
Compiling and Deploying the RapidService Project
A.8.7
CustomerService
A.8.7.1
Modifying Specific CustomerService Project Class Files
A.8.7.2
Modifying the persistence.xml File in the CustomerService Project
A.8.7.3
Compiling and Deploying the CustomerService Project
A.8.8
SOAOrderBooking
A.8.8.1
Modifying the SOAOrderBooking Project
A.8.8.2
Optionally, Changing SOAOrderBooking to Use Upgraded Web Services
A.8.8.3
Compiling and Deploying the SOAOrderBooking Project:
A.8.9
OrderBookingESB
A.8.9.1
Modifying the OrderBookingESB Project
A.8.9.2
Compiling and Deploying the OrderBookingESB Project:
A.8.10
ApproveOrderTaskForm
A.9
Task 8: Test the SOA Order Booking Application in Fusion Middleware Control
B
Additional Oracle WebCenter Migration Details
B.1
Automated Changes in Migrated WebCenter Applications
B.1.1
Customizable Component Changes
B.1.1.1
General Changes
B.1.1.2
Panel Customizable Changes
B.1.1.3
Show Detail Frame
B.1.2
External Application Changes
B.1.2.1
External Applications Changes in Oracle Application Server 10g and Oracle Fusion Middleware 11g
B.1.2.2
External Application Migration Changes
B.1.3
Portlet Component Changes
B.1.3.1
Portlet Tag Changes
B.1.3.2
Attribute Changes
B.2
Content Integration Connections: Migration of Credentials to External Applications
B.3
Preconfigured Portlet Producer: Customization Store Location
B.3.1
WSRP Portlet Producers
B.3.2
Web Clipping Portlet Producer
B.3.3
OmniPortlet and other PDK-Java Portlet Producers
C
Upgrading Oracle Business Rules Dictionaries and Projects
C.1
Using Oracle JDeveloper to Migrate an Oracle Business Rules Dictionary
C.2
Using Rule Migrator Tool to Migrate an Oracle Business Rules Dictionary
C.3
Using MigrateRuleRepository with Oracle Business Rules SDK to Migrate a Dictionary
C.3.1
How to Migrate a Dictionary with Oracle Business Rules SDK
C.3.2
What You May Need to Know About the MigrateRuleRepository API
C.3.2.1
Input Properties
C.3.2.2
Output Properties
C.4
Oracle Business Rules Manual Migration Tasks
C.4.1
How to Migrate JAXB 1.0 to JAXB 2.0
C.4.2
How to Migrate RL Functions
C.4.3
What You May Need to Know About Manual Migration
Scripting on this page enhances content navigation, but does not change the content in any way.