Oracle® Fusion Middleware

Application Adapter Upgrade Guide for Oracle WebLogic Server

11g Release 1 (11.1.1.3.0)

E17392-03

November 2010

Oracle Fusion Middleware Application Adapter Upgrade Guide for Oracle WebLogic Server, 11g Release 1 (11.1.1.3.0)

E17392-03

Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved.

Primary Author: Stefan Kostial

Contributing Authors: Sunil Gopal, Marian Jones, Vikas Anand, Sunil Wadhwa, Vishal Saxena, Vimmika Dinesh

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Figures

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 General Upgrade Guidelines

- Upgrading a 10.1.3.x Outbound Process to 11g

- Prerequisites

- Overview of 10.1.3.x BPEL JCA Outbound Workflow Process

- Creating an Outbound BPEL Process Project

- Migrating the 10.1.3.x BPEL JCA Outbound Process to a 11g Workflow Process

- Prerequisites

- Overview of Migration to 11g BPEL JCA Outbound Workflow Process

- Migrating an Outbound BPEL Process Project

- Post-Upgrade Requirement

- Upgrading a 10.1.3.x Inbound Process to 11g

- Overview of 10.1.3.x BPEL JCA Inbound Workflow Process

- Creating an Inbound BPEL Process Project

- Migrating an Inbound BPEL Process Project

- Post-Upgrade Requirement

- Migrating Oracle Service Bus 10.1.3.x Outbound and Inbound Processes to 11g

- Exporting the Configured Processes From Oracle Service Bus 10.1.3.x

- Importing the Exported Processes to Oracle Service Bus 11g

- Additional Modifications for Imported Processes in Oracle Service Bus 11g

- Imported J2CA Inbound Processes

- Imported BSE Outbound Processes

- Upgrading 11g PS1 Outbound and Inbound Processes to 11g PS2

- Additional Modifications for Migrated Processes in 11g PS2

- Overview of Oracle Upgrade Patches

2 Oracle Application Adapter for SAP R/3 Upgrade Guidelines

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

3 Oracle Application Adapter for Siebel Upgrade Guidelines

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

4 Oracle Application Adapter for PeopleSoft Upgrade Guidelines

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

5 Oracle Application Adapter for J.D. Edwards OneWorld Upgrade Guidelines

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Glossary

Index

List of Figures

- 1-1 New Project Option

- 1-2 New Gallery Dialog

- 1-3 BPEL Project Creation Wizard - Project Settings Page

- 1-4 BPEL Project Creation Wizard - I/O Elements Page

- 1-5 Select Schema Dialog

- 1-6 Type Chooser Dialog

- 1-7 BPEL Project Creation Wizard - I/O Elements Page

- 1-8 Type Chooser Dialog

- 1-9 Import Schema File Dialog

- 1-10 Import Schema Dialog

- 1-11 Import Schema File Dialog

- 1-12 Type Chooser Dialog

- 1-13 BPEL Project Creation Wizard - I/O Elements Page

- 1-14 Standard BPEL Outbound Process

- 1-15 Outbound BPEL Process Project

- 1-16 Open Icon in Oracle JDeveloper 11g

- 1-17 Open Dialog

- 1-18 Welcome Page of the Migration Wizard

- 1-19 Confirmation Page

- 1-20 Component IDs Page

- 1-21 Finish Page of the Migration Wizard

- 1-22 Successful Migration Status Message

- 1-23 A Migrated 10.1.3.x Project in the 11g Environment

- 1-24 Messages Log Tab

- 1-25 Input XML in the Request Tab

- 1-26 Output XML Received in the Response Tab

- 1-27 Source of the JCA Properties File

- 1-28 New Project Option

- 1-29 New Gallery Dialog

- 1-30 BPEL Project Creation Wizard - Project Settings Page

- 1-31 A Standard BPEL Inbound Process

- 1-32 Messages Tab Showing Deployment Was Successful

- 1-33 Oracle JDeveloper 11g Open Icon

- 1-34 Open Dialog

- 1-35 Migration Wizard

- 1-36 Confirmation Page

- 1-37 Component IDs Page

- 1-38 Finish Page

- 1-39 Migration Successfully Completed Message

- 1-40 Migrated 10.1.3.x Project in the 11g Environment

- 1-41 JCA Properties File Source

- 1-42 Messages Tab - BPEL Process Object Compiled and Deployed Successfully

- 1-43 JCA Properties File Source

- 1-44 Oracle Service Bus Console Home Page

- 1-45 Create Button in Change Center Area

- 1-46 System Administration Option

- 1-47 Export Resources Option

- 1-48 Resource Summary Area and Export Button

- 1-49 Opening sbconfig.far Dialog

- 1-50 The sbconfig.jar File Saved Successfully in a File System Directory Location

- 1-51 Oracle Service Bus Console Home Page

- 1-52 Create Button in the Change Center Area

- 1-53 System Administration Option

- 1-54 Import Resources Option From Import/Export Area

- 1-55 Import Resources Page

- 1-56 Browse Button on the Import Resources Page

- 1-57 Import Button in the Resource Summary Area

- 1-58 Processing Status Indicator

- 1-59 Import Process Success Message and Activate Button

- 1-60 Activate Session Page

- 1-61 Project Explorer Option

- 1-62 Imported Project Folders

- 1-63 Expanded mySAP Project Folder

- 1-64 Imported Business Services

- 1-65 Imported Proxy Services

- 1-66 Imported WSDL Files

- 1-67 ProxyService Folder

- 1-68 JCA Binding File

- 1-69 JCA Binding Text View

- 1-70 The <record-converter> Element

- 1-71 Save Button

- 1-72 WSDL File Selected for the Outbound Process

- 1-73 Text View Tab

- 1-74 The Edit a WSDL Resource Page

- 1-75 Transport Configuration Section

- 1-76 Oracle JDeveloper Toolbar

- 1-77 Open Dialog

- 1-78 Open Warning Dialog

- 1-79 Migration Status Message

- 1-80 Migrated Sample Project

- 1-81 Deploy Menu Option

- 1-82 Deployment Action Page

- 1-83 Deploy Configuration Page

- 1-84 Select Server Page

- 1-85 SOA Servers Page

- 1-86 Summary Page

- 1-87 Deployment Log

- 1-88 Input XML in XML View

- 1-89 Received Output XML

- 1-90 Opened Migrated Project

- 1-91 BSE Outbound WSDL File

Preface

Oracle Fusion Middleware Application Adapter Upgrade Guide for Oracle WebLogic Server describes how to upgrade Oracle Application Adapters for Oracle WebLogic Server from 10.1.3.x to 11g.

Audience

The Oracle Fusion Middleware Application Adapter Upgrade Guide for Oracle WebLogic Server is intended for system administrators who are upgrading Oracle Application Adapters for Oracle WebLogic Server from 10.1.3.x to 11g.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle Enterprise Repository 11g Release 1 (11.1.1.3.0) documentation set:

- Oracle Fusion Middleware Application Adapters Installation Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter Best Practices Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter for SAP R/3 User's Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter for SAP R/3 (SAP JCo 3.0) User's Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter for Siebel User's Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter for PeopleSoft User's Guide for Oracle WebLogic Server

- Oracle Fusion Middleware Application Adapter for J.D. Edwards OneWorld User's Guide for Oracle WebLogic Server

- Oracle's Unified Method (OUM)
A wealth of additional Governance information can be found within Oracle's Unified Method (OUM). OUM can be used by Oracle employees, Oracle Partner Network Certified Partners or Certified Advantage Partners, and Clients who either participate in the OUM Customer Program or are engaged on projects where Oracle provides consulting services. OUM is a web-deployed toolkit for planning, executing and controlling software development and implementation projects.

For more information about OUM, see the OUM FAQ at

http://my.oracle.com/portal/page/myo/ROOTCORNER/KNOWLEDGEAREAS1/BUSINESS_PRACTICE/Methods/Learn_about_OUM.html

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 General Upgrade Guidelines

This chapter lists and describes general upgrade guidelines that are common to all Oracle Application Adapters for Oracle WebLogic Server. It contains the following topics:

- Upgrading a 10.1.3.x Outbound Process to 11g

- Upgrading a 10.1.3.x Inbound Process to 11g

- Migrating Oracle Service Bus 10.1.3.x Outbound and Inbound Processes to 11g

- Upgrading 11g PS1 Outbound and Inbound Processes to 11g PS2

- Overview of Oracle Upgrade Patches

Upgrading a 10.1.3.x Outbound Process to 11g

This section describes how to upgrade a 10.1.3.x outbound process to 11g.

Note:
For demonstration purposes, Oracle Application Adapter for SAP R/3 is used as an example.

The 10.1.3.x BPEL and Mediator projects for the application adapters should not have any warning or error messages during compilation and deployment with 10.1.3.x version. If any warning or error messages are present, then they must be corrected before migrating the projects to 11g. If you have followed the 10.1.3.x user guides for creating a BPEL or Mediator project, then you would see two warning messages in Oracle JDeveloper at the time of compilation deployment. These warning messages are not acceptable in the 11g environment. Those warning messages are shown because the assign statements were assigning the BPEL/ESB project namespace to the adapter's namespace. This is an incompatible namespace assignment. As a result, any warning or error messages in 10.1.3.x projects must be corrected before migrating to 11g. This section describes how to create 10.1.3.x projects without the warning messages.

Prerequisites

Take a note of the adapter targets and channels that were created in the 10.1.3.x Application Explorer for your application adapters. For the migration to be successful, you must create the same adapter targets and channels in the 11g environment using the Application Explorer.

Before continuing, ensure that the following components are available:

1. Using Application Explorer, export the schemas for a particular business object for Oracle Application Adapter for SAP R/3 into the default location.

2. Using Application Explorer, generate a JCA outbound WSDL for a particular business object for Oracle Application Adapter for SAP R/3.

Overview of 10.1.3.x BPEL JCA Outbound Workflow Process

1. Create an outbound BPEL process project.

2. Configure an outbound BPEL process.

3. Deploy the outbound BPEL process project.

4. Invoke the input XML using the BPEL console.

Creating an Outbound BPEL Process Project

To create an outbound BPEL process project:

1. As shown in Figure 1-1, start Oracle JDeveloper 10.1.3.4.

Figure 1-1 New Project Option

2. Click the Application Navigator tab and select New Project from the context menu.
The New Gallery dialog is displayed, as shown in Figure 1-2.

Figure 1-2 New Gallery Dialog

3. Select the BPEL Process Project and then click OK.
The BPEL Project Creation Wizard - Project Settings page is displayed, as shown in Figure 1-3.

Figure 1-3 BPEL Project Creation Wizard - Project Settings Page

4. Enter a name for the new BPEL process project in the Name field.

5. Select Synchronous BPEL Process from the Template Type list and click Next.
The BPEL Project Creation Wizard - I/O Elements page is displayed, as shown in Figure 1-4.

Figure 1-4 BPEL Project Creation Wizard - I/O Elements Page

6. Click the Browse icon to the right of the Input Schema Element field.
The Select Schema dialog is displayed, as shown in Figure 1-5.

Figure 1-5 Select Schema Dialog

7. Navigate to the default exported schema location:

<soadp1>\adapters\application\tools

8. Select the request XML schema file (.xsd) for the corresponding business object and click Open.
The Type Chooser dialog is displayed, as shown in Figure 1-6.

Figure 1-6 Type Chooser Dialog

9. Expand Imported Schemas, the request XML schema (for example, GetDetail_request.xsd), and then the method (for example, CompanyCode.GetDetail).

10. Click OK.
You are returned to the BPEL Project Creation Wizard - I/O Elements page, as shown in Figure 1-7.

Figure 1-7 BPEL Project Creation Wizard - I/O Elements Page

11. Click the Browse icon to the right of the Output Schema Element field.
The Type Chooser dialog is displayed, as shown in Figure 1-8.

Figure 1-8 Type Chooser Dialog

12. Click the Import Schema icon.
The Import Schema File dialog is displayed, as shown in Figure 1-9.

Figure 1-9 Import Schema File Dialog

13. Click the Browse icon.
The Import Schema dialog is displayed, as shown in Figure 1-10.

Figure 1-10 Import Schema Dialog

14. Navigate to the default exported schema location:

<soadp1>\adapters\application\tools

15. Select the response XML schema file (.xsd) for the corresponding business object and click Open.
You are returned to the Import Schema File dialog, as shown in Figure 1-11.

Figure 1-11 Import Schema File Dialog

16. Uncheck the Add to Project option.

17. Click OK.
The Type Chooser dialog is displayed, as shown in Figure 1-12.

Figure 1-12 Type Chooser Dialog

18. Expand Imported Schemas, the response XML schema (for example, GetDetail_response.xsd), and then the method (for example, CompanyCode.GetDetail.Response).

19. Click OK.
You are returned to the BPEL Project Creation Wizard - I/O Elements page, as shown Figure 1-13.

Figure 1-13 BPEL Project Creation Wizard - I/O Elements Page

20. Click Finish.

Figure 1-14 Standard BPEL Outbound Process

21. Continue with the creation of a standard BPEL outbound process using Partnerlink, Invoke, and Assign components.

22. Compile the outbound BPEL process project, as shown in Figure 1-15.

Figure 1-15 Outbound BPEL Process Project

23. Verify that there are no error or warning messages during compilation.

24. Deploy the outbound BPEL process project.

25. After the deployment is successful, go to the BPEL console and execute the deployed process.
A successful response is received.

Migrating the 10.1.3.x BPEL JCA Outbound Process to a 11g Workflow Process

This section describes how to migrate the 10.1.3.x BPEL JCA outbound process to a 11g workflow process.

Note:
For demonstration purposes, Oracle Application Adapter for SAP R/3 is used as an example.

Prerequisites

Before continuing, ensure that you copy and paste the 10.1.3.x outbound BPEL Process Project to the 11g system location.

Overview of Migration to 11g BPEL JCA Outbound Workflow Process

1. Open an application.

2. Migrate the 10.1.3.x BPEL JCA outbound process to 11g.

3. Deploy the BPEL process project.

4. Invoke the input XML using the Oracle Enterprise Manager console.

Migrating an Outbound BPEL Process Project

To migrate an outbound BPEL process project:

1. Start Oracle JDeveloper 11g, as shown in Figure 1-16.

Figure 1-16 Open Icon in Oracle JDeveloper 11g

2. Select an available application (for example, FEB10) and click Open from the tool bar.
The Open dialog is displayed, as shown in Figure 1-17.

Figure 1-17 Open Dialog

3. Open the 10.1.3.x project (for example, Isdsrv2_CC_GD_jca) and select the .jpr extension file (for example, Isdsrv2_CC_GD_jca.jpr).

4. Click Open.
The Migration Wizard is displayed, as shown in Figure 1-18.

Figure 1-18 Welcome Page of the Migration Wizard

5. Click Next.
The Confirmation page is displayed, as shown Figure 1-19.

Figure 1-19 Confirmation Page

6. Verify that Yes is selected (default) and click Next.
The Component IDs page is displayed, as shown in Figure 1-20.

Figure 1-20 Component IDs Page

7. Accept the default values and click Next.
The Finish page is displayed, as shown in Figure 1-21.

Figure 1-21 Finish Page of the Migration Wizard

8. Click Finish. The following message is displayed, as shown in Figure 1-22.

Figure 1-22 Successful Migration Status Message

9. Click OK.
As shown in Figure 1-23, the 10.1.3.x project is now available in your 11g environment.

Figure 1-23 A Migrated 10.1.3.x Project in the 11g Environment

10. Expand the migrated project in the left page (for example, Isdsrv2_CC_GD_jca) and double-click the composite.xml file to verify that the project opens without any errors.

11. Click Save.

12. Compile and then deploy the migrated BPEL process project, as shown in Figure 1-24.

Figure 1-24 Messages Log Tab

13. Verify that there are no error or warning messages during compilation and deployment.

14. After the deployment is successful, as shown in Figure 1-25, go to the Oracle Enterprise Manager console and execute the deployed process either in Tree View or XML View and get the successful response.
Input XML in XML View

Figure 1-25 Input XML in the Request Tab

Output XML that is received

Figure 1-26 Output XML Received in the Response Tab

Post-Upgrade Requirement

The following changes must be made for every outbound ESB and BPEL process after the corresponding project is migrated to 11g.

1. Expand the migrated project and double-click the composite.xml file.

2. Click source.

3. Navigate to the reference section, check for the .jca file that has the naming convention as xxxx_iway.jca and replace with xxxx_iway_3P.jca (adding _3P as a suffix).
Original:

<reference ui:wsdlLocation="isdsrv15_eaicreate_node_invoke.wsdl" name="create_node"><interface.wsdl interface="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv15/create_node#wsdl.interface(create_nodePortType)" xmlns:ns="http://xmlns.oracle.com/sca/1.0"/><binding.jca config="create_node_iway.jca"/></reference>

Modified:

<reference ui:wsdlLocation="isdsrv15_eaicreate_node_invoke.wsdl" name="create_node"><interface.wsdl interface="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv15/create_node#wsdl.interface(create_nodePortType)" xmlns:ns="http://xmlns.oracle.com/sca/1.0"/><binding.jca config="create_node_iway_3P.jca"/></reference>

Figure 1-27 Source of the JCA Properties File

4. Open the project folder and rename the same .jca properties file by adding _3P as a suffix in the .jca file (for example, create_node_iway_3P.jca).

Upgrading a 10.1.3.x Inbound Process to 11g

This section describes how to upgrade a 10.1.3.x inbound process to 11g.

Note:
For demonstration purposes, Oracle Application Adapter for SAP R/3 is used as an example.

As a requirement, you must create the same adapter targets and channels in the 11g environment using Application Explorer that you had created in the 10.1.3.x environment. Any change in the adapter target or channel can cause issues for the projects to work in 11g environment.

Overview of 10.1.3.x BPEL JCA Inbound Workflow Process

1. Using Application Explorer, generate a 10.1.3.x JCA inbound WSDL document for Oracle Application Adapter for SAP R/3.

2. Create a 10.1.3.x BPEL JCA inbound process using Oracle JDeveloper 10.1.3.x and deploy it successfully.

3. Trigger the event messages from the ERP system (for example, SAP GUI) and verify that successful instances are received for the deployed process in the BPEL console.

4. Migrate the 10.1.3.x BPEL JCA inbound process to 11g using Oracle JDeveloper 11g.

5. Remove the following line from the JCA properties file in the migrated project and deploy it successfully:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

6. Trigger the event messages from the ERP system (for example, SAP GUI) and ensure that successful instances are received in the Oracle Enterprise Manager console.

Creating an Inbound BPEL Process Project

To create an inbound BPEL process project:

1. As shown in Figure 1-28, start Oracle JDeveloper 10.1.3.4.

Figure 1-28 New Project Option

2. Click the Application Navigator tab and select New Project from the context menu.
The New Gallery dialog is displayed, as shown inFigure 1-29.

Figure 1-29 New Gallery Dialog

3. Select the BPEL Process Project and then click OK.
The BPEL Project Creation Wizard - Project Settings page is displayed, as shown in Figure 1-30.

Figure 1-30 BPEL Project Creation Wizard - Project Settings Page

4. Enter a name for the new BPEL process project in the Name field.

5. Select Empty BPEL Process from the Template Type list and click Finish. Figure 1-31 shows the BPEL inbound process.

Figure 1-31 A Standard BPEL Inbound Process

6. Continue with the creation of a standard BPEL inbound process using Partnerlink and Receive components.

7. Compile the inbound BPEL process project, as shown in Figure 1-32.

Figure 1-32 Messages Tab Showing Deployment Was Successful

8. Verify that there are no error or warning messages during compilation.

9. Deploy the inbound BPEL process project.

10. After the deployment is successful, trigger the event messages from the ERP system (for example, SAP GUI).
The successful instances for the deployed process are received in the BPEL console.

Migrating an Inbound BPEL Process Project

Before continuing, ensure that you copy and paste the 10.1.3.x inbound BPEL Process Project to the 11g system location.

To migrate an inbound BPEL process project:

1. As shown in Figure 1-33, start Oracle JDeveloper 11g.

Figure 1-33 Oracle JDeveloper 11g Open Icon

2. Select an available application and click Open from the tool bar.
The Open dialog is displayed, as shown in Figure 1-34.

Figure 1-34 Open Dialog

3. Open the 10.1.3.x project and select the .jpr extension file (for example, mysap_matmas_inbound_wsdl_browser_bpel.jpr).

4. Click Open.
The Migration Wizard is displayed, as shown in Figure 1-35.

Figure 1-35 Migration Wizard

5. Click Next.
The Confirmation page is displayed, as shown in Figure 1-36.

Figure 1-36 Confirmation Page

6. Verify that Yes is selected (default) and click Next.
The Component IDs page is displayed, as shown in Figure 1-37.

Figure 1-37 Component IDs Page

7. Accept the default values and click Next.
The Finish page is displayed, as shown in Figure 1-38.

Figure 1-38 Finish Page

8. Click Finish.
The following message is displayed, as shown in Figure 1-39.

Figure 1-39 Migration Successfully Completed Message

9. Click OK.
As shown below in Figure 1-40, the 10.1.3.x project is now available in your 11g environment.

Figure 1-40 Migrated 10.1.3.x Project in the 11g Environment

10. Expand the migrated project in the left page and double-click the composite.xml file to verify that the project opens without any errors.

11. Double-click the JCA properties file that is associated with this project (for example, MATMAS01_iway.jca).

12. Remove the XMLRecordConverter line, as shown in Figure 1-41.

Figure 1-41 JCA Properties File Source

13. Click Save.

14. Compile and then deploy the migrated BPEL process project, as shown in Figure 1-42.

Figure 1-42 Messages Tab - BPEL Process Object Compiled and Deployed Successfully

15. Verify that there are no error or warning messages during compilation and deployment.

16. After the deployment is successful, trigger the event messages from the ERP system (for example, SAP GUI).
The successful instances for the deployed process are received in the Oracle Enterprise Manager console.

Post-Upgrade Requirement

The following changes must be made for every inbound ESB and BPEL process after the corresponding project is migrated to 11g.

1. Expand the migrated project and double-click the composite.xml file.

2. Click source.

3. Navigate to the service section, check for the .jca file that has the naming convention as xxxx_iway.jca and replace with xxxx_iway_3P.jca (adding _3P as a suffix).
Original:

<service ui:wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" name="samp_node"><interface.wsdl interface="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node#wsdl.interface(samp_nodePortType)" xmlns:ns="http://xmlns.oracle.com/sca/1.0"/><binding.jca config="samp_node_iway.jca"/></service>

Modified:

<service ui:wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" name="samp_node"><interface.wsdl interface="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node#wsdl.interface(samp_nodePortType)" xmlns:ns="http://xmlns.oracle.com/sca/1.0"/><binding.jca config="samp_node_iway_3P.jca"/></service>

Figure 1-43 JCA Properties File Source

4. Open the project folder and rename the same .jca properties file by adding _3P as a suffix in the .jca file (for example, samp_node_iway_3P.jca).

Migrating Oracle Service Bus 10.1.3.x Outbound and Inbound Processes to 11g

This section describes how to migrate outbound and inbound J2CA processes and outbound BSE processes from Oracle Service Bus 10.1.3.x to 11g. It contains the following topics:

- Exporting the Configured Processes From Oracle Service Bus 10.1.3.x

- Importing the Exported Processes to Oracle Service Bus 11g

- Additional Modifications for Imported Processes in Oracle Service Bus 11g

Exporting the Configured Processes From Oracle Service Bus 10.1.3.x

This section describes how to export the configured processes from Oracle Service Bus 10.1.3.x.

1. Start the Oracle WebLogic Server for the Oracle WebLogic Server domain that you have configured.

2. Open the Oracle Service Bus console in a Web browser by entering the following URL:

http://host name:port/sbconsole

where host name is the name of the system where Oracle WebLogic Server is running (Oracle Service Bus 10.1.3.x) and port is the port for the domain you are using. The port for the default domain is 7001.

3. Log in to the Oracle Service Bus console using a valid user name and password.
The Oracle Service Bus console home page is displayed, as shown in Figure 1-44.

Figure 1-44 Oracle Service Bus Console Home Page

4. As shown in Figure 1-45, click Create in the Change Center area to start a new Oracle Service Bus session.

Figure 1-45 Create Button in Change Center Area

5. Click System Administration in the left pane, as shown in Figure 1-46.

Figure 1-46 System Administration Option

6. Click Export Resources in the Import/Export area, as shown in Figure 1-47.

Figure 1-47 Export Resources Option

7. Ensure that all the available options under Resource Summary are selected (System and default), and then click Export, as shown in Figure 1-48.

Figure 1-48 Resource Summary Area and Export Button

8. Save the sbconfig.jar file, as shown in Figure 1-49.

Figure 1-49 Opening sbconfig.far Dialog

9. As shown in Figure 1-50, verify that the sbconfig.jar is saved successfully.

Figure 1-50 The sbconfig.jar File Saved Successfully in a File System Directory Location

Note:
The sbconfig.jar file that is exported from Oracle Service Bus 10.1.3.x must be copied to the system where Oracle Service Bus 11g is installed.

Importing the Exported Processes to Oracle Service Bus 11g

This section describes how to import the exported processes to Oracle Service Bus 11g.

Prerequisites

- All the adapter targets and channels that are configured using Application Explorer in an Oracle Service Bus 11g environment must match those in an Oracle Service Bus 10.1.3.x environment.

- All the input and output locations configured for the processes in an Oracle Service Bus 11g environment must match those in an Oracle Service Bus 10.1.3.x environment.

To import the exported processes to Oracle Service Bus 11g:

1. Start the Oracle WebLogic Server for the Oracle WebLogic Server domain that you have configured.

2. Open the Oracle Service Bus console in a Web browser by entering the following URL:

http://host name:port/sbconsole

where host name is the name of the system where Oracle WebLogic Server is running (Oracle Service Bus 11g) and port is the port for the domain you are using. The port for the default domain is 7001.

3. Log in to the Oracle Service Bus console using a valid user name and password.
The Oracle Service Bus console home page is displayed, as shown in Figure 1-51.

Figure 1-51 Oracle Service Bus Console Home Page

4. Click Create in the Change Center area to start a new Oracle Service Bus session, as shown below in Figure 1-52.

Figure 1-52 Create Button in the Change Center Area

5. Click System Administration in the left pane, as shown in Figure 1-53.

Figure 1-53 System Administration Option

6. As shown in Figure 1-54, click Import Resources in the Import/Export area.

Figure 1-54 Import Resources Option From Import/Export Area

The Import Resources page is displayed, as shown in Figure 1-55.

Figure 1-55 Import Resources Page

7. As shown in Figure 1-56, click Browse and select the sbconfig.jar file, which was exported from Oracle Service Bus 10.1.3.x and copied to the local machine.

Figure 1-56 Browse Button on the Import Resources Page

8. Click Next.

9. Select all the options listed in the Resource Summary area and click Import, as shown in Figure 1-57.

Figure 1-57 Import Button in the Resource Summary Area

As shown below in Figure 1-58, the processes are imported.

Figure 1-58 Processing Status Indicator

10. Verify that the success message is displayed and click Activate, as shown in Figure 1-59.

Figure 1-59 Import Process Success Message and Activate Button

The Activate Session page is displayed, as shown in Figure 1-60.

Figure 1-60 Activate Session Page

11. Click Submit.

12. Click Project Explorer after the session is successfully activated, as shown in Figure 1-61.

Figure 1-61 Project Explorer Option

13. As shown below in Figure 1-62, ensure that all the project folders are created.

Figure 1-62 Imported Project Folders

The project folder structure must match the one from Oracle Service Bus 10.1.3.x, since you imported these settings from that environment.

14. Expand an adapter folder, for example, mySAP, as shown in Figure 1-63.

Figure 1-63 Expanded mySAP Project Folder

15. As shown in Figure 1-64, select the Business Service folder.

Figure 1-64 Imported Business Services

Ensure that all the Business Services that were created in the Oracle Service Bus 10.1.3.x environment are included.

16. As shown in Figure 1-65, select the Proxy Service folder.

Figure 1-65 Imported Proxy Services

Ensure that all the Proxy Services that were created in the Oracle Service Bus 10.1.3.x environment are included.

17. Select the WSDLS folder, as shown in Figure 1-66.

Figure 1-66 Imported WSDL Files

Ensure that all the WSDL files that were created in the Oracle Service Bus 10.1.3.x environment are included.

Note:
For applications using Oracle Application Adapter for Siebel, the namespace declaration for the XML payload must use the version that is generated in Oracle Service Bus (OSB) 10g Release 3. The Oracle Application Adapter for Siebel namespace in OSB 10g Release 3 environments is different from Oracle Service Bus 11g environments.
For example:

OSB 10g Release 3:

<sbl:Siebel location="S/BO/Account/Account/query" xmlns:sbl="urn:iwaysoftware:adapter:siebel:oct2004:request">

OSB 11g:

<sbl:Siebel location="S/BO/Account/Account/query" xmlns:sbl="urn:iwaysoftware:adapter:siebel:request:S/BO/Account/Account/query">

Additional Modifications for Imported Processes in Oracle Service Bus 11g

This section describes additional modifications that are required for the imported processes in Oracle Service Bus 11g.

Note:
Imported J2CA outbound processes in Oracle Service Bus 11g work properly and do not require any additional changes. Only BSE outbound processes and J2CA inbound processes require additional changes.

This section contains the following topics:

- Imported J2CA Inbound Processes

- Imported BSE Outbound Processes

Imported J2CA Inbound Processes

This section describes additional modifications that are required for imported J2CA inbound processes in Oracle Service Bus 11g.

1. Select the folder that contains the Proxy Services for your adapter in the Project Explorer, as shown in Figure 1-67.

Figure 1-67 ProxyService Folder

2. Select the appropriate JCA binding file for the inbound process that must be changed, as shown in Figure 1-68.

Figure 1-68 JCA Binding File

The JCA Binding Text View is displayed, as shown in Figure 1-69.

Figure 1-69 JCA Binding Text View

3. Click Edit.

4. Remove the <record-converter> element, as shown in Figure 1-70.

Figure 1-70 The <record-converter> Element

5. As shown in Figure 1-71, click Save.

Figure 1-71 Save Button

Imported BSE Outbound Processes

This section describes additional modifications that are required for imported BSE outbound processes in Oracle Service Bus 11g.

1. Select the folder that contains the WSDL files for your adapter in the Project Explorer.

2. Select the specific WSDL file for the outbound process that must be changed, as shown in Figure 1-72.

Figure 1-72 WSDL File Selected for the Outbound Process

3. Click the Text View tab, as shown in Figure 1-73.

Figure 1-73 Text View Tab

4. Click Edit.
The Edit a WSDL Resource page is displayed, as shown in Figure 1-74.

Figure 1-74 The Edit a WSDL Resource Page

5. Change the <soap:address location> element to point to the system where OSB 11g is running. For example:

<soap:address location="http://OSB10gR3Machine:7001/ibse/IBSEServlet/XDSOAPRouter"/>

must be changed to:

<soap:address location="http://OSB11gMachine:7001/ibse/IBSEServlet/XDSOAPRouter"/

6. Click Save.

7. Select a Business Service that is created for a BSE outbound process in the Project Explorer.

8. Click Edit in the Configuration details tab.

9. In the Transport Configuration section, update the value for the Endpoint URI property to point to the system where OSB 11g is running, as shown in Figure 1-75.

Figure 1-75 Transport Configuration Section

For example:

<soap:address location="http://OSB10gR3Machine:7001/ibse/IBSEServlet/XDSOAPRouter"/>

must be changed to:

<soap:address location="http://OSB11gMachine:7001/ibse/IBSEServlet/XDSOAPRouter"/

Note:
The best option for both changes would be to use localhost instead of an IP address, which eliminates the need for this change.

Upgrading 11g PS1 Outbound and Inbound Processes to 11g PS2

As a prerequisite, ensure that the adapter targets and channels created using Application Explorer for J2CA configurations in the Oracle 11g PS2 environment are identical to those created in the Oracle 11g PS1 environment. For BSE configurations, ensure that the adapter targets and Business Services created using Application Explorer in the Oracle 11g PS2 environment are identical to those created in the Oracle 11g PS1 environment.

In addition, ensure that you copy the Oracle 11g PS1 BPEL and Mediator processes for BSE and J2CA to the Oracle 11g PS2 upgraded system location.

1. Open Oracle JDeveloper 11g Release 1 (11.1.1.3.0).

2. Select an available application (for example, migration-testing) and click Open from the toolbar, as shown in Figure 1-76.

Figure 1-76 Oracle JDeveloper Toolbar

The Open dialog is displayed, as shown in Figure 1-77.

Figure 1-77 Open Dialog

3. Open the 11g PS1 project (for example, jca_mysap_bpel_OB ccgd) and then select the .jpr extension file (for example, jca_mysap_bpel_OB ccgd.jpr).

4. Click Open.
The Open Warning dialog is displayed, as shown in Figure 1-78.

Figure 1-78 Open Warning Dialog

5. Click Yes.
The Migration Status message is displayed, as shown in Figure 1-79.

Figure 1-79 Migration Status Message

6. Click OK.
The Oracle 11g PS1 project is now available in your Oracle 11g PS2 environment, as shown in Figure 1-80.

Figure 1-80 Migrated Sample Project

7. Expand the migrated project in the left pane (for example, jca mysap_bpel_OB_ccgd) and then double-click the composite.xml file to verify that the project opens without any errors.

8. Click Save.

9. Right-click the migrated project, click Deploy, and select the project name from the menu (for example, jca_mysap bpel_OB_ccgd), as shown in Figure 1-81.

Figure 1-81 Deploy Menu Option

The Deployment Action page is displayed, as shown in Figure 1-82.

Figure 1-82 Deployment Action Page

10. Ensure that Deploy to Application Server is selected.

11. Click Next.
The Deploy Configuration page is displayed, as shown in Figure 1-83.

Figure 1-83 Deploy Configuration Page

12. Leave the default values selected and click Next.
The Select Server page is displayed, as shown in Figure 1-84.

Figure 1-84 Select Server Page

13. Select the configured server and click Next.
The SOA Servers page is displayed, as shown in Figure 1-85.

Figure 1-85 SOA Servers Page

14. Select a partition from the Partition column list and click Next.
The Summary page is displayed, as shown in Figure 1-86.

Figure 1-86 Summary Page

15. Review and verify all the available deployment information for your project and click Finish.

16. Verify that there are no error or warning messages during compilation and deployment in the deployment log, as shown in Figure 1-87.

Figure 1-87 Deployment Log

17. After the deployment is successful, open the Oracle Enterprise Manager console and execute the deployed process either in Tree View or XML View to receive a successful response, as shown in Figure 1-88 and Figure 1-89.

Figure 1-88 Input XML in XML View

Figure 1-89 Received Output XML

Additional Modifications for Migrated Processes in 11g PS2

Upgraded J2CA outbound and inbound processes in 11g PS2 function properly and do not require any additional modifications. Only BSE outbound processes require additional modifications, which are described in this section.

1. Once the BSE outbound process is migrated successfully to 11g PS2, double-click the composite.xml file to open the migrated project, as shown in Figure 1-90

Figure 1-90 Opened Migrated Project

2. Double-click the BSE outbound WSDL file and then click the Source tab, as shown in Figure 1-91

Figure 1-91 BSE Outbound WSDL File

3. Change the <soap:address location> element to point to the system where 11g PS2 is running.
For example:

<service name="mysap_isdsrv2_compcode_getdetail">        <documentation/><port name="mysap_isdsrv2_compcode_getdetailSoap1" binding="tns:mysap_isdsrv2_compcode_getdetailSoap"><soap:address location="http://172.19.95.190:8001/ibse/IBSEServlet/XDSOAPRouter"/>        </port>    </service></definitions>

Note:
The best option for both changes is to use localhost instead of an IP address, which eliminates the need for this change.

4. Save and deploy the process.

Overview of Oracle Upgrade Patches

This section provides an overview of Oracle upgrade patches.

BUG 9481515 Outbound

This patch must be applied when an ESB outbound process is created by selecting WSDL from Service Explorer in the Custom Adapter Service.

Open the project folder and edit the DefaultSystem_CustomAdapter ServiceName.esbsvc file (for example, DefaultSystem_isdsrv2_cc_gd.esbsvc) by providing the system IP address and port number (for example, 192.168.128.122:80) of the 10.1.3.4 WSDL generated system in the <wsdlURL> section that is located within <serviceDefinition>:

<serviceDefinition><wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/isdsrv2_CC_GetDetail_invoke.wsdl?wsdl</wsdlURL>----------------------</endpointDefinition></serviceDefinition>

BUG 9481515 Inbound

This patch must be applied when an ESB inbound process is created by selecting WSDL from Service Explorer in the Custom Adapter Service.

Open the project folder and edit the files DefaultSystem_CustomAdapterServiceName.esbsvc (for example, DefaultSystem_matmas01_esb.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc (for example, DefaultSystem_matmas01_esb_RS.esbsvc) by providing the system IP address and port number (for example, 192.168.128.122:80) of the 10.1.3.4 WSDL generated system in the <wsdlURL> section:

1. DefaultSystem_matmas01_esb.esbsvc

<interface> <wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ MATMAS01_receive.wsdl?wsdl</wsdlURL>------------------</interface>

2. DefaultSystem_matmas01_esb_RS.esbsvc

<serviceDefinition><wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ MATMAS01_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

BUG 9411107

This patch must be applied when an ESB inbound process is created only for the Oracle Application Adapter for PeopleSoft when selecting the WSDL from the local file system and from the Service Explorer.

Apply this patch on the11g system and migrate the ESB inbound process created for the Oracle Application Adapter for PeopleSoft.

2 Oracle Application Adapter for SAP R/3 Upgrade Guidelines

This chapter lists and describes upgrade guidelines that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and generate an outbound WSDL for this object.

3. Restart the server.

4. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound ESB Project.

5. In the Custom Adapter service, select the outbound WSDL from the local file system.

6. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

7. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

8. Copy the deployed ESB project into the 11g system.

9. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

10. Once the project is migrated, a successful message is received in Oracle JDeveloper.

11. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

12. Save and then deploy the migrated ESB project.

13. Ensure that there are no error or warning messages during the deployment process.

14. Once the deployment is successful, navigate to the input folder and paste the input XML file.
The successful response XML is received in the specified output folder.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and generate an outbound WSDL for this object.

3. Restart the server.

4. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound ESB Project.

5. In the Custom Adapter service, select the outbound WSDL using Service Explorer.

6. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

7. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

8. Copy the deployed ESB project into the 11g system.

Note:
There is a patch BUG 9481515 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT FOR ALL ADPATERS New issue on Migration of ESB processes. For more information, see "BUG 9481515 Outbound" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

9. Open the project folder and edit the DefaultSystem CustomAdapter ServiceName.esbsvc file (for example, DefaultSystem_isdsrv2_cc_gd.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ isdsrv2_CC_GetDetail_invoke.wsdl?wsdl</wsdlURL><portType xmlns:tns="http://xmlns.oracle.com/pcbpel/iWay/wsdl/MySAP/isdsrv2/GetDetail">tns:GetDetailPortType</portType>----------------------</endpointDefinition></serviceDefinition>

Modified

<serviceDefinition><wsdlURL>isdsrv2_CC_GetDetail_invoke.wsdl</wsdlURL><portType xmlns:tns="http://xmlns.oracle.com/pcbpel/iWay/wsdl/MySAP/isdsrv2/GetDetail">tns:GetDetailPortType</portType>-----------------------</endpointDefinition></serviceDefinition>

10. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

11. Once the project is migrated, a successful message is received in Oracle JDeveloper.

12. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

13. Save and then deploy the migrated ESB project.

14. Ensure that there are no error or warning messages during the deployment process.

15. Once the deployment is successful, navigate to the input folder and paste the input XML file.
The successful response XML is received in the specified output folder.

Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object and generate an inbound WSDL for this object.

4. Restart the server.

5. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

6. In the Custom Adapter service, select the inbound WSDL from the local file system.

7. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

8. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

9. Copy the deployed ESB project into the 11g system.

10. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

11. Once the project is migrated, a successful message is received in Oracle JDeveloper.

12. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

13. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="MATMAS01" adapter="iWay ERP Adapter" wsdlLocation="MATMAS01_receive.wsdl?wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

14. Save and then deploy the migrated ESB project.

15. Ensure that there are no error or warning messages during the deployment process.

16. Trigger the event messages from the ERP system (for example, SAP GUI) and verify that successful response XML files are received in the specified output folder.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object and generate an inbound WSDL for this object.

4. Restart the server.

5. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

6. In the Custom Adapter service, select the inbound WSDL using Service Explorer.

7. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

8. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

9. Copy the deployed ESB project into the 11g system.

Note:
There is a patch BUG 9481515 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT FOR ALL ADPATERS New issue on Migration of ESB processes. For more information, see "BUG 9481515 Inbound" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

10. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_matmas01_esb.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_matmas01_esb_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_matmas01_esb.esbsvc)

<interface>  <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ MATMAS01_receive.wsdl?wsdl</wsdlURL>------------------</interface>

Modified (DefaultSystem_matmas01_esb.esbsvc)

<interface><wsdlURL>MATMAS01_receive.wsdl</wsdlURL>------------------------</interface>

Original (DefaultSystem_matmas01_esb_RS.esbsvc)

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ MATMAS01_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

Modified (DefaultSystem_matmas01_esb_RS.esbsvc)

<serviceDefinition><wsdlURL>MATMAS01_receive.wsdl</wsdlURL>---------------------</endpointDefinition></serviceDefinition>

11. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

12. Once the project is migrated, a successful message is received in Oracle JDeveloper.

13. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

14. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="MATMAS01" adapter="iWay ERP Adapter" wsdlLocation="MATMAS01_receive.wsdl?wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

15. Save and then deploy the migrated ESB project.

16. Ensure that there are no error or warning messages during the deployment process.

17. Trigger the event messages from the ERP system (for example, SAP GUI) and verify that successful response XML files are received in the specified output folder.

Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and export the schemas into the default location.

3. Generate the outbound WSDL for the specific business object.

4. Restart the server.

5. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound BPEL Project by uploading the request and response schema generated from Application Explorer in step 2.

6. In the Partner Link, select the outbound WSDL from the local file system.

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

9. Copy the deployed BPEL project into the 11g system.

10. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

11. Once the project is migrated, a successful message is received in Oracle JDeveloper.

12. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

13. Save and then deploy the migrated BPEL project.

14. Ensure that there are no error or warning messages during the deployment process.

15. Open the Oracle Enterprise Manager console and invoke the input XML in XML / Tree view to receive a successful response XML.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and export the schemas into the default location.

3. Generate the outbound WSDL for the specific business object.

4. Restart the server.

5. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound BPEL Project by uploading the request and response schema generated from Application Explorer in step 2.

6. In the Partner Link, select the outbound WSDL from Service Explorer.

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

9. Copy the deployed BPEL project into the 11g system.

10. Edit the bpel.xml file for the WSDL location in the 10.1.3.4 project folder (Project_Name\bpel):

<partnerLinkBinding name="GetDetail"><property name="wsdlLocation">http://192.168.128.125:80/orainfra/wsil/adapters/applications/isdsrv2_CC_GetDetail_invoke.wsdl?wsdl</property></partnerLinkBinding>

Where the IP address and port number refer to the 10.1.3.4 system where the WSDL was generated.

11. Ensure that the 10.1.3.4 server is up and running.

12. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

13. Once the project is migrated, a successful message is received in Oracle JDeveloper.

14. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

15. Save and then deploy the migrated BPEL project.

16. Ensure that there are no error or warning messages during the deployment process.

17. Open the Oracle Enterprise Manager console and invoke the input XML in XML / Tree view to receive a successful response XML.

Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object.

4. Generate the inbound WSDL for the specific business object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound BPEL Project by selecting the inbound WSDL from the local file system in the Partner Link

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. Trigger the event messages from the SAP R/3 system and ensure that successful instances are received in the BPEL Console.

9. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed BPEL project into the 11g system.

11. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

12. Once the project is migrated, a successful message is received in Oracle JDeveloper.

13. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

14. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="MATMAS01" adapter="iWay ERP Adapter" wsdlLocation="MATMAS01_receive.wsdl?wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

15. Save and then deploy the migrated BPEL project.

16. Ensure that there are no error or warning messages during the deployment process.

17. Trigger the event messages from the SAP R/3 system and ensure that successful instances are received in the Oracle Enterprise Manager console.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object.

4. Generate the inbound WSDL for the specific business object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound BPEL Project by selecting the inbound WSDL from the Service Explorer in the Partner Link.

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. Trigger the event messages from the SAP R/3 system and ensure that successful instances are received in the BPEL Console.

9. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed BPEL project into the 11g system.

11. Edit the bpel.xml file for the WSDL location in the 10.1.3.4 project folder (Project_Name\bpel):

<partnerLinkBinding name="MATMAS01"><property name="wsdlLocation">http://192.168.128.122:80/orainfra/wsil/adapters/applications/MATMAS01_receive.wsdl?wsdl</property></partnerLinkBinding>

Where the IP address and port number refer to the 10.1.3.4 system where the WSDL was generated.

12. Ensure that the 10.1.3.4 server is up and running.

13. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

14. Once the project is migrated, a successful message is received in Oracle JDeveloper.

15. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

16. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="MATMAS01" adapter="iWay ERP Adapter" wsdlLocation="MATMAS01_receive.wsdl?wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

17. Save and then deploy the migrated BPEL project.

18. Ensure that there are no error or warning messages during the deployment process.

19. Trigger the event messages from the SAP R/3 system and ensure that successful instances are received in the Oracle Enterprise Manager console.

3 Oracle Application Adapter for Siebel Upgrade Guidelines

This chapter lists and describes upgrade guidelines that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

This section applies to Siebel 7.7 systems.

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create an Integration Object node by selecting a Siebel generated schema file (.xsd) using Application Explorer.

4. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

5. Generate an inbound WSDL for this object.

6. Modify the created 10.1.3.4 WSDL by replacing www.siebel.com with www.iwaysoftware.com in the three lines as shown in the following example:
Original 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node"xmlns:iWayEvent="http://www.siebel.com/xml/Sample%20Account"------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.siebel.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xsdLocal="http://www.siebel.com/xml/Sample%20Account"><xsd:element type="xsdLocal:SiebelMessage" name="SiebelMessage"/><xsd:complexType name="SiebelMessage">

Modified 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node"xmlns:iWayEvent="http://www.iwaysoftware.com/xml/Sample%20Account"-------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.iwaysoftware.com/xml/Sample%20Account"xmlns:xsdLocal="http://www.iwaysoftware.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified"><xsd:element name="SiebelMessage" type="xsdLocal:SiebelMessage"/>

7. Restart the server.

8. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

9. In the Custom Adapter service, select the inbound WSDL from the local file system.

10. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

11. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

12. Copy the deployed ESB project into the 11g system.

13. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

14. Once the project is migrated, a successful message is received in Oracle JDeveloper.

15. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

16. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

17. Save and then deploy the migrated ESB project.

18. Ensure that there are no error or warning messages during the deployment process.

19. Trigger the event messages from the Siebel system and verify that successful response XML files are received in the specified output folder.

This section applies to Siebel 7.0 systems.

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create an Integration Object node by selecting a Siebel generated schema file (.xdr) using Application Explorer.

4. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

5. Generate an inbound WSDL for this object.

6. Modify the created 10.1.3.4 WSDL by replacing urn:iwaysoftware:adapter:siebel:oct2004:request with http://www.iwaysoftware.com/xml/Sample%20Account, where Sample%20Account is the name of the specific Integration Object that is displayed in Application Explorer, in the following three lines:
Original 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/ariba01/samp_node"xmlns:iWayEvent="urn:iwaysoftware:adapter:siebel:oct2004:request"------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"targetNamespace="urn:iwaysoftware:adapter:siebel:oct2004:request"elementFormDefault="qualified" xmlns:sbl="urn:iwaysoftware:adapter:siebel:oct2004:request"><xsd:element name="SiebelMessage">

Modified 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/ariba01/samp_node"xmlns:iWayEvent="http://www.iwaysoftware.com/xml/Sample%20Account"-------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.iwaysoftware.com/xml/Sample%20Account"xmlns:xsdLocal="http://www.iwaysoftware.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified"><xsd:element name="SiebelMessage" type="xsdLocal:SiebelMessage"/>

7. Restart the server.

8. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

9. In the Custom Adapter service, select the inbound WSDL from the local file system.

10. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

11. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

12. Copy the deployed ESB project into the 11g system.

13. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

14. Once the project is migrated, a successful message is received in Oracle JDeveloper.

15. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

16. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

17. Save and then deploy the migrated ESB project.

18. Ensure that there are no error or warning messages during the deployment process.

19. Trigger the event messages from the Siebel system and verify that successful response XML files are received in the specified output folder.

Selecting a WSDL Using Service Explorer

This section applies to Siebel 7.7 systems.

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create an Integration Object node by selecting a Siebel generated schema file (.xsd) using Application Explorer.

4. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

5. Generate an inbound WSDL for this object.

6. Modify the created 10.1.3.4 WSDL by replacing www.siebel.com with www.iwaysoftware.com in the three lines as shown in the following example:
Original 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node"xmlns:iWayEvent="http://www.siebel.com/xml/Sample%20Account"------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.siebel.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xsdLocal="http://www.siebel.com/xml/Sample%20Account"><xsd:element type="xsdLocal:SiebelMessage" name="SiebelMessage"/><xsd:complexType name="SiebelMessage">

Modified 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/isdsrv22/samp_node"xmlns:iWayEvent="http://www.iwaysoftware.com/xml/Sample%20Account"-------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.iwaysoftware.com/xml/Sample%20Account"xmlns:xsdLocal="http://www.iwaysoftware.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified"><xsd:element name="SiebelMessage" type="xsdLocal:SiebelMessage"/>

7. Restart the server.

8. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

9. In the Custom Adapter service, select the inbound WSDL using Service Explorer.

10. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

11. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

12. Copy the deployed ESB project into the 11g system.

Note:
There is a patch BUG 9481515 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT FOR ALL ADPATERS New issue on Migration of ESB processes. For more information, see "BUG 9481515 Inbound" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

13. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_SA_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_SA.esbsvc)

<interface>  <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ isdsrv22_SA_receive.wsdl?wsdl</wsdlURL>------------------</interface>

Modified (DefaultSystem_SA.esbsvc)

<interface><wsdlURL> isdsrv22_SA_receive.wsdl </wsdlURL>------------------------</interface>

Original (DefaultSystem_SA_RS.esbsvc)

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ isdsrv22_SA_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

Modified (DefaultSystem_SA_RS.esbsvc)

<serviceDefinition><wsdlURL> isdsrv22_SA_receive.wsdl </wsdlURL>---------------------</endpointDefinition></serviceDefinition>

14. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

15. Once the project is migrated, a successful message is received in Oracle JDeveloper.

16. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

17. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

18. Save and then deploy the migrated ESB project.

19. Ensure that there are no error or warning messages during the deployment process.

20. Trigger the event messages from the Siebel system and verify that successful response XML files are received in the specified output folder.

This section applies to Siebel 7.0 systems.

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create an Integration Object node by selecting a Siebel generated schema file (.xdr) using Application Explorer.

4. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

5. Generate an inbound WSDL for this object.

6. Modify the created 10.1.3.4 WSDL by replacing urn:iwaysoftware:adapter:siebel:oct2004:request with http://www.iwaysoftware.com/xml/Sample%20Account, where Sample%20Account is the name of the specific Integration Object that is displayed in Application Explorer, in the following three lines:
Original 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/ariba01/samp_node"xmlns:iWayEvent="urn:iwaysoftware:adapter:siebel:oct2004:request"------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"targetNamespace="urn:iwaysoftware:adapter:siebel:oct2004:request"elementFormDefault="qualified" xmlns:sbl="urn:iwaysoftware:adapter:siebel:oct2004:request"><xsd:element name="SiebelMessage">

Modified 10.1.3.4 WSDL

<definitions name="samp_node"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/Siebel/ariba01/samp_node"xmlns:iWayEvent="http://www.iwaysoftware.com/xml/Sample%20Account"-------------<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.iwaysoftware.com/xml/Sample%20Account"xmlns:xsdLocal="http://www.iwaysoftware.com/xml/Sample%20Account" attributeFormDefault="unqualified" elementFormDefault="qualified"><xsd:element name="SiebelMessage" type="xsdLocal:SiebelMessage"/>

7. Restart the server.

8. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

9. In the Custom Adapter service, select the inbound WSDL using Service Explorer.

10. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

11. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

12. Copy the deployed ESB project into the 11g system.

Note:
There is a patch BUG 9481515 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT FOR ALL ADPATERS New issue on Migration of ESB processes. For more information, see "BUG 9481515 Inbound" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

13. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_SA_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_SA.esbsvc)

<interface>  <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ ariba01_SA_receive.wsdl?wsdl</wsdlURL>------------------</interface>

Modified (DefaultSystem_SA.esbsvc)

<interface><wsdlURL> ariba01_SA_receive.wsdl </wsdlURL>------------------------</interface>

Original (DefaultSystem_SA_RS.esbsvc)

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ ariba01_SA_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

Modified (DefaultSystem_SA_RS.esbsvc)

<serviceDefinition><wsdlURL> ariba01_SA_receive.wsdl </wsdlURL>---------------------</endpointDefinition></serviceDefinition>

14. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

15. Once the project is migrated, a successful message is received in Oracle JDeveloper.

16. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

17. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="ariba01_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

18. Save and then deploy the migrated ESB project.

19. Ensure that there are no error or warning messages during the deployment process.

20. Trigger the event messages from the Siebel system and verify that successful response XML files are received in the specified output folder.

Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to the particular business object. Create an Integration Object node by selecting the Siebel generated XSD/XDR file using Application Explorer.

3. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

4. Generate the inbound WSDL for the specific business object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound BPEL Project by selecting the inbound WSDL from the local file system in the Partner Link

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. Trigger the event messages from the Siebel system and ensure that successful instances are received in the BPEL Console.

9. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

10. Copy the deployed BPEL project into the 11g system.

11. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

12. Once the project is migrated, a successful message is received in Oracle JDeveloper.

13. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

14. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

15. Save and then deploy the migrated BPEL project.

16. Ensure that there are no error or warning messages during the deployment process.

17. Trigger the event messages from the Siebel system and ensure that successful instances are received in the Oracle Enterprise Manager console.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to the particular business object. Create an Integration Object node by selecting the Siebel generated XSD/XDR file using Application Explorer.

3. Create a new HTTP channel for Oracle Application Adapter for SAP R/3.

4. Generate the inbound WSDL for the specific business object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound BPEL Project by selecting the inbound WSDL from the Service Explorer in the Partner Link

7. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

8. Trigger the event messages from the Siebel system and ensure that successful instances are received in the BPEL Console.

9. On the 11g system, ensure the target, Integration Object node, and channel are created, and named the same as on the 10.1.3.4 system. While configuring the channel, in the PreParser tab, provide the event schema location generated from Application Explorer (right-click the Integration Object node and export the schema in 11g).

10. Copy the deployed BPEL project into the 11g system.

11. Edit the bpel.xml file for the WSDL location in the 10.1.3.4 project folder (Project_Name\bpel):

<partnerLinkBinding name="samp_node"><property name="wsdlLocation">http://192.168.128.125:80/orainfra/wsil/adapters/applications/isdsrv22_sampleAcct_receive.wsdl?wsdl</property></partnerLinkBinding>

Where the IP address and port number refer to the 10.1.3.4 system where the WSDL was generated.

12. Ensure that the 10.1.3.4 server is up and running.

13. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

14. Once the project is migrated, a successful message is received in Oracle JDeveloper.

15. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

16. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

17. Save and then deploy the migrated BPEL project.

18. Ensure that there are no error or warning messages during the deployment process.

19. Trigger the event messages from the Siebel system and ensure that successful instances are received in the Oracle Enterprise Manager console.

4 Oracle Application Adapter for PeopleSoft Upgrade Guidelines

This chapter lists and describes upgrade guidelines that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object and generate an inbound WSDL for this object.

Note:
There is a patch BUG 9411107 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT. Issue on Migration of ESB processes for PeopleSoft. For more information, see "BUG 9411107" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

4. Modify the WSDL by replacing the period (.) character in DEPT_SYNC.VERSION_1 to some other character (for example, an underscore '_', DEPT_SYNC_VERSION_1). There are nearly 19 occurrences in the 10.1.3.4 WSDL for the DEPT_SYNC object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

7. In the Custom Adapter service, select the inbound WSDL from the local file system.

8. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

9. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed ESB project into the 11g system.

11. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

12. Once the project is migrated, a successful message is received in Oracle JDeveloper.

13. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

14. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="DEPT_SYNC_VERSION_1" adapter="iWay ERP Adapter" wsdlLocation="isdsrv14_DEPT_SYNC_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

15. Save and then deploy the migrated ESB project.

16. Ensure that there are no error or warning messages during the deployment process.

17. Trigger the event messages from the ERP system (for example, PeopleTools) and verify that successful response XML files are received in the specified output folder.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Create a new channel for Oracle Application Adapter for SAP R/3.

3. Browse to a specific business object and generate an inbound WSDL for this object.

Note:
There is a patch BUG 9411107 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT. Issue on Migration of ESB processes for PeopleSoft. For more information, see "BUG 9411107" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

4. Modify the WSDL by replacing the period (.) character in DEPT_SYNC.VERSION_1 to some other character (for example, an underscore '_', DEPT_SYNC_VERSION_1). There are nearly 19 occurrences in the 10.1.3.4 WSDL for the DEPT_SYNC object.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

7. In the Custom Adapter service, select the inbound WSDL using Service Explorer.

8. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

9. On the 11g system, create a target and channel using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed ESB project into the 11g system.

11. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_dept_sync_wsdl_brows.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_dept_sync_wsdl_brows_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_dept_sync_wsdl_brows.esbsvc)

<interface>  <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ isdsrv14_DEPT_SYNC_receive_esb.wsdl?wsdl</wsdlURL>------------------</interface>

Modified (DefaultSystem_dept_sync_wsdl_brows.esbsvc)

<interface><wsdlURL> isdsrv14_DEPT_SYNC_receive_esb.wsdl</wsdlURL>------------------------</interface>

Original (DefaultSystem_dept_sync_wsdl_brows_RS.esbsvc)

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ isdsrv14_DEPT_SYNC_receive_esb.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

Modified (DefaultSystem_dept_sync_wsdl_brows_RS.esbsvc)

<serviceDefinition><wsdlURL> isdsrv14_DEPT_SYNC_receive_esb.wsdl</wsdlURL>---------------------</endpointDefinition></serviceDefinition>

12. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

13. Once the project is migrated, a successful message is received in Oracle JDeveloper.

14. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

15. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="DEPT_SYNC_VERSION_1" adapter="iWay ERP Adapter" wsdlLocation="isdsrv14_DEPT_SYNC_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/><record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

16. Save and then deploy the migrated ESB project.

17. Ensure that there are no error or warning messages during the deployment process.

18. Trigger the event messages from the ERP system (for example, PeopleTools) and verify that successful response XML files are received in the specified output folder.

Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and export the schemas into the default location.

3. Generate the outbound WSDL for the specific business object.

4. Modify the request and response schema that was exported from Application Explorer by changing the elementFormDefault value from unqualified to qualified.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound BPEL Project by uploading the request and response schema that is modified in step 4.

7. In the Partner Link, select the outbound WSDL from the local file system.

8. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

9. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed BPEL project into the 11g system.

11. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

12. Once the project is migrated, a successful message is received in Oracle JDeveloper.

13. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

14. Save and then deploy the migrated BPEL project.

15. Ensure that there are no error or warning messages during the deployment process.

16. Open the Oracle Enterprise Manager console and invoke the input XML in XML / Tree view to receive a successful response XML.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object and export the schemas into the default location.

3. Generate the outbound WSDL for the specific business object.

4. Modify the request and response schema that was exported from Application Explorer by changing the elementFormDefault value from unqualified to qualified.

5. Restart the server.

6. Start Oracle JDeveloper 10.1.3.4 and create a JCA outbound BPEL Project by uploading the request and response schema that is modified in step 4.

7. In the Partner Link, select the outbound WSDL from Service Explorer.

8. Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.

9. On the 11g system, create a target using the same name that was provided on the 10.1.3.4 system.

10. Copy the deployed BPEL project into the 11g system.

11. Edit the bpel.xml file for the WSDL location in the 10.1.3.4 project folder (Project_Name\bpel):

<partnerLinkBinding name="DEPT"><property name="wsdlLocation">http://192.168.128.125:80/orainfra/wsil/adapters/applications/isdsrv14_DEPT_invoke.wsdl?wsdl </property></partnerLinkBinding>

Where the IP address and port number refer to the 10.1.3.4 system where the WSDL was generated.

12. Ensure that the 10.1.3.4 server is up and running.

13. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

14. Once the project is migrated, a successful message is received in Oracle JDeveloper.

15. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

16. Save and then deploy the migrated BPEL project.

17. Ensure that there are no error or warning messages during the deployment process.

18. Open the Oracle Enterprise Manager console and invoke the input XML in XML / Tree view to receive a successful response XML.

Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

5 Oracle Application Adapter for J.D. Edwards OneWorld Upgrade Guidelines

This chapter lists and describes upgrade guidelines that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:

- Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

- Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Upgrading a 10.1.3.x ESB J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

Upgrading a 10.1.3.x ESB J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create a new port and TCP channel for Oracle Application Adapter for SAP R/3.

4. Trigger from the back-end and generate a schema with the response XML that was received in the port location using XMLSpy.

5. Copy the generated schema (.xsd file) in the following location:

<soadp1>\adapters\application\config\jca_sample\schemas\JDEdwards\target

6. Generate an inbound WSDL manually using the generated schema.

7. Make the following changes to the generated WSDL, as shown in the following examples:
Change 1

Replace Schemas-jdedwards-com to iwaysoftware in the target namespace:

<xs:schematargetNamespace="urn:Schemas-jdedwards-com:trans.response.JDESOOUT"      xmlns="urn:Schemas-jdedwards-com:trans.response.JDESOOUT" xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

to:

<xs:schema      targetNamespace="urn:iwaysoftware:trans.response.JDESOOUT"      xmlns="urn:iwaysoftware:trans.response.JDESOOUT"xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

Change 2

Cut and place the <xs:element name="jdeResponse"></xs:element> section before the <xs:element name="transaction"> section in the WSDL as shown in the following example:

<xs:element name="jdeResponse">        <xs:complexType>          <xs:sequence>      ----------------------------------</xs:element>      <xs:element name="transaction">      -------------------------------

Change 3

Replace iWayEvent:transaction to iWayEvent:jdeResponse, which is located in the <message name="event"> section:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:transaction"/></message>

to:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:jdeResponse"/></message>

8. Restart the server.

9. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

10. In the Custom Adapter service, select the inbound WSDL from the local file system.

11. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

12. On the 11g system, ensure that the target and channel that are created use the same name as specified on the 10.1.3.4 system. Copy the 10.1.3.4 schema and modify the 10.1.3.4 schema (jdeschema.xsd) as described in step 7 (only change 1 and change 2), which is used for 10.1.3.4 inbound WSDL creation. While creating the channel on the 11g system, in the PreParser tab, provide the modified event schema location (for example, c:\jdeschema.xsd).

13. Copy the deployed ESB project into the 11g system.

14. Start the Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

15. Once the project is migrated, a successful message is received in Oracle JDeveloper.

16. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

17. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="jde90_schema_ori" adapter="iWay ERP Adapter" wsdlLocation="jde9_salesorder_tcp_Feb27.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

18. Save and then deploy the migrated ESB project.

19. Ensure that there are no error or warning messages during the deployment process.

20. Trigger the event messages from the J.D. Edwards OneWorld system and verify that successful response XML files are received in the specified output folder.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create a new port and TCP channel for Oracle Application Adapter for SAP R/3.

4. Trigger from the back-end and generate a schema with the response XML that was received in the port location using XMLSpy.

5. Copy the generated schema (.xsd file) in the following location:

<soadp1>\adapters\application\config\jca_sample\schemas\JDEdwards\target

6. Generate an inbound WSDL manually using the generated schema.

7. Make the following changes to the generated WSDL, as shown in the following examples:
Change 1

Replace Schemas-jdedwards-com to iwaysoftware in the target namespace:

<xs:schematargetNamespace="urn:Schemas-jdedwards-com:trans.response.JDESOOUT"      xmlns="urn:Schemas-jdedwards-com:trans.response.JDESOOUT" xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

to:

<xs:schema      targetNamespace="urn:iwaysoftware:trans.response.JDESOOUT"      xmlns="urn:iwaysoftware:trans.response.JDESOOUT"xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

Change 2

Cut and place the <xs:element name="jdeResponse"></xs:element> section before the <xs:element name="transaction"> section in the WSDL as shown in the following example:

<xs:element name="jdeResponse">        <xs:complexType>          <xs:sequence>      ----------------------------------</xs:element>      <xs:element name="transaction">      -------------------------------

Change 3

Replace iWayEvent:transaction to iWayEvent:jdeResponse, which is located in the <message name="event"> section:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:transaction"/></message>

to:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:jdeResponse"/></message>

8. Restart the server.

9. Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.

10. In the Custom Adapter service, select the inbound WSDL using Service Explorer.

11. Deploy the ESB project successfully and ensure the registration of the ESB project is successful.

12. On the 11g system, ensure that the target and channel that are created use the same name as specified on the 10.1.3.4 system. Copy the 10.1.3.4 schema and modify the 10.1.3.4 schema (jdeschema.xsd) as described in step 7 (only change 1 and change 2), which is used for 10.1.3.4 inbound WSDL creation. While creating the channel on the 11g system, in the PreParser tab, provide the modified event schema location (for example, c:\jdeschema.xsd).

13. Copy the deployed ESB project into the 11g system.

Note:
There is a patch BUG 9481515 - EXCEPTION THROWN WHILE MIGRATING 10.1.3.X I-WAY PROJECT FOR ALL ADPATERS New issue on Migration of ESB processes. For more information, see "BUG 9481515 Inbound" on what has to be done if you apply the patch. If you do not apply the patch, then follow the next step or else skip it.

14. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_SalesOrder.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_SalesOrder_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_SalesOrder.esbsvc)

<interface>  <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ jde90_SalesOrder_receive.wsdl?wsdl</wsdlURL>------------------</interface>

Modified (DefaultSystem_SalesOrder.esbsvc)

<interface><wsdlURL> jde90_SalesOrder_receive.wsdl </wsdlURL>------------------------</interface>

Original (DefaultSystem_SalesOrder_RS.esbsvc)

<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ jde90_SalesOrder_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>

Modified (DefaultSystem_SalesOrder_RS.esbsvc)

<serviceDefinition><wsdlURL> jde90_SalesOrder_receive.wsdl </wsdlURL>---------------------</endpointDefinition>     </serviceDefinition>

15. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

16. Once the project is migrated, a successful message is received in Oracle JDeveloper.

17. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

18. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="jde90_schema_ori" adapter="iWay ERP Adapter" wsdlLocation="jde9_salesorder_tcp_Feb27.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

19. Save and then deploy the migrated ESB project.

20. Ensure that there are no error or warning messages during the deployment process.

21. Trigger the event messages from the J.D. Edwards OneWorld system and verify that successful response XML files are received in the specified output folder.

Upgrading a 10.1.3.x BPEL J2CA Outbound Process to 11g

Selecting a WSDL From the Local File System

You can follow the same procedure in "Selecting a WSDL From the Local File System".

Selecting a WSDL Using Service Explorer

You can follow the same procedure in "Selecting a WSDL Using Service Explorer".

Upgrading a 10.1.3.x BPEL J2CA Inbound Process to 11g

Selecting a WSDL From the Local File System

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create a new port and TCP channel for Oracle Application Adapter for SAP R/3.

4. Trigger from the back-end and generate a schema with the response XML that was received in the port location using XMLSpy.

5. Copy the generated schema (.xsd file) in the following location:

<soadp1>\adapters\application\config\jca_sample\schemas\JDEdwards\target

6. Generate an inbound WSDL manually using the generated schema.

7. Make the following changes to the generated WSDL, as shown in the following examples:
Change 1

Replace Schemas-jdedwards-com to iwaysoftware in the target namespace:

<xs:schematargetNamespace="urn:Schemas-jdedwards-com:trans.response.JDESOOUT"      xmlns="urn:Schemas-jdedwards-com:trans.response.JDESOOUT" xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

to:

<xs:schema      targetNamespace="urn:iwaysoftware:trans.response.JDESOOUT"      xmlns="urn:iwaysoftware:trans.response.JDESOOUT"xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

Change 2

Cut and place the <xs:element name="jdeResponse"></xs:element> section before the <xs:element name="transaction"> section in the WSDL as shown in the following example:

<xs:element name="jdeResponse">        <xs:complexType>          <xs:sequence>      ----------------------------------</xs:element>      <xs:element name="transaction">      -------------------------------

Change 3

Replace iWayEvent:transaction to iWayEvent:jdeResponse, which is located in the <message name="event"> section:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:transaction"/></message>

to:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:jdeResponse"/></message>

8. Restart the server.

9. Start Oracle JDeveloper 10.1.3.4 and create the inbound BPEL Process by selecting the inbound WSDL from the local file system in the Partner Link.

10. Deploy the BPEL process successfully and ensure there are no error or warning messages during deployment.

11. Trigger the event messages from the J.D. Edwards OneWorld system and ensure that successful instances are received in the BPEL Console.

12. On the 11g system, ensure that the target and channel that are created use the same name as specified on the 10.1.3.4 system. Copy the 10.1.3.4 schema and modify the 10.1.3.4 schema (jdeschema.xsd) as described in step 7 (only change 1 and change 2), which is used for 10.1.3.4 inbound WSDL creation. While creating the channel on the 11g system, in the PreParser tab, provide the modified event schema location (for example, c:\jdeschema.xsd).

13. Copy the deployed BPEL project into the 11g system.

14. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

15. Once the project is migrated, a successful message is received in Oracle JDeveloper.

16. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

17. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="jde90_schema_ori" adapter="iWay ERP Adapter" wsdlLocation="jde9_salesorder_tcp_Feb27.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

18. Save and then deploy the migrated BPEL project.

19. Ensure that there are no error or warning messages during the deployment process.

20. Trigger the event messages from the J.D. Edwards OneWorld system and ensure that successful instances are received in the Oracle Enterprise Manager console.

Selecting a WSDL Using Service Explorer

1. On the 10.1.3.4 system, create a new target for Oracle Application Adapter for SAP R/3 using Application Explorer and connect to the target.

2. Browse to a specific business object.

3. Create a new port and TCP channel for Oracle Application Adapter for SAP R/3.

4. Trigger from the back-end and generate a schema with the response XML that was received in the port location using XMLSpy.

5. Copy the generated schema (.xsd file) in the following location:

<soadp1>\adapters\application\config\jca_sample\schemas\JDEdwards\target

6. Generate an inbound WSDL manually using the generated schema.

7. Make the following changes to the generated WSDL, as shown in the following examples:
Change 1

Replace Schemas-jdedwards-com to iwaysoftware in the target namespace:

<xs:schematargetNamespace="urn:Schemas-jdedwards-com:trans.response.JDESOOUT"      xmlns="urn:Schemas-jdedwards-com:trans.response.JDESOOUT" xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

to:

<xs:schema      targetNamespace="urn:iwaysoftware:trans.response.JDESOOUT"      xmlns="urn:iwaysoftware:trans.response.JDESOOUT"xmlns:xs=http://www.w3.org/2001/XMLSchema elementFormDefault="qualified">

Change 2

Cut and place the <xs:element name="jdeResponse"></xs:element> section before the <xs:element name="transaction"> section in the WSDL as shown in the following example:

<xs:element name="jdeResponse">        <xs:complexType>          <xs:sequence>      ----------------------------------</xs:element>      <xs:element name="transaction">      -------------------------------

Change 3

Replace iWayEvent:transaction to iWayEvent:jdeResponse, which is located in the <message name="event"> section:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:transaction"/></message>

to:

<message name="event">    <part name="event_jde_inbound" element="iWayEvent:jdeResponse"/></message>

8. Restart the server.

9. Start Oracle JDeveloper 10.1.3.4 and create the inbound BPEL Process by selecting the inbound WSDL from the Service Explorer in the Partner Link.

10. Deploy the BPEL process successfully and ensure there are no error or warning messages during deployment.

11. Trigger the event messages from the J.D. Edwards OneWorld system and ensure that successful instances are received in the BPEL Console.

12. On the 11g system, ensure that the target and channel that are created use the same name as specified on the 10.1.3.4 system. Copy the 10.1.3.4 schema and modify the 10.1.3.4 schema (jdeschema.xsd) as described in step 7 (only change 1 and change 2), which is used for 10.1.3.4 inbound WSDL creation. While creating the channel on the 11g system, in the PreParser tab, provide the modified event schema location (for example, c:\jdeschema.xsd).

13. Copy the deployed BPEL project into the 11g system.

14. Edit the bpel.xml file for the WSDL location in the 10.1.3.4 project folder (Project_Name\bpel):

<partnerLinkBinding name=" jde90_schema_ori"><property name="wsdlLocation">http://192.168.128.125:80/orainfra/wsil/adapters/applications/ jde9_salesorder_tcp_Feb27.wsdl?wsdl</property></partnerLinkBinding>

Where the IP address and port number refer to the 10.1.3.4 system where the WSDL was generated.

15. Ensure that the 10.1.3.4 server is up and running.

16. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.

17. Once the project is migrated, a successful message is received in Oracle JDeveloper.

18. Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.

19. Double-click the J2CA properties file under the migrated project in Oracle JDeveloper and remove the following line:

<record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

For example:

<adapter-config name="jde90_schema_ori" adapter="iWay ERP Adapter" wsdlLocation="jde9_salesorder_tcp_Feb27.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>

20. Save and then deploy the migrated BPEL project.

21. Ensure that there are no error or warning messages during the deployment process.

22. Trigger the event messages from the J.D. Edwards OneWorld system and ensure that successful instances are received in the Oracle Enterprise Manager console.

Glossary

adapter

Provides universal connectivity by enabling an electronic interface to be accommodated (without loss of function) to another electronic interface.

agent

Supports service protocols in listeners and documents.

business service

Also known as a Web service. A Web service is a self-contained, modularized function that can be published and accessed across a network using open standards. It is the implementation of an interface by a component and is an executable entity.

channel

Represents configured connections to particular instances of back-end systems. A channel binds one or more event ports to a particular listener managed by an adapter.

listener

A component that accepts requests from client applications.

port

Associates a particular business object exposed by the adapter with a particular disposition. A disposition is a URL that defines the protocol and location of the event data. The port defines the end point of the event consumption.

Index
G  I  O  U

G

general upgrade guidelines, 1

I

inbound ESB and BPEL process

post-upgrade requirement, 1.2.4

inbound process

upgrading, 1.2

O

Oracle Application Adapter for J.D. Edwards OneWorld

BPEL J2CA inbound process

upgrading, 5.4

BPEL J2CA outbound process

upgrading, 5.3

ESB J2CA inbound process

upgrading, 5.2

ESB J2CA outbound process

upgrading, 5.1

Oracle Application Adapter for PeopleSoft

BPEL J2CA inbound process

upgrading, 4.4

BPEL J2CA outbound process

upgrading, 4.3

ESB J2CA inbound process

upgrading, 4.2

ESB J2CA outbound process

upgrading, 4.1

Oracle Application Adapter for SAP R/3

BPEL J2CA inbound process

upgrading, 2.4

BPEL J2CA outbound process

upgrading, 2.3

ESB J2CA inbound process

upgrading, 2.2

ESB J2CA outbound process

upgrading, 2.1

Oracle Application Adapter for Siebel

BPEL J2CA inbound process

upgrading, 3.4

BPEL J2CA outbound process

upgrading, 3.3

ESB J2CA inbound process

upgrading, 3.2

ESB J2CA outbound process

upgrading, 3.1

Oracle upgrade patches, 1.5 Oracle's Unified Method (OUM), Preface outbound ESB and BPEL process

post-upgrade requirement, 1.1.5

outbound process

upgrading, 1.1

U

upgrade considerations, 1.5

upgrade guidelines

general, 1

Oracle Application Adapter for J.D. Edwards OneWorld, 5

Oracle Application Adapter for PeopleSoft, 4

Oracle Application Adapter for SAP R/3, 2

Oracle Application Adapter for Siebel, 3

upgrade patches, 1.5

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.