1/24
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 Upgrade 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: If Necessary, Upgrade the Oracle Database That Hosts the Oracle SOA Suite Schemas
6.3
Task 3: Use the Repository Creation Utility to Install the 11
g
SOA Schemas
6.3.1
Running the Repository Creation Utility in Preparation for an Oracle SOA Suite Upgrade
6.3.2
Selecting the Schemas Required for a Oracle SOA Suite Upgrade
6.4
Task 4: Install and Configure the Oracle SOA Suite 11
g
Middle Tiers
6.5
Task 5: If Necessary, Upgrade the SOA Component Schemas
6.5.1
Task 5a: Start the Upgrade Assistant for an Oracle SOA Schema Upgrade
6.5.2
Task 5b: If Necessary, Upgrade the B2B Schema
6.5.2.1
General Information About the B2B Schema Upgrade
6.5.2.2
Applying the Required Patch Set to the Oracle B2B 10
g
Middle Tier
6.5.2.3
Setting the Maximum Message Size Attribute In the Oracle WebLogic Server Administration Console
6.5.2.4
Performing the B2B Schema Upgrade
6.5.3
Task 5c: If Necessary, Upgrade the BAM Schema
6.5.3.1
Understanding the Oracle BAM Schema Upgrade
6.5.3.2
About Upgrading From Previous Versions of Oracle BAM
6.5.3.3
Applying the Required Patch Set to the Oracle Database That Contains the Oracle BAM Schema
6.5.3.4
Performing the Oracle BAM Schema Upgrade
6.5.3.5
Recovering From and Retrying an Interrupted Oracle BAM Schema Upgrade
6.5.3.6
Locating and Configuring the Oracle BAM Upgrade Log Files
6.6
Task 6: Configure Any Required Java EE Features to Support Your SOA Applications
6.7
Task 7: Perform Any Required Post-Upgrade Tasks for the SOA Components
6.7.1
Configuring Oracle SOA Suite 11
g
to Use Identity Management Components
6.7.2
About Case Sensitivity in Oracle Human Workflow
7
Upgrading an Oracle WebCenter Environment
7.1
Task 1: Decide Upon an 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 an 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
7.6
Task 6: Upgrade Back-End Components for WebCenter Services
7.6.1
Upgrading Oracle WebCenter Discussions
7.6.2
Upgrading Oracle Content Server
7.6.3
Migrating Oracle WebCenter Wiki and Blog Server Data
Part III Upgrading Oracle SOA Suite, Oracle WebCenter, and ADF 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: Review the Specific Considerations for the Type of Application You Are Upgrading
8.4
Task 4: Verify That You Have Upgraded Your 10
g
Environment to 11
g
8.5
Task 5: Install and Start Oracle JDeveloper 11
g
8.6
Task 6: Open and Upgrade the Application in Oracle JDeveloper
8.7
Task 7: Locate Specific Upgrade Information for the Components of Your Application
8.8
Task 8: Review and Recompile the Application
8.9
Task 9: Redeploy the Application
9
Considerations When Upgrading All 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
Understanding File Naming Conventions in Oracle SOA Suite 11
g
9.3.7
Using the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.1
Benefits of Using the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.2
Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11
g
9.3.7.3
Limitations When Upgrading Human Workflow Applications with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.4
Upgrading BPEL or ESB Projects with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.5
Combining Multiple BPEL Projects Into a Single Composite with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.6
Upgrading Oracle Enterprise Service Bus (ESB) Projects with the Oracle SOA Suite Command-Line Upgrade Tool
9.3.7.7
Upgrading Domain Value Maps (DVMs) and Cross References (XREFs) in the ESB Repository
9.3.8
Upgrading Oracle SOA Suite 10
g
Cross-References (XREF) Runtime Data to 11
g
9.3.8.1
Procedure for Upgrading the XREF Runtime Data
9.3.8.2
Additional Tasks and Considerations When Upgrading the XREF Runtime Data
10
Upgrading Oracle BPEL Process Manager Applications
10.1
Manual Upgrade Steps After Migrating Oracle BPEL Process Manager Applications
10.1.1
Providing Missing Binding Information for External References
10.1.2
Correcting Problems With Oracle BPEL Process Manager Test Suites
10.1.3
Using Oracle BPEL Process Manager Deployment Plans After Upgrade
10.1.4
Upgrading Fault Policies in an Oracle BPEL Process Manager Project
10.1.5
Upgrading a 10
g
Project With No BPEL Folder
10.1.6
Post-Upgrade Steps for Projects That Use WSIF Bindings to EJBs
10.2
Additional Considerations for Oracle BPEL Process Manager Applications
10.2.1
Verifying New and Deprecated Properties in the bpel.xml Deployment Descriptor
10.2.2
Upgrading User-Defined (Custom) XPath Functions in an Oracle BPEL Process Manager Project
10.2.3
Change in Support for Multiple BPEL Implementations
10.2.4
Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service.
10.2.5
Upgrading Projects With the transaction=participate Property
10.2.6
Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11
g
10.2.7
Upgrading Applications That Use Multiple Oracle BPEL Process Manager Domains
10.2.8
Verifying Process ID, Project Name, and BPEL File Name Conventions Before Upgrade
10.2.9
Verifying Oracle BPEL Process Manager 11
g
Namespace Prefixes in XPath Functions
10.2.10
Upgrading Oracle BPEL Process Manager Projects with Multiple Tasks
11
Upgrading Oracle Business Activity Monitoring Applications
11.1
Migrating Oracle BAM Users, Groups, and Other LDAP Information to 11
g
11.2
Verifying Oracle BAM Action Form Templates After Upgrade
11.3
Upgrading Oracle BAM External Data Sources
11.4
Upgrading Images in Oracle BAM Reports
11.5
Using Oracle BAM Web Services in 11
g
11.5.1
Using Web Services Clients with Oracle BAM 11
g
11.5.2
Invoking Web Services from Oracle BAM Alerts
11.5.3
Using the ManualRuleFire Web Service in Oracle BAM 11
g
11.5.4
New Support for Web Services in Oracle BAM 11
g
11.6
Upgrading Oracle BAM Sensor Actions
11.7
Upgrading Enterprise Link Plans to Oracle BAM 11
g
11.8
Additional Considerations When Upgrading to Oracle BAM 11
g
11.8.1
Using Oracle BAM Alert Actions After Upgrade
11.8.2
Recreating Oracle BAM Enterprise Message Sources After Upgrade
12
Upgrading Oracle B2B Applications
12.1
Features That are Not Upgraded to Oracle B2B 11
g
12.1.1
Host and Partner Security Certificates
12.1.2
Callout Library JAR Files
12.1.3
Exchange Protocol Parameter Identifiers
12.1.4
The Receipt Recipient Property of the AS2-1.1 Channel
12.1.5
Generic TCP Channels
12.1.6
PositionalFlatFile Documents
12.2
Features That are Changed After Upgrade to Oracle B2B 11
g
12.2.1
Document Protocol Revision and Document Type Fields
12.2.2
Exchange Protocol Parameters for the MLLP Channel
12.2.3
Channel Passwords
12.2.4
Optional Fields in Oracle B2B 10
g
That are Mandatory in Oracle B2B 11
g
12.2.5
Inbound and Outbound Partner Agreements
12.2.6
RosettaNet Outbound Messages
12.3
Oracle B2B 11
g
Post-Upgrade Tasks
12.3.1
Configuring MLLP Channels for Inbound and Outbound Messages
12.3.2
Considerations When Upgrading B2B-Related Oracle BPEL Processes
13
Upgrading Oracle Web Services Manager Policies and OC4J Security Enviroments
13.1
Upgrading Oracle Web Services Manager (WSM) Policies
13.1.1
Before You Upgrade
13.1.1.1
A Note About Oracle WSM 10
g
Gateways
13.1.1.2
A Note About Third-party Software
13.1.2
Upgrading Oracle WSM 10
g
Predefined Policies
13.1.3
Upgrading Oracle WSM Custom Policies
13.2
Upgrading Oracle Containers for J2EE (OC4J) Security Environments
13.2.1
Before You Upgrade
13.2.2
Anonymous Authentication with Message Protection (WS-Security 1.0)
13.2.2.1
OC4J 10
g
13.2.2.2
Oracle WSM 11
g
13.2.3
Anonymous Authentication with Message Integrity (WS-Security 1.0)
13.2.3.1
OC4J 10
g
13.2.3.2
Oracle WSM 11
g
13.2.4
Anonymous Authentication with Message Confidentiality (WS-Security 1.0)
13.2.4.1
OC4J 10
g
13.2.4.2
Oracle WSM 11
g
13.2.5
Username Token with Message Protection (WS-Security 1.0)
13.2.5.1
OC4J 10
g
13.2.5.2
Oracle WSM 11
g
13.2.6
ID Propagation Using SAML Token (Sender Vouches) with Message Protection (WS-Security 1.0)
13.2.6.1
OC4J 10
g
13.2.6.2
Oracle WSM 11
g
13.2.7
ID Propagation Using SAML Token (Holder of Key) with Message Protection (WS-Security 1.0)
13.2.7.1
OC4J 10
g
13.2.7.2
Oracle WSM 11
g
13.2.8
Mutual Authentication with Message Protection (WS-Security 1.0)
13.2.8.1
OC4J 10
g
13.2.8.2
Oracle WSM 11
g
13.2.9
Username token over SSL
13.2.9.1
OC4J 10
g
13.2.9.2
Oracle WSM 11
g
13.2.10
ID Propagation with SAML Token (Sender Vouches) over SSL (WS-Security 1.0)
13.2.10.1
OC4J 10
g
13.2.10.2
Oracle WSM 11
g
13.2.11
Log Information
13.2.11.1
OC4J 10
g
13.2.11.2
Oracle WSM 11
g
14
Upgrading Other Oracle SOA Suite Technologies
14.1
Upgrade Tasks Associated with Oracle Enterprise Service Bus
14.1.1
Upgrading Oracle Enterprise Service Bus Routing Rules That Are Not Exposed as Services
14.1.2
Upgrading Oracle Enterprise Service Bus Domain Value Maps (DVMs) and Cross References
14.1.3
Upgrading Oracle Enterprise Service Bus Projects with SOAP Headers to Oracle Mediator 11
g
14.1.4
Upgrading Projects with Multiple Routing Services That Use the Same Namespace
14.1.5
Upgrading Routing Services to Use Asynchronous Routing
14.1.6
Upgrading Filtering or Setting Message Headers in Oracle Enterprise Service Bus
14.1.7
Using the Sync From ESB Server Command Before Upgrading ESB Projects
14.2
Upgrade Tasks Associated with Technology Adapters
14.2.1
Verifying Adapters with the Oracle JDeveloper 11
g
Adapter Configuration Wizard
14.2.2
Upgrading Adapter Header Variables
14.2.3
Upgrading Non-Managed Connection Information in the Adapter JCA File
14.2.4
Description Lost After Upgrade of Technology Adapter
14.2.5
Upgrading an Inbound Synchronous Request-Reply Use Case
14.2.6
Upgrading Projects That Use Outbound Dequeue
14.2.7
Upgrading AQ Adapter Headers
14.2.8
Additional Steps When Upgrading Technology Adapter Headers
14.2.9
Upgrading Composite Applications That Rely on Payload Header Functionality
14.2.10
Upgrading an AQ Outbound Request-Reply Scenario
14.2.11
Upgrading Database Adapters Used for Stored Procedures
14.3
Upgrade Tasks Associated with Human Workflow Tasks
14.3.1
Upgrading Task Details for an Associated Human Workflow Task
14.3.2
Upgrading Multiple Projects That Share a Common Human Workflow Task
14.3.3
Editing Human Workflow Tasks After Upgrade
14.4
Upgrade Tasks Associated with Oracle Business Rules
14.5
Upgrading Oracle SOA Suite Client Applications
15
Considerations When Upgrading Oracle WebCenter Applications
15.1
About Upgrading WebCenter Applications
15.1.1
Tasks Involved in Upgrading WebCenter Applications
15.1.2
About WebCenter Application Templates
15.2
Prerequisites for Upgrading WebCenter Applications
15.3
Upgrading WebCenter Consumer Applications
15.3.1
Preparing Your Applications for Upgrade
15.3.1.1
Backing Up Your Applications
15.3.1.2
Preparing Applications That Rely on Oracle Content DB
15.3.1.3
Preparing Applications That Contain Portlets
15.3.2
Upgrading Your WebCenter Application
15.3.3
Performing Post Upgrade Tasks
15.3.3.1
Configuring Application Settings for Customizable Components
15.3.3.2
Moving Resource Catalogs from an Application's MDS to a Project Directory
15.3.3.3
Upgrading Oracle Portal Connections
15.3.3.4
Configuring ADF Security
15.3.3.5
Upgrading Producer Registrations of Preconfigured Portlet Producers
15.3.3.6
Redeploying Your Applications
15.4
Upgrading Portlet Producers
15.4.1
Determining WebCenter Consumer Application and Portlet Producer Compatibility
15.4.2
Upgrading Portlet Producer Applications
15.4.2.1
About Upgrading JSR168 Portlet Producers to JSR286
15.4.2.2
Upgrading Portlet Producers Created in JDeveloper
15.4.2.3
Upgrading Portlet Producers Created Outside of JDeveloper
15.4.2.3.1
Creating a JDeveloper Application from an EAR File
15.4.2.3.2
Creating a JDeveloper Application from a WAR File
15.4.2.4
Upgrading Preconfigured Portlet Producers
15.4.2.4.1
Migrating Customizations from the Default Location
15.4.2.4.2
Migrating Customizations from a Nondefault Location
15.4.3
Performing Post Upgrade Tasks for Portlet Producers
15.4.3.1
Migrating Customizations
15.4.3.2
Redeploying a Portlet Producer Application
15.5
Migrating Data
15.5.1
Migrating Data from Oracle WebCenter Wiki and Blog Server
15.5.2
Migrating Data from Oracle Content DB
16
Additional Oracle WebCenter Upgrade Details
16.1
Automated Changes in Upgraded WebCenter Applications
16.1.1
Customizable Component Changes
16.1.1.1
General Changes
16.1.1.2
Panel Customizable Changes
16.1.1.3
Show Detail Frame
16.1.2
External Application Changes
16.1.2.1
Overview of External Applications Changes in Oracle Application Server 10
g
and Oracle Fusion Middleware 11
g
16.1.2.2
External Application Upgrade Changes
16.1.3
Portlet Component Changes
16.1.3.1
Portlet Tag Changes
16.1.3.2
Attribute Changes
16.2
Content Integration Connections: Migration of Credentials to External Applications
16.3
Preconfigured Portlet Producers: Customization Store's Location
16.3.1
WSRP Portlet Producers
16.3.2
Web Clipping Portlet Producer
16.3.3
OmniPortlet and other PDK-Java Portlet Producers
16.3.4
OmniPortlet Repository Changes
16.4
Migration of JSR 168 Portlet Producers to JSR 286: Handling of Portlet Elements
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
Upgrading Oracle Business Rules Dictionaries and Projects
B.1
Using Oracle JDeveloper to Migrate an Oracle Business Rules Dictionary
B.2
Using Rule Migrator Tool to Migrate an Oracle Business Rules Dictionary
B.3
Using MigrateRuleRepository with Oracle Business Rules SDK to Migrate a Dictionary
B.3.1
How to Migrate a Dictionary with Oracle Business Rules SDK
B.3.2
What You May Need to Know About the MigrateRuleRepository API
B.3.2.1
Input Properties
B.3.2.2
Output Properties
B.4
Oracle Business Rules Manual Migration Tasks
B.4.1
How to Migrate JAXB 1.0 to JAXB 2.0
B.4.2
How to Migrate RL Functions
B.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.