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

3 Oracle Application Adapter for Siebel Upgrade Guidelines

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

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

Selecting a WSDL From the Local File System

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

Selecting a WSDL Using Service Explorer

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

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

Selecting a WSDL From the Local File System

This section applies to Siebel 7.7 systems.

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

  2. Browse to a specific business object.

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

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

  5. Generate an inbound WSDL for this object.

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

    Original 10.1.3.4 WSDL

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

    Modified 10.1.3.4 WSDL

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

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

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

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

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

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

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

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  17. Save and then deploy the migrated ESB project.

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

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

This section applies to Siebel 7.0 systems.

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

  2. Browse to a specific business object.

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

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

  5. Generate an inbound WSDL for this object.

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

    Original 10.1.3.4 WSDL

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

    Modified 10.1.3.4 WSDL

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

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

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

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

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

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

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

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  17. Save and then deploy the migrated ESB project.

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

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

Selecting a WSDL Using Service Explorer

This section applies to Siebel 7.7 systems.

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

  2. Browse to a specific business object.

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

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

  5. Generate an inbound WSDL for this object.

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

    Original 10.1.3.4 WSDL

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

    Modified 10.1.3.4 WSDL

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

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

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

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

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

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

  13. Open the project folder and edit the files DefaultSystem_CustomAdapterServiceName.esbsvc (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc (for example, DefaultSystem_SA_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_SA.esbsvc)

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

    Modified (DefaultSystem_SA.esbsvc)

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

    2. Original (DefaultSystem_SA_RS.esbsvc)

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

    Modified (DefaultSystem_SA_RS.esbsvc)

    <serviceDefinition><wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ isdsrv22_SA_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>
    
  14. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  18. Save and then deploy the migrated ESB project.

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

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

This section applies to Siebel 7.0 systems.

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

  2. Browse to a specific business object.

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

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

  5. Generate an inbound WSDL for this object.

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

    Original 10.1.3.4 WSDL

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

    Modified 10.1.3.4 WSDL

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

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

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

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

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

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

  13. Open the project folder and edit the files DefaultSystem_CustomAdapterServiceName.esbsvc (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc (for example, DefaultSystem_SA_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_SA.esbsvc)

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

    Modified (DefaultSystem_SA.esbsvc)

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

    2. Original (DefaultSystem_SA_RS.esbsvc)

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

    Modified (DefaultSystem_SA_RS.esbsvc)

    <serviceDefinition><wsdlURL>http://192.168.128.122:80/orainfra/wsil/adapters/applications/ isdsrv22_SA_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>
    
  14. Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="ariba01_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  18. Save and then deploy the migrated ESB project.

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

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

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

Selecting a WSDL From the Local File System

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

Selecting a WSDL Using Service Explorer

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

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

Selecting a WSDL From the Local File System

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

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

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

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

  5. Restart the server.

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

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

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

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

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

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

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  15. Save and then deploy the migrated BPEL project.

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

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

Selecting a WSDL Using Service Explorer

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

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

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

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

  5. Restart the server.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    For example:

    <adapter-config name="samp_node" adapter="iWay ERP Adapter" wsdlLocation="isdsrv22_sampleAcct_receive.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"><resource-adapter className="com.iwaysoftware.afjca15.IWAFOracleResourceAdapter"/> <record-converter className="com.iwaysoftware.afjca15.oracle.InboundXMLRecordConverterImpl"/>
    
  17. Save and then deploy the migrated BPEL project.

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

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