Publish WSDL with endpoints
[axis wsdl] [BC-ESI-UDDI] [endpoints] [myeclipse wsdl] [portType] [portTypeBindingService] [SR] [UDDI] [wsdl]
Related:
- Create and assign physical system in SR 710Symptom Publish by WSDL feature in the Services Registry client...
Symptom
Published WSDL from Integration Directory does not contain neither binding information nor endpoint soap address locations.
Use-case:
You publish a Sender Agreement or Integrated Configuration into Service Registry from Integration Directory. The publication results in a configured Service Definition with endpoints. Hovewer the published WSDL contains only portType information – binding and endpoint descriptions are missing.
Other terms
portTypeBindingService portType SR UDDI BC-ESI-UDDI
Reason and Prerequisites
The publication logic publishes only portType wsdl because other parts of the WSDL – binding and endpoint are published separately.
During publication two different WSDLs are published – one for Service Definition and a second one for each endpoint’s binding. As already described as a symptom the first wsdl contains only wsdl:portType element.
The second WSDL contains wsdl:binding and refers to the first WSDL by using wsdl:import statement. But wsdl:service and wsdl:endpoint elements are not available in second WSDL as well because endpoint information is published directly to UDDI entities and can be found there.
Solution
Starting from 7.10 SP8 it is possible to publish complete WSDL into registry. You need to configure following boolean property in Exchange Profile:
IntegrationBuilder ->
IntegrationBuilder.Directory->
com.sap.aii.ibdir.wsdl.registry.publishWsdlWithEndpoints
When property is “true” the complete wsdl is published. The default value is “no” – portType only wsdl.
After setting this property you need to republish all previously published Sender Agreements.