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.

This chapter contains the following examples:

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

Selecting a WSDL From the Local File System

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

Selecting a WSDL Using Service Explorer

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

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

Selecting a WSDL From the Local File System

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

  2. Browse to a specific business object.

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

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

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

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

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

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

    Change 1

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

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

    to:

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

    Change 2

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

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

    Change 3

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

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

    to:

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

  8. Restart the server.

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

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

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

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

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

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

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

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

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

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

    For example:

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

  18. Save and then deploy the migrated ESB project.

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

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

Selecting a WSDL Using Service Explorer

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

  2. Browse to a specific business object.

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

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

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

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

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

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

    Change 1

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

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

    to:

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

    Change 2

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

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

    Change 3

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

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

    to:

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

  8. Restart the server.

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

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

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

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

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

    Note:

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

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

    Original (DefaultSystem_SalesOrder.esbsvc)

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

    Modified (DefaultSystem_SalesOrder.esbsvc)

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

    Original (DefaultSystem_SalesOrder_RS.esbsvc)

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

    Modified (DefaultSystem_SalesOrder_RS.esbsvc)

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

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

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

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

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

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

    For example:

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

  19. Save and then deploy the migrated ESB project.

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

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

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

Selecting a WSDL From the Local File System

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

Selecting a WSDL Using Service Explorer

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

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

Selecting a WSDL From the Local File System

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

  2. Browse to a specific business object.

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

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

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

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

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

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

    Change 1

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

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

    to:

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

    Change 2

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

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

    Change 3

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

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

    to:

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

  8. Restart the server.

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

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

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

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

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

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

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

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

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

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

    For example:

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

  18. Save and then deploy the migrated BPEL project.

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

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

Selecting a WSDL Using Service Explorer

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

  2. Browse to a specific business object.

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

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

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

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

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

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

    Change 1

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

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

    to:

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

    Change 2

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

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

    Change 3

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

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

    to:

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

  8. Restart the server.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    For example:

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

  20. Save and then deploy the migrated BPEL project.

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

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