APIs
Proprietary APIs, Version 1.1
Area |
Interfaces |
Services Registry APIs - Java |
WSDL: http://localhost:50000/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl Endpoint: http://localhost:50000/ServicesRegistrySiService/ServicesRegistrySiPort deleteClassificationSystemValues deleteClassificationSystems deleteServices findClassificationSystemsPerPhysicalSystems findClassificationValuesPerPhysicalSystems findGroupClassificationValuesPerPhysicalSystems findPhysicalSystems findPhysicalSystemsPerGroupClassifcationValues findService findServiceDefinitions findServiceDefinitionsByKeywords findServiceEndpoints getClassificationSystemValues getClassificationSystemValuesFlat getClassificationSystems getClassificationSystemsGreaterThanVersion getGroupClassificationSystemValues getGroupClassificationSystemValuesFlat getGroupClassificationSystems getPhysicalSystems getServiceDefinitions getVersionInfo hidePhysicalSystems hideServiceDefinitions isKeywordSearchSupported notifyPhysicalSystem publishClassificationSystemValues publishClassificationSystemValuesFlat publishClassificationSystems publishGroupClassificationSystemValues publishGroupClassificationSystemValuesFlat publishPhysicalSystems publishServiceDefinitions publishServices publishWSDL |
Services Registry APIs - ABAP Version 1.1 |
WSDL: http://localhost:50000/ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort?wsdl&mode=sap_wsdl Endpoint: http://localhost:50000/ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort
deleteClassificationSystemValues deleteClassificationSystems deleteServices findClassificationSystemsPerPhysicalSystems findGroupClassificationValuesPerPhysicalSystems findPhysicalSystems findPhysicalSystemsPerGroupClassifcationValues findService findServiceDefinitions findServiceDefinitionsByKeywords findServiceEndpoints getClassificationSystemValuesFlat getClassificationSystems getClassificationSystemsGreaterThanVersion getGroupClassificationSystemValuesFlat getGroupClassificationSystems getPhysicalSystems getServiceDefinitions getVersionInfo hidePhysicalSystems hideServiceDefinitions isKeywordSearchSupported notifyPhysicalSystem publishClassificationSystemValuesFlat publishClassificationSystems publishGroupClassificationSystemValuesFlat publishPhysicalSystems publishServiceDefinitions publishServices publishWSDL |
Proprietary APIs, Version 1.0 for ABAP, obsolete
Area |
Interfaces |
Services Registry APIs - ABAP Version 1.0 |
WSDL: http://localhost:50000/ESRegistryWS/BasicAuthConfig?wsdl Endpoint: http://localhost:50000/ESRegistryWS/BasicAuthConfig?style=document deleteClassificationSystemValues deleteClassificationSystems findServiceDefinitionsByName findWSEndpoints getAllERClassificationSystems getClassificationSystem getClassificationSystemGroup getClassificationSystemValuesFlatHierarchy getGroupClassificationSystemValuesFlatHierarchy getPhysicalSystem getPhysicalSystems getServiceDefinitions getVersionInfo hideService hideServiceDefinition hideServiceDefinitions hideServices isKeywordSearchSupported notifyPhysicalSystem publishPhysicalSystem publishService publishServiceDefinitions saveClassificationSystem saveClassificationSystemValuesFlatHierarchy saveGroupClassificationSystem saveGroupClassificationSystemValuesFlatHierarchy |
These interfaces should be used by external tools, although it is still possible to call the lower-level APIs or UDDI operations directly.
Standard APIs
The UDDI specification defines API sets, which are designed to be implemented by registries or registry clients. They are separated in Node API Sets and Client API Sets.
UDDI Node API Sets: |
Description: |
UDDI Inquiry |
The operations available in the UDDI Inquiry API Set provide the current discovery functions. There are also interfaces available if you wish to perform a search in the registry or retrieve detailed information about entities. You must implement this API set if you have an UDDI-conform registry. |
UDDI Publication |
Together with the Inquiry API, this is the only required UDDI API set. Its interfaces provide the functions for publishing, updating, and deleting the entities in the registry. |
UDDI Security |
Authentication is sometimes necessary for certain operations in the registry. For this reason, the registry client can send an authentication token together with its operation call. The operations within the UDDI Security API Set provide the functions for getting or discarding such a token. |
UDDI Custody Transfer |
The operations within the Custody Transfer API Set provide the functions for transferring ownership and custody of entities within the registry from one registry user to another (and also between different registries). |
UDDI Subscription
|
The operations provided by the subscription API enable a registry user to subscribe to certain entities. To describe which entities the user would like to subscribe to, he or she can use any functions of the Inquiry API. A subscription, for example, can use any query that is compliant with the UDDI Inquiry API. Subsequently, all entities that match this query are relevant for this subscription. Whenever the result of the query changes, the entities affected by the subscription will change as well. There are two options available to the subscriber for monitoring the matching entities: Asynchronous Notification and Synchronous Change Tracking. Asynchronous Notification A subscribed user is notified whenever an entity that matches the specified query changes. As a result, the subscriber can provide an implementation of the UDDI Subscription Listener API. This is then called. Synchronous Change Tracking The registry can provide an operation which can then be called by the subscriber at any time. It provides information about how the monitored entities have changed. |
UDDI Replication |
The Replication API Set provides interfaces that are to be used for data replication between different registries. |
UDDI Client API Sets: |
Description: |
UDDI Subscription Listener |
As described above, the Subscription Listener API can be provided by a subscriber for certain entities. This operation is then called by the registry every time the state of an affected entity changes. |
UDDI Value Set |
In UDDI, you can use value sets for storing categorizations. If a certain category is used while an entity is being saved or changed in the registry, the registry may be able to call an external operation in order to prove that the provided values are valid. |
More information: UDDI V3 Specification .