2 Oracle Application Adapter for SAP R/3 Upgrade Guidelines

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

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

Selecting a WSDL From the Local File System

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

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

  3. Restart the server.

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

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

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

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

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

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

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

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

  12. Save and then deploy the migrated ESB project.

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

  14. Once the deployment is successful, navigate to the input folder and paste the input XML file.

    The successful response XML is received in the specified output folder.

Selecting a WSDL Using Service Explorer

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

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

  3. Restart the server.

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

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

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

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

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

    Note:

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

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

    Original

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

    Modified

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

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

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

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

  13. Save and then deploy the migrated ESB project.

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

  15. Once the deployment is successful, navigate to the input folder and paste the input XML file.

    The successful response XML is received in the specified output folder.

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

Selecting a WSDL From the Local File System

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

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

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

  4. Restart the server.

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

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

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

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

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

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

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

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

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

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

    For example:

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

  14. Save and then deploy the migrated ESB project.

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

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

Selecting a WSDL Using Service Explorer

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

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

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

  4. Restart the server.

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

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

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

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

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

    Note:

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

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

    Original (DefaultSystem_matmas01_esb.esbsvc)

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

    Modified (DefaultSystem_matmas01_esb.esbsvc)

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

    Original (DefaultSystem_matmas01_esb_RS.esbsvc)

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

    Modified (DefaultSystem_matmas01_esb_RS.esbsvc)

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

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

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

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

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

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

    For example:

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

  15. Save and then deploy the migrated ESB project.

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

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

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

Selecting a WSDL From the Local File System

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

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

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

  4. Restart the server.

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

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

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

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

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

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

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

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

  13. Save and then deploy the migrated BPEL project.

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

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

Selecting a WSDL Using Service Explorer

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

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

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

  4. Restart the server.

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

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

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

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

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

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

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

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

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

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

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

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

  15. Save and then deploy the migrated BPEL project.

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

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

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

Selecting a WSDL From the Local File System

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

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

  3. Browse to a specific business object.

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

  5. Restart the server.

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

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

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

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

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

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

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

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

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

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

    For example:

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

  15. Save and then deploy the migrated BPEL project.

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

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

Selecting a WSDL Using Service Explorer

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

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

  3. Browse to a specific business object.

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

  5. Restart the server.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    For example:

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

  17. Save and then deploy the migrated BPEL project.

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

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