Skip Headers
Oracle® Fusion Middleware Application Adapter Upgrade Guide for Oracle WebLogic Server
11g Release 1 (11.1.1.4.0)

Part Number E17392-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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

Selecting a WSDL From the Local File System

This workaround must be performed for a J.D. Edwards outbound ESB process when migrating from 10.1.3.x to PS2 and 10.1.3.x to PS3. If you are migrating 10.1.3.x to PS1, then you can follow the same procedure in "Selecting a WSDL From the Local File System".

  1. On the 10.1.3.4 system, create a new target for the 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 file 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 file from the local file system.

  6. Deploy the ESB project successfully and ensure that 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. Open the 10.1.3.4 project and edit the associated WSDL file with the following changes:

    Change 1

    Add the following line in the <definitions> section for iWayResponse:

    xmlns:iWayResponse="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"
    

    For example:

    <definitions name="GetPhone"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde9/GetPhone" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"xmlns:GetPhone="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde9/GetPhone"xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:iWay="http://xmlns.oracle.com/pcbpel/adapter/iWay/"xmlns:pc="http://xmlns.oracle.com/pcbpel/"xmlns:iWayRequest="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"   xmlns:iWayResponse="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"xmlns="http://schemas.xmlsoap.org/wsdl/">
    

    Change 2

    Add .response at the end of targetNamespace and ns declaration in the schema section above the <xsd:element name="jdeResponse"> line. 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"><xsd:element name="jdeResponse">
    

    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"><xsd:element name="jdeResponse">
    

    Change 3

    Change iWayRequest to iWayResponse in the element field for the response message section. For example:

    Original

    <message name="response">       <part name="output_GetPhone" element="iWayRequest:jdeResponse"/>        </message>
    

    Modified

    <message name="response">       <part name="output_GetPhone" element="iWayResponse:jdeResponse"/>     </message>
    
  10. Open and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_jde9_getphone.esbsvc) in the reply validate section by adding .response in the tns namespace. For example:

    Original

    <reply validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" element="tns:jdeResponse" schemaLocation="esb:///ESB_Projects/Upgrade_testing_jde9_getphone_10134_jca_esb/JDE90_GetPhone_invoke.wsdl"/>
    

    Modified

    <reply validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" element="tns:jdeResponse" schemaLocation="esb:///ESB_Projects/Upgrade_testing_jde9_getphone_10134_jca_esb/JDE90_GetPhone_invoke.wsdl"/>
    
  11. Open and edit the DefaultSystem_FileAdapterName.esbsvc file created for the write operation (for example, DefaultSystem_write getphone.esbsvc) in the request validate section by adding .response in the tns namespace. For example:

    Original

    <request validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" element="tns:jdeResponse"/
    

    Modified

    <request validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" element="tns:jdeResponse"/>
    
  12. Open and edit the FileAdapterName.wsdl file created for write operation (for example, write_getphone.wsdl) by adding .response. For example:

    Original

    <definitions name="write_getphone"targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"xmlns="http://schemas.xmlsoap.org/wsdl/"xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:imp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/file/"><import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" location="JDE90_GetPhone_invoke.wsdl"/>
    

    Modified

    <definitions name="write_getphone"targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"            xmlns="http://schemas.xmlsoap.org/wsdl/"         xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"           xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"          xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:imp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"           xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/file/"><import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" location="JDE90_GetPhone_invoke.wsdl"/>
    
  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.

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

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

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

    Figure 5-1 Transform Using Field

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

    The Reply Transformation Map dialog is displayed, as shown in Figure 5-2.

    Figure 5-2 Reply Transformation Map Dialog

    Reply Transformation Map dialog
    Description of "Figure 5-2 Reply Transformation Map Dialog"

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

  19. Automap the iWayResponse:jdeResponse in the source and iWayResponse:jdeResponse in the target, as shown in Figure 5-3.

    Figure 5-3 Mapping Source To Target

    Mapping tab
    Description of "Figure 5-3 Mapping Source To Target"

    The Auto Map Preferences dialog is displayed, as shown in Figure 5-4.

    Figure 5-4 Auto Map Preferences Dialog

    Auto Map Preferences dialog
    Description of "Figure 5-4 Auto Map Preferences Dialog"

  20. Accept the default values and click OK.

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

    Figure 5-5 Completed Automap

    completed automap
    Description of "Figure 5-5 Completed Automap"

  21. Double click the composite.xml file.

  22. Save and then deploy the migrated ESB project.

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

  24. 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

This workaround must be performed for a J.D. Edwards outbound ESB process when migrating from 10.1.3.x to PS2 and 10.1.3.x to PS3. If you are migrating 10.1.3.x to PS1, then you can follow the same procedure in "Selecting a WSDL Using Service Explorer".

  1. On the 10.1.3.4 system, create a new target for the 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 file 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 that the registration of the ESB project is successful.

  7. Navigate to the location where the 10.1.3.4 WSDL file is generated and edit the WSDL file with the following changes:

    Change 1

    Add the following line in the <definitions> section for iWayResponse:

    xmlns:iWayResponse="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"
    

    For example:

    <definitions name="GetPhone"targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde9/GetPhone" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"xmlns:GetPhone="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/jde9/GetPhone"xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:iWay="http://xmlns.oracle.com/pcbpel/adapter/iWay/"xmlns:pc="http://xmlns.oracle.com/pcbpel/"xmlns:iWayRequest="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"   xmlns:iWayResponse="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"xmlns="http://schemas.xmlsoap.org/wsdl/">
    

    Change 2

    Add .response at the end of the targetNamespace and ns declaration in the schema section above the <xsd:element name="jdeResponse"> line. 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"><xsd:element name="jdeResponse">
    

    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"><xsd:element name="jdeResponse">
    

    Change 3

    Change iWayRequest to iWayResponse in the element field for the response message section. For example:

    Original

    <message name="response">       <part name="output_GetPhone" element="iWayRequest:jdeResponse"/>        </message>
    

    Modified

    <message name="response">       <part name="output_GetPhone" element="iWayResponse:jdeResponse"/>     </message>
    
  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 ESB project into the 11g system

  10. Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_jde9_getphone.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>. For example:

    Original

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

    Modified

    <serviceDefinition><wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ JDE90_GetPhone_invoke.wsdl?wsdl</wsdlURL>----------------------</endpointDefinition></serviceDefinition>
    
  11. Open and edit the DefaultSystem_ CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_jde9_getphone.esbsvc) in the reply validate section by adding .response in the tns namespace. For example:

    Original

    <reply validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" element="tns:jdeResponse" schemaLocation="esb:///ESB_Projects/Upgrade_testing_jde9_getphone_10134_jca_esb/JDE90_GetPhone_invoke.wsdl"/>
    

    Modified

    <reply validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" element="tns:jdeResponse" schemaLocation="esb:///ESB_Projects/Upgrade_testing_jde9_getphone_10134_jca_esb/JDE90_GetPhone_invoke.wsdl"/>
    
  12. Open and edit the DefaultSystem_FileAdapterName.esbsvc file created for the write operation (for example, DefaultSystem_write_getphone.esbsvc) in the request validate section by adding .response in the tns namespace. For example:

    Original

    <request validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" element="tns:jdeResponse"/>
    

    Modified

    <request validate="false" xmlns:tns="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" element="tns:jdeResponse"/>
    
  13. Open and edit the FileAdapterName.wsdl file created for the write operation (for example, write_getphone.wsdl) by adding .response. For example:

    Original

    <definitions name="write_getphone"targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"xmlns="http://schemas.xmlsoap.org/wsdl/"xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:imp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone"xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/file/"><import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone" location="JDE90_GetPhone_invoke.wsdl"/>
    

    Modified

    <definitions name="write_getphone"targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"            xmlns="http://schemas.xmlsoap.org/wsdl/"         xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/write_getphone/"           xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"          xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"xmlns:imp1="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response"           xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/file/"><import namespace="urn:iwaysoftware:jde/services/CALLBSFN/Addressbook/GetPhone.response" location="JDE90_GetPhone_invoke.wsdl"/>
    
  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.

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

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

  18. Click the Select an existing mapper file or create a new one button in the Transform Using field, as shown in Figure 5-6.

    Figure 5-6 Transform Using Field

    Transform Using field
    Description of "Figure 5-6 Transform Using Field"

    The Reply Transformation Map dialog is displayed, as shown in Figure 5-7.

    Figure 5-7 Reply Transformation Map Dialog

    Reply Transformation Map dialog
    Description of "Figure 5-7 Reply Transformation Map Dialog"

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

  20. Automap the iWayResponse:jdeResponse in the source and iWayResponse:jdeResponse in the target, as shown in Figure 5-8.

    Figure 5-8 Mapping Source To Target

    Mapping tab
    Description of "Figure 5-8 Mapping Source To Target"

    The Auto Map Preferences dialog is displayed, as shown in Figure 5-9.

    Figure 5-9 Auto Map Preferences Dialog

    Auto Map Preferences dialog
    Description of "Figure 5-9 Auto Map Preferences Dialog"

  21. Accept the default values and click OK.

    The automap is completed successfully, as shown in Figure 5-10.

    Figure 5-10 Completed Automap

    completed automap
    Description of "Figure 5-10 Completed Automap"

  22. Double click the composite.xml file.

  23. Save and then deploy the migrated ESB project.

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

  25. 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. 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.

  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 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> sections. For example:

    1. 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>http://192.168.128.122:80/orainfra/wsil/adapters/applications/jde90_SalesOrder_receive.wsdl?wsdl</wsdlURL>------------------</interface>
    

    2. 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>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ jde90_SalesOrder_receive.wsdl?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.