Applies to: Siebel CRM - Version: 7.7.1 [18306] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
***Checked for relevance on 11-NOV-2010***
SymptomsHi Support,
Our external system "Axway" cannot import external web services definitions (wsdl), so, I am trying to use a generic WSDL definition for both inbound and outbound web services.
In order to accommodate such a situation with Siebel, I have defined an Business Service (MessageServiceInbound) which is published as a web service in the web client using the name space http://<webserver>/tradingengine/transport/api/webservice and mimic the sendMessage operation.
If I try to generate the WSDL from Siebel I get always the following errors:
a). WSDL cannot be generated for webservice 'InboundMessageService' of namespace 'http://<webserver>/tradingengine/transport/api/webservice'. No valid port has been defined. Make sure that the 'Transport' and 'Binding' values are supported combinations.(SBL-EAI-04328)
b). WSDL cannot be generated for port type 'MessageServiceInboundPort'.(SBL-EAI-04326)
c). The XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition. (SBL-EAI-04449)
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
CauseThe three errors the customer received when trying to generate the WSDL, are chained errors, and must be addressed from bottom - up, which means the actual error is shown in c)
The XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition.
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
And as the error details, XMLTagNamespace and XSDTypeNamespace cannot be different.
Solution
The issue reported is because the XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition.
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
In Siebel Tools you need to go to your Integration Objecs -> Integration Objects User Properties and change the XSDTypeNamespace to be the same as XMLTagNamespace, recompile the Integration Objects, run your client and go to Administration – Web Services > Inbound Web Services, find your Web Service, “clear the cache†and click "Generate WSDL".
Information in this document applies to any platform.
***Checked for relevance on 11-NOV-2010***
SymptomsHi Support,
Our external system "Axway" cannot import external web services definitions (wsdl), so, I am trying to use a generic WSDL definition for both inbound and outbound web services.
In order to accommodate such a situation with Siebel, I have defined an Business Service (MessageServiceInbound) which is published as a web service in the web client using the name space http://<webserver>/tradingengine/transport/api/webservice and mimic the sendMessage operation.
If I try to generate the WSDL from Siebel I get always the following errors:
a). WSDL cannot be generated for webservice 'InboundMessageService' of namespace 'http://<webserver>/tradingengine/transport/api/webservice'. No valid port has been defined. Make sure that the 'Transport' and 'Binding' values are supported combinations.(SBL-EAI-04328)
b). WSDL cannot be generated for port type 'MessageServiceInboundPort'.(SBL-EAI-04326)
c). The XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition. (SBL-EAI-04449)
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
CauseThe three errors the customer received when trying to generate the WSDL, are chained errors, and must be addressed from bottom - up, which means the actual error is shown in c)
The XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition.
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
And as the error details, XMLTagNamespace and XSDTypeNamespace cannot be different.
Solution
The issue reported is because the XML Schema generator does not support different XML Namespaces for XML Tags and XSD Type in the integration Object Definition.
XMLTagNamespace=’http://<webserver>/tradingengine/transport/api/webservice’,
XSDTypeNamespace=’http://<webserver>/tradingengine/transport/api/webservice/types’
In Siebel Tools you need to go to your Integration Objecs -> Integration Objects User Properties and change the XSDTypeNamespace to be the same as XMLTagNamespace, recompile the Integration Objects, run your client and go to Administration – Web Services > Inbound Web Services, find your Web Service, “clear the cache†and click "Generate WSDL".
Related
Products
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM
Keywords
| |
NAMESPACE; WSDL; XML SCHEMA; WEBSERVICE; INBOUND; SERVICES; WEB SERVICES
| |
Errors
| |
SBL-EAI-04449; SBL-EAI-04328; SBL-EAI-04326
| |
No comments:
Post a Comment