This chapter lists and describes upgrade guidelines that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:
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".
Selecting a WSDL From the Local File System
This section applies to Siebel 7.7 systems.
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.
Browse to a specific business object.
Create an Integration Object node by selecting a Siebel generated schema file (.xsd) using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate an inbound WSDL for this object.
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"/>
Restart the server.
Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.
In the Custom Adapter service, select the inbound WSDL from the local file system.
Deploy the ESB project successfully and ensure the registration of the ESB project is successful.
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).
Copy the deployed ESB project into the 11g system.
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated ESB project.
Ensure that there are no error or warning messages during the deployment process.
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.
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.
Browse to a specific business object.
Create an Integration Object node by selecting a Siebel generated schema file (.xdr) using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate an inbound WSDL for this object.
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"/>
Restart the server.
Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.
In the Custom Adapter service, select the inbound WSDL from the local file system.
Deploy the ESB project successfully and ensure the registration of the ESB project is successful.
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).
Copy the deployed ESB project into the 11g system.
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated ESB project.
Ensure that there are no error or warning messages during the deployment process.
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.
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.
Browse to a specific business object.
Create an Integration Object node by selecting a Siebel generated schema file (.xsd) using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate an inbound WSDL for this object.
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"/>
Restart the server.
Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.
In the Custom Adapter service, select the inbound WSDL using Service Explorer.
Deploy the ESB project successfully and ensure the registration of the ESB project is successful.
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).
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.Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_SA_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
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> isdsrv22_SA_receive.wsdl </wsdlURL>------------------------</interface>
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> isdsrv22_SA_receive.wsdl </wsdlURL>---------------------</endpointDefinition></serviceDefinition>
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated ESB project.
Ensure that there are no error or warning messages during the deployment process.
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.
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.
Browse to a specific business object.
Create an Integration Object node by selecting a Siebel generated schema file (.xdr) using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate an inbound WSDL for this object.
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"/>
Restart the server.
Start Oracle JDeveloper 10.1.3.4 and create a JCA inbound ESB Project.
In the Custom Adapter service, select the inbound WSDL using Service Explorer.
Deploy the ESB project successfully and ensure the registration of the ESB project is successful.
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).
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.Open the project folder and edit the DefaultSystem_CustomAdapterServiceName.esbsvc file (for example, DefaultSystem_SA.esbsvc) and DefaultSystem_CustomAdapterServiceName_RS.esbsvc file (for example, DefaultSystem_SA_RS.esbsvc) by modifying the WSDL URL in the serviceDefinition section. For example:
Original (DefaultSystem_SA.esbsvc)
<interface> <wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ ariba01_SA_receive.wsdl?wsdl</wsdlURL>------------------</interface>
Modified (DefaultSystem_SA.esbsvc)
<interface><wsdlURL> ariba01_SA_receive.wsdl </wsdlURL>------------------------</interface>
Original (DefaultSystem_SA_RS.esbsvc)
<serviceDefinition><wsdlURL>http://127.0.0.1:80/orainfra/wsil/adapters/applications/ ariba01_SA_receive.wsdl?wsdl</wsdlURL>--------------------------</endpointDefinition></serviceDefinition>
Modified (DefaultSystem_SA_RS.esbsvc)
<serviceDefinition><wsdlURL> ariba01_SA_receive.wsdl </wsdlURL>---------------------</endpointDefinition></serviceDefinition>
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 ESB project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated ESB project.
Ensure that there are no error or warning messages during the deployment process.
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 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".
Selecting a WSDL From the Local File System
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.
Browse to the particular business object. Create an Integration Object node by selecting the Siebel generated XSD/XDR file using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate the inbound WSDL for the specific business object.
Restart the server.
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
Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.
Trigger the event messages from the Siebel system and ensure that successful instances are received in the BPEL Console.
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).
Copy the deployed BPEL project into the 11g system.
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated BPEL project.
Ensure that there are no error or warning messages during the deployment process.
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
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.
Browse to the particular business object. Create an Integration Object node by selecting the Siebel generated XSD/XDR file using Application Explorer.
Create a new HTTP channel for Oracle Application Adapter for SAP R/3.
Generate the inbound WSDL for the specific business object.
Restart the server.
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
Deploy the BPEL project successfully and ensure that there are no error or warning messages during the deployment process.
Trigger the event messages from the Siebel system and ensure that successful instances are received in the BPEL Console.
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).
Copy the deployed BPEL project into the 11g system.
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.
Ensure that the 10.1.3.4 server is up and running.
Start Oracle JDeveloper 11g and migrate the 10.1.3.4 BPEL project.
Once the project is migrated, a successful message is received in Oracle JDeveloper.
Expand the migrated project and double-click the composite.xml file to ensure that the project opens without any errors.
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"/>
Save and then deploy the migrated BPEL project.
Ensure that there are no error or warning messages during the deployment process.
Trigger the event messages from the Siebel system and ensure that successful instances are received in the Oracle Enterprise Manager console.