Applies to: Siebel Call Center - Version: 8.0.0.9[20433] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsWhen attempt to import WSDL document that imports another schema using <import> element into Siebel Tools the following error occurs:-
Port 'PickupDespatch_162_BPELPort' can not be imported. PortType 'PickupDespatch_162_BPEL' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ListOfTollPriorityOrderResponseIo' in 'http://www.siebel.com/xml/TOLL%20Priority%20Order%20Response%20IO'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.siebel.com/xml/TOLL%20Priority%20Order%20Response%20IO'(SBL-EAI-09002)
.(SBL-EAI-04331)
.
CauseOn reviewing the WSDL document, it was found that the <schema> element does not have 'targetNamespace' attribute for the imported schema while it has different namespace for the schema (XSD file) that is being imported.
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="urn:tollgroup:service:PickupDespatch_162_BPEL">
<import namespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
schemaLocation="SiebelOrderRequest_162_v1_0.xsd"/>
SolutionWhen the namespace attribute is specified in the import element, it only be used to import schemas in a different namespaces as the targetnamespace of the enclosing schema element.
To implement the recommended solution, add the targetNamespace attribute to the schema element as the namesapce specified in the import element.
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="urn:tollgroup:service:PickupDespatch_162_BPEL"
targetNamespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO">
<import namespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
schemaLocation="SiebelOrderRequest_162_v1_0.xsd"/>
Applies to: Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 12-Nov-2010***
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4
This document was previously published as Siebel SR 38-1737275741.
SymptomsSBL-EAI-08009, SBL-EAI-09002, SBL-EAI-04333, SBL-EAI-04340
HI,
when importing a WSDL file in Tools, the import fails with the following error message:
***********************************************************
Project: ATP
WSDL file to import: d:\Profiles\MCHERECH\Desktop\createFSCDID.wsdl
Run-time configuration data file: d:\Profiles\MCHERECH\Desktop\createFSCDID.xml
Log File: d:\Profiles\MCHERECH\Desktop\createFSCDID.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'FSCCorporateERMSync_SiebelERMService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'FSCCorporateERMSync_SiebelERMPort0' can not be imported. PortType 'FSCCorporateERMSync_SiebelERMPortType' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'createFSCDID' was ignored. Error importing XML schema via method 'IsSimpleType' for 'type' '__webService_output' in ''(SBL-EAI-08009)
Cannot find schema with targetNamespace: ''(SBL-EAI-09002)
***********************************************************
We are following the steps outlined in Bookshelf.
Regards,
Elmar
SolutionMessage 1Hello Elmar,
Thank you for using the Siebel SupportWeb.
For the benefit of other readers, the following errors were reported when importing a wsdl file in Tools, using the EAI wizard :-
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'FSCCorporateERMSync_SiebelERMService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'FSCCorporateERMSync_SiebelERMPort0' can not be imported. PortType 'FSCCorporateERMSync_SiebelERMPortType' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'createFSCDID' was ignored. Error importing XML schema via method 'IsSimpleType' for 'type' '__webService_output' in ''(SBL-EAI-08009)
Cannot find schema with targetNamespace: ''(SBL-EAI-09002)
[cont]
Message 2[cont]
The error message was indicating a problem processing the type ‘__webService_output’. On reviewing the wsdl, it was noticed that was no namespace declared for the message in the type attribute :-
<wsdl:message name="createFSCDIDOutput">
<wsdl:part name="Output" type="__webService_output"/>
</wsdl:message>
This was replaced with :-
<wsdl:message name="createFSCDIDOutput">
<wsdl:part name="Output" type="tns:__webService_output"/>
</wsdl:message>
Also, in the schema declaration for Output there is also no namespace in the type attribute :-
<xsd:sequence>
<xsd:element name="Output" nillable="true" type="__webService_output"/>
</xsd:sequence>
This was replaced with :-
<xsd:sequence>
<xsd:element name="Output" nillable="true" type="tns:__webService_output"/>
</xsd:sequence>
With the the above changes, the wsdl could be imported without errors.
Applies to: Siebel CRM - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 04-Jan-2011***
SymptomsWhen I try to import a WSDL File, I'm getting following errors.
Project: CM Interface
WSDL file to import: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.wsdl
Run-time configuration data file: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.xml
Log File: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'BPEL_CAMB_DOMICILIOS' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'BPEL_CAMB_DOMICILIOSPort' can not be imported. PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.cablemas.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
.(SBL-EAI-04331)
CauseIncreasing the Tools Client log the additional information was collected.
a) Instructions to increase Tools Client log.
You have to set the following System Environment Variables:
SIEBEL_LOG_EVENTS=5
To set up environment variables perform the following steps:
Start > Settings > Control Panel > System.
Click on the Advanced tab and then click on the Environment Variables button.
Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished. After that, you have to restart the Tools Client.
The detailed siebdev.log file should be generated.
b) In the siebdev.log file
WebSvcDesign XSDImpWarning 2 000000024a520670:0 2009-07-06 17:53:49 [0] Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=file:///C:\Shared\WSDL2\INT-210-BPEL-CAMB_DOMICILIOS.xsd(SBL-EAI-00247) (IDS_XMLCNV_ERR_FTLPARSE)
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (xsdcontext.cpp (693)) SBL-EAI-09004: XML Schema document located at 'INT-210-BPEL-CAMB_DOMICILIOS.xsd' could not be parsed.
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (wsimpwiz.cpp (2163)) SBL-EAI-04331: PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
c) As the error log indicated the WSDL file points to an xsd file that could not be imported because it does not exist in the same directory where the WSDL file is located.
The following import instruction in the WSDL file triggers this event.
<import namespace="http://www.server.com/SBLCambioDomicilios" schemaLocation="INT-210-BPEL-CAMB_DOMICILIOS.xsd"/>
SolutionPlease move the XSD file to the same directory where the WSDL file is located.
Best Regards
Oracle Support
ReferencesNOTE:1076251.1 - Master Note for Siebel Web Services
Information in this document applies to any platform.
SymptomsWhen attempt to import WSDL document that imports another schema using <import> element into Siebel Tools the following error occurs:-
Port 'PickupDespatch_162_BPELPort' can not be imported. PortType 'PickupDespatch_162_BPEL' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ListOfTollPriorityOrderResponseIo' in 'http://www.siebel.com/xml/TOLL%20Priority%20Order%20Response%20IO'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.siebel.com/xml/TOLL%20Priority%20Order%20Response%20IO'(SBL-EAI-09002)
.(SBL-EAI-04331)
.
CauseOn reviewing the WSDL document, it was found that the <schema> element does not have 'targetNamespace' attribute for the imported schema while it has different namespace for the schema (XSD file) that is being imported.
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="urn:tollgroup:service:PickupDespatch_162_BPEL">
<import namespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
schemaLocation="SiebelOrderRequest_162_v1_0.xsd"/>
SolutionWhen the namespace attribute is specified in the import element, it only be used to import schemas in a different namespaces as the targetnamespace of the enclosing schema element.
To implement the recommended solution, add the targetNamespace attribute to the schema element as the namesapce specified in the import element.
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="urn:tollgroup:service:PickupDespatch_162_BPEL"
targetNamespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO">
<import namespace="http://www.siebel.com/xml/TOLL%20Priority%20Order%20Request%20IO"
schemaLocation="SiebelOrderRequest_162_v1_0.xsd"/>
Applies to: Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 12-Nov-2010***
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4
This document was previously published as Siebel SR 38-1737275741.
SymptomsSBL-EAI-08009, SBL-EAI-09002, SBL-EAI-04333, SBL-EAI-04340
HI,
when importing a WSDL file in Tools, the import fails with the following error message:
***********************************************************
Project: ATP
WSDL file to import: d:\Profiles\MCHERECH\Desktop\createFSCDID.wsdl
Run-time configuration data file: d:\Profiles\MCHERECH\Desktop\createFSCDID.xml
Log File: d:\Profiles\MCHERECH\Desktop\createFSCDID.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'FSCCorporateERMSync_SiebelERMService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'FSCCorporateERMSync_SiebelERMPort0' can not be imported. PortType 'FSCCorporateERMSync_SiebelERMPortType' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'createFSCDID' was ignored. Error importing XML schema via method 'IsSimpleType' for 'type' '__webService_output' in ''(SBL-EAI-08009)
Cannot find schema with targetNamespace: ''(SBL-EAI-09002)
***********************************************************
We are following the steps outlined in Bookshelf.
Regards,
Elmar
SolutionMessage 1Hello Elmar,
Thank you for using the Siebel SupportWeb.
For the benefit of other readers, the following errors were reported when importing a wsdl file in Tools, using the EAI wizard :-
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'FSCCorporateERMSync_SiebelERMService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'FSCCorporateERMSync_SiebelERMPort0' can not be imported. PortType 'FSCCorporateERMSync_SiebelERMPortType' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'createFSCDID' was ignored. Error importing XML schema via method 'IsSimpleType' for 'type' '__webService_output' in ''(SBL-EAI-08009)
Cannot find schema with targetNamespace: ''(SBL-EAI-09002)
[cont]
Message 2[cont]
The error message was indicating a problem processing the type ‘__webService_output’. On reviewing the wsdl, it was noticed that was no namespace declared for the message in the type attribute :-
<wsdl:message name="createFSCDIDOutput">
<wsdl:part name="Output" type="__webService_output"/>
</wsdl:message>
This was replaced with :-
<wsdl:message name="createFSCDIDOutput">
<wsdl:part name="Output" type="tns:__webService_output"/>
</wsdl:message>
Also, in the schema declaration for Output there is also no namespace in the type attribute :-
<xsd:sequence>
<xsd:element name="Output" nillable="true" type="__webService_output"/>
</xsd:sequence>
This was replaced with :-
<xsd:sequence>
<xsd:element name="Output" nillable="true" type="tns:__webService_output"/>
</xsd:sequence>
With the the above changes, the wsdl could be imported without errors.
Applies to: Siebel CRM - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 04-Jan-2011***
SymptomsWhen I try to import a WSDL File, I'm getting following errors.
Project: CM Interface
WSDL file to import: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.wsdl
Run-time configuration data file: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.xml
Log File: C:\Documents and Settings\Edgar\Escritorio\Interfaces\BPEL_CAMB_DOMICILIOS\BPEL_CAMB_DOMICILIOS.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'BPEL_CAMB_DOMICILIOS' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'BPEL_CAMB_DOMICILIOSPort' can not be imported. PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.cablemas.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
.(SBL-EAI-04331)
CauseIncreasing the Tools Client log the additional information was collected.
a) Instructions to increase Tools Client log.
You have to set the following System Environment Variables:
SIEBEL_LOG_EVENTS=5
To set up environment variables perform the following steps:
Start > Settings > Control Panel > System.
Click on the Advanced tab and then click on the Environment Variables button.
Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished. After that, you have to restart the Tools Client.
The detailed siebdev.log file should be generated.
b) In the siebdev.log file
WebSvcDesign XSDImpWarning 2 000000024a520670:0 2009-07-06 17:53:49 [0] Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=file:///C:\Shared\WSDL2\INT-210-BPEL-CAMB_DOMICILIOS.xsd(SBL-EAI-00247) (IDS_XMLCNV_ERR_FTLPARSE)
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (xsdcontext.cpp (693)) SBL-EAI-09004: XML Schema document located at 'INT-210-BPEL-CAMB_DOMICILIOS.xsd' could not be parsed.
ObjMgrLog Error 1 000000024a520670:0 2009-07-06 17:53:49 (wsimpwiz.cpp (2163)) SBL-EAI-04331: PortType 'BPEL_CAMB_DOMICILIOS' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'process' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'SBLCambioDomiciliosRequest' in 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-08009)
Cannot find schema with targetNamespace: 'http://www.server.com/SBLCambioDomicilios'(SBL-EAI-09002)
c) As the error log indicated the WSDL file points to an xsd file that could not be imported because it does not exist in the same directory where the WSDL file is located.
The following import instruction in the WSDL file triggers this event.
<import namespace="http://www.server.com/SBLCambioDomicilios" schemaLocation="INT-210-BPEL-CAMB_DOMICILIOS.xsd"/>
SolutionPlease move the XSD file to the same directory where the WSDL file is located.
Best Regards
Oracle Support
ReferencesNOTE:1076251.1 - Master Note for Siebel Web Services
Related
Products
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM
Keywords
| |
WSDL; IMPORT; RUN-TIME; IDS_XMLCNV_ERR_FTLPARSE; XSD
| |
Errors
| |
SBL-EAI-04340; SBL-EAI-08009; SBL-EAI-09004; SBL-EAI-04331; SBL-EAI-04333; SBL-EAI-00247; SBL-EAI-09002; ERROR 1
| |
No comments:
Post a Comment