SBL-EAI-08009: Error importing XML schema via method '%1' for '%2' '%3' in '%4'

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-08009: Error importing XML schema via method '%1' for '%2' '%3' in '%4'.

ScopeThis document is informational and intended for any user.

SBL-EAI-08009: Error importing XML schema via method '%1' for '%2' '%3' in '%4'.ExplanationThe XML schema contained in the WSDL document cannot be imported.

Corrective ActionCorrect the specified error in the XML schema or the WSDL document and restart the WSDL import.

















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.

Siebel Technical Support

keywords SBL-EAI-04340, SBL-EAI-04333, SBL-EAI-08009, SBL-EAI-09002

















Applies to: Siebel CRM - Version: 8.0.0.6 SIA [20423] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 12-JAN-2011***

Symptoms
The customer created an inbound web service in version 8.0.0.6 that invoked a custom business service. The WSDL generated by Siebel was not valid. For example, a WSDL compliance check in SOAPUI returned the following:

Failed Assertion BP2122.

Failure Message:

A wsdl:types element contained a data type definition that is not an XML schema definition.

Failure Detail Message:

Error: src-resolve: Cannot resolve the name 'xsdLocal1:DeleteWorkforce' to a(n) 'element declaration' component.
Error: src-resolve: Cannot resolve the name 'xsdLocal1:ModifyWorkforce' to a(n) 'element declaration' component.
Error: src-resolve: Cannot resolve the name 'xsdLocal1:WorkforceStatusChange' to a(n) 'element declaration' component.

Element Location:
lineNumber=3

Also, I consumed it using Tools and the following information was output:


“Integration object definitions to be generated:
ProcessModifiedWorkforce_Input for type/element:ProcessModifiedWorkforce_Input in namespace http://amgen.com/WorkforceClient

Following are warnings generated in the process:

The http://schemas.xmlsoap.org/wsdl/:operation 'ProcessNewWorkforce' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ProcessNewWorkforce_Input' in 'http://amgen.com/WorkforceClient'(SBL-EAI-08009)
Cannot find global 'element' declaration for name: 'http://amgen.com/types:NewWorkforce'.(SBL-EAI-09001)

The http://schemas.xmlsoap.org/wsdl/:operation 'ProcessDeletedWorkforce' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ProcessDeletedWorkforce_Input' in 'http://amgen.com/WorkforceClient'(SBL-EAI-08009)
Cannot find global 'element' declaration for name: 'http://amgen.com/types:DeleteWorkforce'.(SBL-EAI-09001)

The http://schemas.xmlsoap.org/wsdl/:operation 'ProcessWorkforceStatusChange' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ProcessWorkforceStatusChange_Input' in 'http://amgen.com/WorkforceClient'(SBL-EAI-08009)
Cannot find global 'element' declaration for name: 'http://amgen.com/types:WorkforceStatusChange'.(SBL-EAI-09001)”

CauseThe business service included 4 methods; DeleteWorkforce, ModifyWorkforce, NewWorkforce and WorkforceStatusChange. It appears that the problem was related to the fact that each of the methods referenced a different IO and all 4 IOs included the following integration object user properties:

Name	Value
XMLTagNamespace	http://amgen.com/types
XSDTypeNamespace	http://amgen.com/types

SolutionNamespaces are used to provide uniqueness. The WSDL generated by Siebel passed a SOAPUI compliance check and could be consumed in Tools after the IO user properties were modified as follows to make each one unique:

DeleteWorkforce

XMLTagNamespace, http://amgen.com/types1
XSDTypeNamespace, http://amgen.com/types1
ModifyWorkforce

XMLTagNamespace, http://amgen.com/types2
XSDTypeNamespace, http://amgen.com/types2

NewWorkforce

XMLTagNamespace, http://amgen.com/types3
XSDTypeNamespace, http://amgen.com/types3
WorkforceStatusChange

XMLTagNamespace, http://amgen.com/types4
XSDTypeNamespace, http://amgen.com/types4


















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

























Applies to: Siebel System Software - Version: 7.8.2.5 SIA [19227] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Solaris Operating System (SPARC 64-bit)
Product Release: V7 (Professional)
Version: 7.7.2.2 [18356]
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: HP 9000 Series HP-UX

This document was previously published as Siebel SR 38-2217436991.
""""Checked for relevance on 29-OCT-2010""""

SymptomsSBL-EAI-09004, SBL-UNU-00247

Hi,

I am importing a wsdl file using the web service wizard for connectivity to an external soap web service.

I am getting the following error messages:


The http://schemas.xmlsoap.org/wsdl/:operation 'updateDocument' was ignored. Error importing XML schema via method 'GetIntObjByType' for 'type' 'ContentBean' in 'urn:IQuadContentService'(SBL-EAI-08009)
XML Schema document located at 'http://www.w3.org/2001/XMLSchema.xsd' could not be parsed.(SBL-EAI-09004)
Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL 'http://www.w3.org/2001/XMLSchema.xsd'(SBL-UNU-00247)

Fatal Error in XML Parser at line 0, column 0: An exception occurred! Type:NetAccessorException, Message:The host/address 'www.w3.org' could not be resolved(SBL-UNU-00247)


This looks like there is a connectivity issue to the internet, but the internet connectivity seems fine on the PC I am using. Also I have been able to import a different wsdl which points to a public soap service which imports fine and also uses the same xml schema file available on the internet at w3.org. I have attached the log file and wsdl file which is causing us the problem.

Causefeature unavailable. Tools needs file access to xsd files referenced in the WSDL.

Solution
The same wsdl could be imported by Siebel Technical Support without error. The reason for the error at the customer site was due to the use of a proxy server (check Explorer > Tools > Internet Options > Connections, and click LAN Setting). One suggestion was to configure the settings to bypass the proxy server for the www.w3.org urls. The customer instead used a dial up connection to avoid the proxy server, and was able to import the wsdl ok.


BUG: 10483854 has previously been logged to request that Tools support use of a proxy server when accessing the url (still open at the time of writing).



ReferencesBUG:10483854 - TOOLS MUST SUPPORT A PROXY SERVER WHEN IMPORTING WSDL
NOTE:1076251.1 - Master Note for Siebel Web Services




















Applies to: Siebel System Software - Version: 7.8.2.2 [19219] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.2 [19219]
Database: Oracle 9.2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 4.1.4 RS/6000

This document was previously published as Siebel SR 38-3054195451.
***Checked for relevance on 20-DEC-2010***

SymptomsA WSDL file contains 3 tags for schema definitions.
When we import the WSDL Siebel returns an error that it was not able to find the definition of the 'ClauseTextReply' message which is located in the 3rd schema tag.

Port 'GetClausePort' can not be imported. PortType 'GetClausePortType' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'GetClause' was ignored. Error importing XML schema via method 'GetIntObjByElement' for 'element' 'ClauseTextReply' in 'http://<hostname>/siebel-get-clause/'(SBL-EAI-08009)
Cannot find global 'element' declaration for name: 'http://<hostname>/siebel-get-clause/:ClauseTextReply'.(SBL-EAI-09001)

WSDL Example:

<wsdl:types>
<xs:schema targetNamespace="http://<webserver1>/bebop/weaheader_1_1" elementFormDefault="qualified">
<xs:element name="MessageHeader">
...
</xs:schema>
<xs:schema xmlns:wea="http://<webserver1>/bebop/weaheader_1_1" targetNamespace="http://<webserver2>/siebel-get-clause/">
<xs:element name="ClauseTextRequest">
...
</xs:schema>
<xs:schema xmlns:wea="http://<webserver1>/bebop/weaheader_1_1" targetNamespace="http://<webserver2>/siebel-get-clause/">
<xs:element name="ClauseTextReply">
...
</xs:schema>
</wsdl:types>



CauseThere were two schema definitions with the same namespaces and Siebel was not reading the definitions of the last one.

WSDL with problems:

<wsdl:types>
...
<xs:schema xmlns:wea="http://www.server.com/weaheader_1_1" targetNamespace="http://test.server.com/siebel-get-clause/">
<xs:element name="ClauseTextRequest">
...
</xs:schema>
<xs:schema xmlns:wea="http://www.server.com/weaheader_1_1" targetNamespace="http://test.server.com.com/siebel-get-clause/">
<xs:element name="ClauseTextReply">
...
</xs:schema>
</wsdl:types>



As per the WS-I BP 1.0 definition to which Siebel conforms, having two schemas with the same namespace is accepted as shown below:

"R2114: The target namespace for WSDL definitions and the target namespace for schema definitions in a DESCRIPTION MAY be the same."

Defect 12-1EKVEBJ has been raised to address this issue to a future version

SolutionIn this particular case, the issue was solved by removing the second schema definition from the WSDL.
It was possible because both schemas were the same.
Below is the working WSDL:


<wsdl:types>
...
<xs:schema xmlns:wea="http://www.server.com/weaheader_1_1" targetNamespace="http://test.server.com/siebel-get-clause/">
<xs:element name="ClauseTextRequest">
...
<xs:element name="ClauseTextReply">
...
</xs:schema>
</wsdl:types>


ReferencesBUG:10509505 - ERROR WHEN IMPORTING WSDL WITH 2 EQUAL SCHEMAS

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software Keywords
IMPORT WSDL; RETURNED AN ERROR
Errors
SBL-EAI-08009; SBL-EAI-09001