Migrating oracle service oriented architecture(SOA) suite 10g to 11g

1. MiddleWare M MI IG GR RA AT TI IN NG G O OR RA AC CL LE E S SE ER RV VI IC CE E- -O OR RI IE EN NT TE ED D A AR RC CH HI IT TE EC CT TU UR RE ES S ( (S SO OA A) )S SU UI IT TE E 1 10 0G G T TO O 1 11 1 G G Manoj Machiwal, Jade Global Inc ABSTRACT In This white paper, you will learn how to plan and execute a successful SOA 10g to SOA 11g Migration. You will also learn commonly faced challenges, Risks for such project and how to overcome and mitigate the risks. In the end there will be some tips and tricks will be shared for execution along with a customer case study. TARGET AUDIENCE This whitepaper concentrates on the individuals who are experienced on the development or administrator with Oracle SOA suite 10g and 11g. Oracle SOA Architects Oracle SOA Developers Oracle SOA Suite Administrators EXECUTIVE SUMMARY There have been significant changes between SOA 10g and 11g Environment. In this white paper we will brief the differences between 10g and 11g environments and highlight the best practices for such migration along with a customer case study. In Brief we will explain about the following topics as below : • • • • • • • • SOA Suite 10g and 11g Architecture Comparison High-Level Upgrade Steps Setting Up SOA Suite 11g Environment Oracle BPEL/ESB Projects Migration BPEL Instance migration Oracle BAM Migration Case Study & Lessons Learnt Common Deployment Issues and Best Practices 1 Session #113

2. MiddleWare BACKGROUND SOA Suite 10g and 11g Architecture Comparison There has been significant changes happened between SOA suite 10g and 11g, below table summarizes the diffeences between 10g and 11g environment. These changes should be well studied and considered while migrating applications from 10g to 11g environments. Below diagram shows the pictorial representaion of archictechure difference between soa 10g and 11g environments. 2 Session #113

3. MiddleWare High Level Upgrade Steps               Review Concepts in the Oracle Fusion Middleware Upgrade Planning Guide Review the Starting Points and Topologies for 11g Prepare a Database for the SOA and WebCenter Schemas Consider a strategy for BPEL Long-Running Processes Install the 11g SOA, WebCenter, or ADF, and create the Middleware home. Use the Upgrade Assistant to Upgrade the SOA Schemas Perform Any WebLogic Server Configuration Tasks to Support Your Applications Perform Any Manual SOA or WebCenter Configuration Tasks Install and Configure an 11g Web Tier Use the Upgrade Assistant to Upgrade the Web Tier Components Install and Configure Oracle JDeveloper 11g Open and Migrate Your Applications with Oracle JDeveloper Release 11g Recompile the Application Projects Implement any other code changes required for the application to run successfully on Oracle Fusion Middleware 11g   Redeploy Your Applications on Oracle Fusion Middleware 11g Verify the Redeployed Applications Below is a flow diagram which represents the high level upgrade steps for SOA 10g to 11g Migration. 3 Session #113

4. MiddleWare Setting up SOA suite 11g Environment Below are some high level steps for setting up SOA suite 11g environment • SOA Suite Topology Before we can begin the upgrade process, we need to decide upon a new topology for new fusion middleware 11g environment. • Upgrade the Repository Database We have to ensure that database which is hosting SOA suite schemas are supported by SOA suite 11g. If not, we have to plan to upgrade the database or plan for a new repository database. • RCU We have to use the Repository Creation Utility to install the schemas in the database. Repository Creation Utility is a graphical and command-line tool used to create and manage Oracle Fusion Middleware database schemas in your database. Running the Repository Creation Utility in Preparation for an Oracle SOA Suite Upgrade 4 Session #113

5. MiddleWare To start the Repository Creation Utility (RCU), we run the rcu command, which is in the root directory of the Repository Creation Utility CD-ROM or (if we have already installed the Oracle SOA Suite software on disk) in the bin directory of the Oracle SOA Suite Oracle home. Selecting the Schemas Required for a Oracle SOA Suite Upgrade We can use the Repository Creation Utility to install the schemas required for all of the Oracle Fusion Middleware software components that require a schema. However, there is no need to install all the schemas unless we plan to install a complete Oracle Fusion Middleware environment and we plan to use the same database for all the Oracle Fusion Middleware component schemas. For a Oracle SOA Suite upgrade, we must select the following schemas when you prompted by the Repository Creation Utility (as shown in figure below):  Select the Metadata Services schema in the AS Common Schemas category. This schema supports Oracle Fusion Middleware Metadata Services (MDS), which is required by some Oracle Fusion Middleware components, as well as for custom applications that support MDS. For more information, see "Understanding the MDS Repository" in the Oracle Fusion Middleware Administrator's Guide.  Select the entire SOA Infrastructure category of schemas. These schemas are required for the Oracle SOA Suite components. 5 Session #113

6. MiddleWare • Install and Configure SOA Suite 11g Middle Tiers This step will have following high level tasks 1.Install Oracle WebLogic Server and create the Middleware home 2.Install the Oracle SOA Suite software and create the Oracle SOA Suite Oracle home 3.Configure the Oracle SOA Suite domain 4.Start the Oracle WebLogic Server domain 5.Verify the installation Below is the diagram which reflects at high level for setting up an SOA suite 11g environment. 6 Session #113

7. MiddleWare Oracle BPEL/ESB Projects Migration Approaches There are many different approach can be used for migrating BPEL and ESB Projects from SOA suite 10g to 11g.  Upgrade in JDeveloper o It’s a good approach, if we are just migrating one project, however we need to analyze the warnings in log files generated during upgrade process.  Command Line Upgrade o Can not upgrade whole application o Usually upgraded directory is different than the source directory o It does not upgrade .jpr files 7 Session #113

8. MiddleWare o HTTP WSDL references to project must be accessible during upgrade  Upgrade using ant o We have to make sure all environment variables are correctly set. o Upgrade an 10g ESB service to an 11g composite application with mediator component o Merge several 10g BPEL processes to an 11g Composite application BPEL Instance Migration Upgrade approaches do not support BPEL Instances and audit trail migration Two choices for cutting over long-running BPEL processes to 11g – Side by side upgrade • 10g and 11g systems run side by side • 10g system has long-running process in retired state • Clients are switched over to 11g • 10g system continues running until all callbacks arrive to complete the long running processes • 10g system is decommissioned – Grace period cutover • 10g system has long-running process in retired state • After a grace period all long-running processes in 10g are killed • 10g system is decommissioned • 11g system is brought up in production Oracle BAM Migration To upgrade the BAM schema: 1.Stop the administration server and the managed servers in the Oracle WebLogic Server domain that hosts the BAM application. 2.Start the Upgrade Assistant 3.Select BAM Schema on the Specify Operation screen ( as in diagram below). 8 Session #113

9. MiddleWare 4.Refer to table below description of the Upgrade Assistant screens that require input from you during a Oracle BAM schema upgrade and the options on each screen. 5.After the Specify Schema Name screen, the Upgrade Assistant performs the following tasks and provides the progress on each task: o Examines the components and schemas to be upgraded and verifies that they can be upgraded successfully. o Provides a summary of the components to be upgraded so you can verify that Upgrade Assistant is upgrading the components and schemas you expect. o Provides a progress screen so you can see the status of the upgrade as it proceeds. o Alerts you of any errors or problems that occur during the upgrade. See Also: "Troubleshooting Your Upgrade" in the Oracle Fusion Middleware Upgrade Planning Guide for specific instructions for troubleshooting problems that occur while running the Upgrade Assistant o Displays the End of Upgrade screen, which confirms that the upgrade was complete. Upgrade Assistant Screens That Require Input during a BAM Schema Upgrade 9 Session #113

10. MiddleWare Upgrade Assistant Screen Description Specify Source Database Use this screen to enter the database connection details for the database that contains the Oracle BAM 10g schema. Specify Target Database Details Use this screen to enter the database connection details for the database that contains the Oracle BAM 11g schema that you created with the Oracle Fusion Middleware Repository Creation Utility. Specify Schema Name Use this screen to select the Oracle BAM 11g schema and enter the password for the BAM schema. This is the Oracle BAM schema password that you set in the Repository Creation Utility when you installed the schema in the database. Examining Components This page shows the status of examination phase, where the upgrade assistant verifies the source and target schema. Testing Considerations • Application flow testing • Business and Application team availability • Preparing Testing data • External Integrations – Identify inbound and Outbound touch points – Identify the teams ( application, networking etc.) • Connection Pools testing • File Transfer testing • Security Considerations Case Study The Client • A leading provider of optical products and test and measurement solutions for the communications industry • Revenue ~2 Billion Dollar 10 Session #113

11. MiddleWare Technologies • Oracle EBS 11.5.10.2 • SOA 11g • OnDemand Siebel CRM • Salesforce.com • External Integrations – B2B Vendors Challenges • Precision provided Web Service had Http binding, with Complex input & output. SOA 11g does not support Complex data type for Http Binding Web Service • Custom JAVA Client was developed in 10g using Flexera provided Web Service. 10g Client could not be used directly in 11g • AIA version was not certified for latest SOA release Key Requirements • Oracle EBS and Precision Integration for Shipment (create/void shipment & shipment confirmation) • Oracle EBS and Flexera (3rd party System – On Demand) Integration for Sales Orders(for license entitlements only) • EBS and CRM OnDemand Integration using AIA Framework The Solution • Use HttpClient (in JAVA Embed) for invoking Http Web Service with Complex data type • Regenerate Web Service Client in 11g & depending on customization, • Customize Custom JAVA Client in 11g OR • Develop new SOA Artifacts in 11g based on External web service only • Migrate to latest certified AIA version and retrofit customizations Lessons Learnt • Migration can be as simple as importing 10g resources in 11g JDeveloper, customizing existing SOA artifacts to fresh SOA artifacts development • Limitations of SOA can be overcome with JAVA • Estimations should be provided based on number of integration points, binding, accessibility better to postpone estimating efforts after initial analysis of integration touch points 11 Session #113

12. MiddleWare • Every migration is new and unique in its own Common Deployment Issues Base64 encoding/decoding class issue BPEL compilation might fail if we have used com.collaxa.common.util.Base64Decoder/Base64Encoder classes in 10g.The import of com.collaxa.common.util.Base64Decoder/Base64Encoder class should be changed to oracle.soa.common.util.Base64Decoder/Base64Encoder Recursive Import issue The deployment of the migrated composite might fail if the composite invokes the partner WSDL that is having the duplicate import of same WSDL with the following error “WSDL contains recursive import loop”. RuntimeFault.wsdl and ws-addressing.xsd cannot found The http://xxxxx:xxxx/orabpel/xmllib/RuntimeFault.wsdl and http://xxxxx:xxxx/orabpel/xmllib/ws-addressing.xsd could not be found after migration. In 11g these files are moved to MDS .change the location manually to the following MDS location in the code oramds:/soa/shared/bpel/RuntimeFault.wsdl and oramds:/soa/shared/common/ ws-addressing.xsd Best Practices Before Migration • Ensure that 10g projects are up and running on latest SOA 10g release • Install Jdeveloper using SOA extensions • Install latest SOA Suite • Configure all necessary resources • Start with a Pilot Project, rather than a Big Bang Approach During and After Migration • Recompile the migrated projects • Think about rearranging artifacts to corresponding folders; also, only change the reference as needed • Run 11g Adapter configuration wizard for each adapter to verify the adapter configuration • Create JDeveloper Applications and Projects REFERENCES Oracle® Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF 11g Release 1 (11.1.1.6.0) 12 Session #113