Siebel System Software - Version: 7.5.3.3 [16172] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1168496881.
***Checked for relevance on 06-JAN-2011***
Symptoms
The customer used the WSDL Import Wizard of Siebel Tools 7.5.3 to import an external Web Service definition (a .WSDL file) with several:
WSDL-elements referred to external XML Schema definitions (.XSD files).
In some of these XML Schemas definitions, several:
XSD-elements were also used to refer some common XML Sub-schemas (.XSD files)
The wizard failed with
"... (SBL-EAI-04331) PortType '... ' can not be imported. The operation '...' was ignored. EAI Common Internal Error: Cannot find schema with targetNamespace: '...' (SBL-UNU-00133) ..."
Cause
The reported behavior was reproduced (using the customer examples) with the Siebel Tools 7.5.3.3.
Following points were identified:
(1) 'WSDL:import' statements can be processed correctly, if .WSDL file contains the default(!) XML namespace definition for WSDL: '<...definitions ... xmlns="http://schemas.xmlsoap.org/wsdl/" ...' (2) 'XSD:import' statement(s) in .XSD files are ignored. The wrong interpretation of the schema location URL of the 'xsd:import' tag was identified as a product defect, addressed via the Change Request 10466449. This has been fixed as of Siebel Tools version 7.7. Solution To workaround this case in the Siebel Tools 7.5.x, either move all nested 'xsd:import's into the .WSDL file as accordant 'wsdl:imports syntax or modify all .XSD files referred via 'wsdl:import' tags to have it as complete XSD-definitions without 'xsd:import' sub-includes. In additional, it was identified, what extensive application of the
So the import will be stopped with the message like"... Method 'SetFieldValue' of business component 'Repository Integration Component' (integration component 'Repository Integration Component') ... returned the following error:"Value too long for field 'Comments' (maximum size 250).(SBL-DAT-00235)"(SBL-EAI-04375) ..."
To solve this case, please consider to modify .WSDL and .XSD files to remove/short all 'annotation' tags.
The Change Request 10472380 has been filed to ask for a product enhancement to allow the WSDL Import Wizard to not stop the import process in case of the 'Comments' field overflow. This will be reviewed and prioritized for whether to be implemented in the future product versions.
References
BUG:10472380 - WSDL WITH EXTENSIVE NODES USAGE CAN NOT BE IMPORTED.
BUG:10466449 - WSDL IMPORT WIZARD IS HAVING PROBLEMS IMPORTING WSDL FILE THAT HAS "IMPORT" STATEMENTS
Applies to:
Siebel System Software - Version: 7.5.3.3 [16172] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1168496881.
***Checked for relevance on 06-JAN-2011***
Symptoms
The customer used the WSDL Import Wizard of Siebel Tools 7.5.3 to import an external Web Service definition (a .WSDL file) with several:
WSDL-elements referred to external XML Schema definitions (.XSD files).
In some of these XML Schemas definitions, several:
XSD-elements were also used to refer some common XML Sub-schemas (.XSD files)
The wizard failed with
"... (SBL-EAI-04331) PortType '... ' can not be imported. The operation '...' was ignored. EAI Common Internal Error: Cannot find schema with targetNamespace: '...' (SBL-UNU-00133) ..."
Cause
The reported behavior was reproduced (using the customer examples) with the Siebel Tools 7.5.3.3.
Following points were identified:
(1) 'WSDL:import' statements can be processed correctly, if .WSDL file contains the default(!) XML namespace definition for WSDL: '<...definitions ... xmlns="http://schemas.xmlsoap.org/wsdl/" ...' (2) 'XSD:import' statement(s) in .XSD files are ignored. The wrong interpretation of the schema location URL of the 'xsd:import' tag was identified as a product defect, addressed via the Change Request 10466449. This has been fixed as of Siebel Tools version 7.7. Solution To workaround this case in the Siebel Tools 7.5.x, either move all nested 'xsd:import's into the .WSDL file as accordant 'wsdl:imports syntax or modify all .XSD files referred via 'wsdl:import' tags to have it as complete XSD-definitions without 'xsd:import' sub-includes. In additional, it was identified, what extensive application of the
So the import will be stopped with the message like"... Method 'SetFieldValue' of business component 'Repository Integration Component' (integration component 'Repository Integration Component') ... returned the following error:"Value too long for field 'Comments' (maximum size 250).(SBL-DAT-00235)"(SBL-EAI-04375) ..."
To solve this case, please consider to modify .WSDL and .XSD files to remove/short all 'annotation' tags.
The Change Request 10472380 has been filed to ask for a product enhancement to allow the WSDL Import Wizard to not stop the import process in case of the 'Comments' field overflow. This will be reviewed and prioritized for whether to be implemented in the future product versions.
References
BUG:10472380 - WSDL WITH EXTENSIVE NODES USAGE CAN NOT BE IMPORTED.
BUG:10466449 - WSDL IMPORT WIZARD IS HAVING PROBLEMS IMPORTING WSDL FILE THAT HAS "IMPORT" STATEMENTS
Applies to:
Siebel Call Center - Version: 7.5.3.16 [16284] and later [Release: V7 and later ]
Information in this document applies to any platform.
***Checked for relevance on 02-FEB-2011***
Symptoms
The following error was encountered while trying to import the a WSDL in Siebel Tools:-
-----------------------------
Project: SUMA WS
WSDL file to import: C:\001_002\WS\Suma_grabar_llamada.wsdl
Run-time configuration data file: C:\001_002\WS\Suma_grabar_llamada.xml
Log File: C:\001_002\WS\Suma_grabar_llamada.log
Errors during processing:
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'Suma_grabar_llamada' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'Suma_grabar_llamada_Port' can not be imported. PortType 'Suma_grabar_llamada_PortType' can not be imported. The operation 'Suma_grabar_llamada' was ignored. EAI Common Internal Error: Cannot find global type declaration for name: 'http://www.w3.org/2001/XMLSchema:Suma_grabar_llamada_entranteXMLType'(SBL-UNU-00133)
.(SBL-EAI-04331)
.
-------------------------------------
Cause
The problem was caused due to incorrect 'targetNamespace' reference for wsdl message type.
Fom the definitions in the WSDL, it can be seen that the 'targetNamespace' for the schema 'types' pointed to the namespace "http://www.siebel.com/xml/SUMASRWS". From the WSDL:
----------------------
…
…
------------------------
However, the message type for the operation 'Suma_grabar_llamada' (PortType 'Suma_grabar_llamada_PortType') was defined as below (note that the namespace qualifier for the message 'type' is 'xsd:'):
--------------------------------
...
...
---------------------------------
where 'xsd' is defined in the wsdl as:-
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
This is not correct! This is because it is necessary for the user defined types to be referred correctly in association with their namespaces (for the WSDL to be consumed successfully).
Since reference to a 'type' (or element per se) with the namespace qualifier e.g 'tns1:Suma_grabar_llamada_entranteXMLType' is equivalent to referring to it with its namespace (e.g
'http://www.siebel.com/xml/SUMASRWS:Suma_grabar_llamada_entranteXMLType') where 'tns1' is defined as :
xmlns:tns1=http://www.siebel.com/xml/SUMASRWS
it is necessary that the 'targetNamespace' of the wsdl 'types' and the namespace qualifier used to define the message type belong to the same namespace (i.e http://www.siebel.com/xml/SUMASRWS).
Solution
On modifying the WSDL (as below) it could be successfully imported in Siebel Tools:
1) In the WSDL , the namespace "http://www.siebel.com/xml/SUMASRWS" (which is declared in the targetNamespace') was defined as below:
--------------
definitions name="suma_grabar_llamada" (...)xmlns:tns1="http://www.siebel.com/xml/SUMASRWS">
--------------
2) The 'type' declaration of the WSDL message 'part' was modified to refer to 'tns1' instead of 'xsd' (as below):-
-------------
------------------
Kind Regards
Oracle Customer Support
Related
--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Call Center
Keywords
--------------------------------------------------------------------------------
WSDL; NAMESPACE; IMPORT; IMPORT WSDL
Errors
--------------------------------------------------------------------------------
SBL-EAI-04340; SBL-UNU-00133; SBL-EAI-04331; SBL-EAI-04333; 00133 ERROR
Applies to:
Siebel System Software - Version: 7.5.3.15 [16279] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.15 [16279]
Database: Oracle 9.2.0.6
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-3212917851.
***Checked for relevance on 06-JAN-2011***
Symptoms
An error message is reported when trying to consume siebel 7.8 CalculatePriceWS webservice in Siebel 7.5 instance :-
There are no web service definitions to be generated.(SBL-EAI-04340)
Following are warnings generated in the process:
Service 'xx' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
Port 'xx' can not be imported. PortType 'xx' can not be imported. The http://schemas.xmlsoap.org/wsdl/:operation 'xx' was ignored. Error importing XML schema via method 'xx' for 'element' 'xx' in 'xx'(SBL-EAI-08009)
Cycle detected in the 'xx' schema: xx 'xx' has a cycle (SBL-EAI-09008).
(SBL-EAI-04331).
Cause
The error came from the fact that one type definition had a cycle reference to itself. In other words, complex type T1 had one element of type T1 (or another element T2 of complex type having one element of type T1, etc).
BUG (Enhancement Request) BUG 10539615 was created to have this considered for future version.
Solution
The cycle reference was removed in the WSDL file and import worked correctly.
The following note is added to Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Consuming External Web Services Using Siebel Web Services > Creating an Outbound Web Service Based on a WSDL File :-
NOTE: Importing a WSDL containing a cyclic reference, that is, a complex type definition having a member of the same type as itself, is not supported.
References
BUG:10539615 - IMPORT OF WSDL CONTAINING CYCLE REFERENCE IS NOT SUPPORTED.
Related
--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software
Keywords
--------------------------------------------------------------------------------
WSDL; WEB SERVICES; TYPE DEFINITIONS; XML; WEBSERVICE; IMPORT XML; OUTBOUND; SERVICES
Errors
--------------------------------------------------------------------------------
SBL-EAI-04340; SBL-EAI-09008; SBL-EAI-08009; SBL-EAI-04331; SBL-EAI-04333
No comments:
Post a Comment