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

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

    Oracle JDeveloper context menu
    Description of "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

    New Gallery dialog
    Description of "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

    BPEL Project Creation Wizard
    Description of "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

    Input/Output Elements page
    Description of "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

    Select Schema dialog
    Description of "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

    Type Chooser dialog
    Description of "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

    Input/Output Elements page
    Description of "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

    Type Chooser dialog
    Description of "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

    Import Schema File dialog
    Description of "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

    Import Schema dialog
    Description of "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

    Import Schema File dialog
    Description of "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

    Type Chooser dialog
    Description of "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

    Input/Output Elements page
    Description of "Figure 1-13 BPEL Project Creation Wizard - I/O Elements Page"

  20. Click Finish.

    Figure 1-14 Standard BPEL Outbound Process

    completed process
    Description of "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

    Messages tab
    Description of "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

    Open icon
    Description of "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

    Open dialog
    Description of "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

    Migration Wizard
    Description of "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

    Confirmation page
    Description of "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

    Component IDs page
    Description of "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

    Finish page
    Description of "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

    Migration Status message
    Description of "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

    migrated BPEL project
    Description of "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

    Messages tab
    Description of "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

    Input XML
    Description of "Figure 1-25 Input XML in the Request Tab"

    Output XML that is received

    Figure 1-26 Output XML Received in the Response Tab

    Output XML
    Description of "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

    JCA Properties Source
    Description of "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

    Oracle JDeveloper context menu
    Description of "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

    New Gallery dialog
    Description of "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

    BPEL Project Creation Wizard
    Description of "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

    completed process
    Description of "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

    Messages tab
    Description of "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

    Open icon
    Description of "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

    Open dialog
    Description of "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

    Migration Wizard
    Description of "Figure 1-35 Migration Wizard"

  5. Click Next.

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

    Figure 1-36 Confirmation Page

    Confirmation page
    Description of "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

    Component IDs page
    Description of "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

    Finish page
    Description of "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

    Migration Status message
    Description of "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

    migrated project
    Description of "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

    JCA properties file
    Description of "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

    Messages tab
    Description of "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

    JCA Properties Source
    Description of "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/PS2 Outbound and Inbound Processes to 11g PS3

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

Exporting the Configured Processes From Oracle Service Bus 10.1.3.x/PS2

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

  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/PS2) 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

    Oracle Service Bus console home page
    Description of "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

    Change Center area
    Description of "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

    System Administration option
    Description of "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

    Export Resources option
    Description of "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

    Resource Summary area
    Description of "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

    Opening dialog
    Description of "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

    file system directory location
    Description of "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/PS2 must be copied to the system where Oracle Service Bus 11g PS3 is installed.

Importing the Exported Processes to Oracle Service Bus 11g PS3

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

Prerequisites

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

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

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

  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 PS3) 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

    Oracle Service Bus console home page
    Description of "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

    Description of Figure 1-52 follows
    Description of "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

    System Administration option
    Description of "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

    Description of Figure 1-54 follows
    Description of "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

    Import Resources page
    Description of "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/PS2 and copied to the local system.

    Figure 1-56 Browse Button on the Import Resources Page

    Description of Figure 1-56 follows
    Description of "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

    Resource Summary area
    Description of "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

    processing status indicator
    Description of "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

    success message
    Description of "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

    Activate Session page
    Description of "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

    Project Explorer
    Description of "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

    imported project folders
    Description of "Figure 1-62 Imported Project Folders"

    The project folder structure must match the one from Oracle Service Bus 10.1.3.x/PS2, 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

    expanded mySAP project folder
    Description of "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

    imported Business Services
    Description of "Figure 1-64 Imported Business Services"

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

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

    Figure 1-65 Imported Proxy Services

    imported Proxy Services
    Description of "Figure 1-65 Imported Proxy Services"

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

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

    Figure 1-66 Imported WSDL Files

    imported WSDL files
    Description of "Figure 1-66 Imported WSDL Files"

    Ensure that all the WSDL files that were created in the Oracle Service Bus 10.1.3.x/PS2 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 PS3 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">

    The change that is described in this note is only required if you are migrating an OSB 10g Release 3 process to 11g PS3. This change is not required if you are migrating an OSB 11g PS2 process to 11g PS3.

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

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

Note:

Imported J2CA outbound processes in Oracle Service Bus 11g PS3 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

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

Note:

The changes that are described in this section are only required if you are migrating an OSB 10g Release 3 process to 11g PS3. If you are migrating an OSB 11g PS2 process to 11g PS3, then you can skip this section (1.3.3.1, "Imported J2CA Inbound Processes").

  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

    ProxyService folder
    Description of "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

    selected JCA binding file
    Description of "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

    JCA Binding Text View
    Description of "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

    XML element
    Description of "Figure 1-70 The <record-converter> Element"

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

    Figure 1-71 Save Button

    Save button
    Description of "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 PS3.

  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

    selected WSDL file
    Description of "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

    Text View tab
    Description of "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

    Edit a WSDL Resource page
    Description of "Figure 1-74 The Edit a WSDL Resource Page"

  5. Change the <soap:address location> element to point to the system where OSB 11g PS3 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 PS3 is running, as shown in Figure 1-75.

    Figure 1-75 Transport Configuration Section

    Transport Configuration section
    Description of "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/PS2 Outbound and Inbound BPEL and Mediator Processes to 11g PS3

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

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

  1. Open Oracle JDeveloper 11g Release 1 (11.1.1.4.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

    JDeveloper toolbar
    Description of "Figure 1-76 Oracle JDeveloper Toolbar"

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

    Figure 1-77 Open Dialog

    Open dialog
    Description of "Figure 1-77 Open Dialog"

  3. Open the 11g PS1/PS2 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

    Open Warning dialog
    Description of "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

    Migration Status message
    Description of "Figure 1-79 Migration Status Message"

  6. Click OK.

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

    Figure 1-80 Migrated Sample Project

    Migrated sample project
    Description of "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

    Deploy menu option
    Description of "Figure 1-81 Deploy Menu Option"

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

    Figure 1-82 Deployment Action Page

    Deployment Action page
    Description of "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

    Deploy Configuration page
    Description of "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

    Select Server page
    Description of "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

    SOA Servers page
    Description of "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

    Summary page
    Description of "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

    Deployment Log
    Description of "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

    Input XML in XML View
    Description of "Figure 1-88 Input XML in XML View"

    Figure 1-89 Received Output XML

    Received Output XML
    Description of "Figure 1-89 Received Output XML"

Workaround for PS1 J.D. Edwards OneWorld Outbound Mediator Process When Migrating to 11g PS2/PS3

Once the J.D. Edwards OneWorld Mediator process is copied into 11g PS2/PS3 system, perform the following steps:

  1. Open the PS1 project folder and open the WSDL file generated from Application Explorer to edit and perform the following changes:

    Original

    <definitionsname="GetPhone"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde_90_attr_tgt/GetPhone"xmlns="http://schemas.xmlsoap.org/wsdl/"xmlns:iWayRequest="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:GetPhone="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde_90_attr_tgt/GetPhone"xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">..............<schema xmlns="http://www.w3.org/2001/XMLSchema"><import schemaLocation="jde90_GetPhone_invoke_response.xsd" namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"/></schema>................<message name="response"><part name="output_GetPhone" element="iWayRequest:jdeResponse"/></message>

    Modified

    <definitionsname="GetPhone"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde_90_attr_tgt/GetPhone"xmlns="http://schemas.xmlsoap.org/wsdl/"xmlns:iWayResponse="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"xmlns:iWayRequest="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:GetPhone="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde_90_attr_tgt/GetPhone"xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">..............................<schema xmlns="http://www.w3.org/2001/XMLSchema"><import schemaLocation="jde90_GetPhone_invoke_response.xsd" namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"/></schema>..................................<message name="response"><part name="output_GetPhone" element="iWayResponse:jdeResponse"/></message>

  2. Open the response.xsd file generated from Application Explorer to edit and .response to the end of the targetNamespace and ns declaration. For example:

    Original

    <xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema targetNamespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:ns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" elementFormDefault="qualified">

    Modified

    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"xmlns:ns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" elementFormDefault="qualified">

  3. Open the MediatorComponentName.wsdl file (for example, Mediator.wsdl) to edit and perform the following changes:

    Original

    <wsdl:definitions      name="Mediator1"targetNamespace="http://xmlns.oracle.com/ps1_project/ps1_jca_jd90_medi_gephone/Mediator1"      xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/xmlns:inp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:tns=http://xmlns.oracle.com/ps1_project/ps1_jca_jd90_medi_gephone/Mediator1xmlns:out1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"><wsdl:import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" location="jde90_GetPhone_invoke.wsdl"/><wsdl:import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" location="jde90_GetPhone_invoke.wsdl"/>          …………………………………………..      <wsdl:message name="replyMessage">            <wsdl:part name="reply" element="inp1:jdeResponse"/>         </wsdl:message>

    Modified

    <wsdl:definitions      name="Mediator1"targetNamespace="http://xmlns.oracle.com/ps1_project/ps1_jca_jd90_medi_gephone/Mediator1"      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"            xmlns:inp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:tns="http://xmlns.oracle.com/ps1_project/ps1_jca_jd90_medi_gephone/Mediator1"xmlns:out1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"><wsdl:import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" location="jde90_GetPhone_invoke.wsdl"/><wsdl:import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" location="jde90_GetPhone_invoke.wsdl"/>        ………………………………..      <wsdl:message name="replyMessage">            <wsdl:part name="reply" element="out1:jdeResponse"/></wsdl:message>

  4. Start Oracle JDeveloper 11g and migrate the PS1 Mediator project.

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

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

    Since changes were made to the WSDL file for the response section, a new mapper file must be created for jdeResponse.

  7. Double-click the mediator component and go to the Synchronous Reply area.

  8. Click the Select an existing mapper file or create a new one button in the Transform Using field, as shown in Figure 1-90.

    Figure 1-90 Transform Using Field

    Transform Using field
    Description of "Figure 1-90 Transform Using Field"

    The Reply Transformation Map dialog is displayed, as shown in Figure 1-91.

    Figure 1-91 Reply Transformation Map Dialog

    Reply Transformation Map dialog
    Description of "Figure 1-91 Reply Transformation Map Dialog"

  9. Click the Create New Mapper File option and click OK.

  10. Automap the iWayResponse:jdeResponse in the source and iWayResponse:jdeResponse in the target, as shown in Figure 1-92.

    Figure 1-92 Mapping Source To Target

    Mapping tab
    Description of "Figure 1-92 Mapping Source To Target"

    The Auto Map Preferences dialog is displayed, as shown in Figure 1-93.

    Figure 1-93 Auto Map Preferences Dialog

    Auto Map Preferences dialog
    Description of "Figure 1-93 Auto Map Preferences Dialog"

  11. Accept the default values and click OK.

    The automap is completed successfully, as shown in Figure 1-94.

    Figure 1-94 Completed Automap

    completed automap
    Description of "Figure 1-94 Completed Automap"

  12. Double click the composite.xml file.

  13. Save and then deploy the migrated Mediator project.

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

  15. Once the deployment is successful, navigate to the Oracle Enterprise Manager console and invoke the input XML file for the particular deployed project in the Request tab.

    The successful response XML is received in the Response tab.

Additional Modifications for Migrated Processes in 11g PS3

Upgraded J2CA outbound and inbound processes in 11g PS3 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 PS3, double-click the composite.xml file to open the migrated project, as shown in Figure 1-95

    Figure 1-95 Opened Migrated Project

    opened migrated project
    Description of "Figure 1-95 Opened Migrated Project"

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

    Figure 1-96 BSE Outbound WSDL File

    BSE outbound WSDL file
    Description of "Figure 1-96 BSE Outbound WSDL File"

  3. Change the <soap:address location> element to point to the system where 11g PS3 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.

Upgrading 11g PS2 Outbound and Inbound BPM Processes to 11g PS3

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

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

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

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

    Figure 1-97 Oracle JDeveloper Toolbar

    JDeveloper toolbar
    Description of "Figure 1-97 Oracle JDeveloper Toolbar"

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

    Figure 1-98 Open Dialog

    Open dialog
    Description of "Figure 1-98 Open Dialog"

  3. Open the 11g PS2 project (for example, mysap_esdsun9_jca_bpm_ccgd_OB) and then select the .jpr extension file (for example, mysap_esdsun9_jca_bpm_ccgd_OB.jpr).

  4. Click Open.

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

    Figure 1-99 Open Warning Dialog

    Open Warning dialog
    Description of "Figure 1-99 Open Warning Dialog"

  5. Click Yes.

    The Migration Status message is displayed, as shown in Figure 1-100.

    Figure 1-100 Migration Status Message

    Migration Status message
    Description of "Figure 1-100 Migration Status Message"

  6. Click OK.

    The Oracle 11g PS2 project is now available in your Oracle 11g PS3 environment, as shown in Figure 1-101.

    Figure 1-101 Migrated Sample Project

    Migrated sample project
    Description of "Figure 1-101 Migrated Sample Project"

  7. Expand the migrated project in the left pane (for example, mysap_esdsun9_jca_bpm_ccgd_OB) 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, mysap_esdsun9_jca_bpm_ccgd_OB), as shown in Figure 1-102.

    Figure 1-102 Deploy Menu Option

    Deploy menu option
    Description of "Figure 1-102 Deploy Menu Option"

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

    Figure 1-103 Deployment Action Page

    Deployment Action page
    Description of "Figure 1-103 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-104.

    Figure 1-104 Deploy Configuration Page

    Deploy Configuration page
    Description of "Figure 1-104 Deploy Configuration Page"

  12. Leave the default values selected and click Next.

    The Select Server page is displayed, as shown in Figure 1-105.

    Figure 1-105 Select Server Page

    Select Server page
    Description of "Figure 1-105 Select Server Page"

  13. Select the configured server and click Next.

    The SOA Servers page is displayed, as shown in Figure 1-106.

    Figure 1-106 SOA Servers Page

    SOA Servers page
    Description of "Figure 1-106 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-107.

    Figure 1-107 Summary Page

    Summary page
    Description of "Figure 1-107 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-108.

    Figure 1-108 Deployment Log

    Deployment Log
    Description of "Figure 1-108 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-109 and Figure 1-110.

    Figure 1-109 Input XML in XML View

    Input XML in XML View
    Description of "Figure 1-109 Input XML in XML View"

    Figure 1-110 Received Output XML

    Received Output XML
    Description of "Figure 1-110 Received Output XML"

Workaround for J2CA BPM Processes

This section describes a workaround for J2CA BPM processes when migrating BAPI or RFC objects for MySAP adapter from 11g PS2 to 11g PS3.

When a 11g PS2 J2CA BPM outbound process for the CompanyCode GetDetail object is migrated, a warning symbol is displayed in the 11g PS3 version of Oracle JDeveloper, as shown in Figure 1-111.

Figure 1-111 Warning Symbol

warning symbol
Description of "Figure 1-111 Warning Symbol"

When you move your pointer over the warning symbol, warning messages are displayed, as shown in Figure 1-112.

Figure 1-112 Warning Messages

warning messages
Description of "Figure 1-112 Warning Messages"

For example:

WARNINGS:-Data Association expression is not valid in node 'ServiceTask': Undefined variable 'getDetail'.- Data Association expression is not valid in node 'ServiceTask': Undefined variable 'response'.- Data Association expression is not valid in node 'ServiceTask1': Undefined variable 'response'.

This section provides instructions on how to apply a workaround that resolves this issue.

Note:

This workaround is applicable to Oracle BUG 11798374 - migration ps2-> ps3 bug.

  1. Open the composite.xml file from the project folder and double-click the BPM Process component.

    The BPM process is opened and you are able to see the ServiceTask and ServiceTask1 activities, including the error symbols, as shown in Figure 1-113.

    Figure 1-113 ServiceTask Activities

    ServiceTask Activities
    Description of "Figure 1-113 ServiceTask Activities"

  2. Double-click the ServiceTask activity.

    The Properties - ServiceTask dialog is displayed, as shown in Figure 1-114.

    Figure 1-114 Properties - ServiceTask Dialog

    ServiceTask dialog
    Description of "Figure 1-114 Properties - ServiceTask Dialog"

  3. Click the Implementation tab.

  4. Uncheck the Use Associations option.

    A confirmation message is displayed in the Data Associations dialog, as shown in Figure 1-115.

    Figure 1-115 Confirmation Message

    Data Associations dialog
    Description of "Figure 1-115 Confirmation Message"

  5. Click Yes.

    You are returned to the Properties - ServiceTask dialog, as shown in Figure 1-116.

    Figure 1-116 Properties - ServiceTask Dialog

    ServiceTask dialog
    Description of "Figure 1-116 Properties - ServiceTask Dialog"

  6. Select the Use Associations option and then click the Edit Data Associations icon.

    The Data Associations window is displayed, as shown in Figure 1-117.

    Figure 1-117 Data Associations Window

    Data Associations window
    Description of "Figure 1-117 Data Associations Window"

  7. Drag and drop dataobject1 (request) to the Inputs field and dataobject2 (response) to the Outputs field, as shown in Figure 1-118.

    Figure 1-118 Dataobject1 and Dataobject 2

    Data Associations window
    Description of "Figure 1-118 Dataobject1 and Dataobject 2"

  8. Click OK.

    You are returned to the Properties - ServiceTask dialog, as shown in Figure 1-119.

    Figure 1-119 Properties - ServiceTask Dialog

    ServiceTask dialog
    Description of "Figure 1-119 Properties - ServiceTask Dialog"

  9. Click OK.

    You are returned to the Process tab, as shown in Figure 1-120.

    Figure 1-120 Process Tab

    Process tab
    Description of "Figure 1-120 Process Tab"

  10. Double-click the ServiceTask1 activity.

    The Properties - ServiceTask1 dialog is displayed, as shown in Figure 1-121.

    Figure 1-121 Properties - ServiceTask1 Dialog

    ServiceTask1 dialog
    Description of "Figure 1-121 Properties - ServiceTask1 Dialog"

  11. Click the Implementation tab.

  12. Uncheck the Use Associations option.

    A confirmation message is displayed in the Data Associations dialog, as shown in Figure 1-122.

    Figure 1-122 Confirmation Message

    Data Associations dialog
    Description of "Figure 1-122 Confirmation Message"

  13. Click Yes.

    You are returned to the Properties - ServiceTask1 dialog, as shown in Figure 1-123.

    Figure 1-123 Properties - ServiceTask1 Dialog

    ServiceTask1 dialog
    Description of "Figure 1-123 Properties - ServiceTask1 Dialog"

  14. Select the Use Associations option and then click the Edit Data Associations icon.

    The Data Associations window is displayed, as shown in Figure 1-124.

    Figure 1-124 Data Associations Window

    Data Associations window
    Description of "Figure 1-124 Data Associations Window"

  15. Drag and drop dataobject2 (response) to the Inputs field, as shown in Figure 1-125.

    Figure 1-125 Dataobject2

    Data Associations window
    Description of "Figure 1-125 Dataobject2"

  16. Click OK.

    You are returned to the Properties - ServiceTask1 dialog, as shown in Figure 1-126.

    Figure 1-126 Properties - ServiceTask1 Dialog

    ServiceTask1 dialog
    Description of "Figure 1-126 Properties - ServiceTask1 Dialog"

  17. Click OK.

    You are returned to the Process tab, as shown in Figure 1-127.

    Figure 1-127 Process Tab

    Process tab
    Description of "Figure 1-127 Process Tab"

    Notice that no errors or warnings are being indicated.

  18. Save the process.

  19. Double-click the composite.xml file.

    Notice that the warning symbol is still indicated in the BPM Process component, as shown in Figure 1-128.

    Figure 1-128 BPM Process Component

    BPM Process Component
    Description of "Figure 1-128 BPM Process Component"

  20. Restart Oracle JDeveloper.

    Once Oracle JDeveloper has restarted, the warning symbol is not indicated in the BPM Process component, as shown in Figure 1-129.

    Figure 1-129 BPM Process Component

    BPM Process Component
    Description of "Figure 1-129 BPM Process Component"

Additional Modifications for Migrated Processes in 11g PS3

Upgraded J2CA outbound and inbound processes in 11g PS3 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 PS3, double-click the composite.xml file to open the migrated project, as shown in Figure 1-130

    Figure 1-130 Opened Migrated Project

    opened migrated project
    Description of "Figure 1-130 Opened Migrated Project"

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

    Figure 1-131 BSE Outbound WSDL File

    BSE outbound WSDL file
    Description of "Figure 1-131 BSE Outbound WSDL File"

  3. Change the <soap:address location> element to point to the system where 11g PS3 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.