CentraSite Documentation : CentraSite Developer’s Guide : Access via UDDI : CentraSite UDDI Architecture : Modeling of the Node Business Entity : Node Business Entity
Node Business Entity
The node business entity that is preloaded into the Registry/Repository looks like this:
<businessEntity
businessKey="...">
<name xml:lang="en-US">NodeBusinessEntity</uddi:name>
<description xml:lang="en-US">
Node Business Entity of the CentraSite UDDI registry
</description>
<categoryBag>
<uddi:keyedReference
keyName=""
keyValue="node"
tModelkey="...:keyGenerator"/>
</categoryBag>
</businessEntity>
The node business entity references certain businessService objects which reflect the UDDI API sets. The first UDDI registry interacting with the Registry/Repository adds the businessService objects. It also adds the bindingTemplate objects pointing to the API set's endpoints offered by the UDDI registry. Every additional UDDI registry in a multiple UDDI servlet environment adds bindingTemplate objects pointing to the additional endpoints where the UDDI services can be called. The tModels referenced by the businessService objects are preloaded into the UDDI registry. Due to the fact that multiple bindingTemplate objects are defined for each UDDI registry, the bindingTemplate objects get node generated keys.
The web services that implement the UDDI API sets are themselves registered in the UDDI registry. For CentraSite, only the supported API sets are reflected by this self-registration. These are:
*Inquiry API set
*Publication API set
*Security Policy API set
*Custody and Ownership Transfer API Set
Copyright © Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback