Replication Basic Concepts of the UDDI Specification

1.3.7. Technical Notes

Technical Notes TN are non-normative documents accompanying the UDDI Specification that provide guidance on how to use UDDI registries. Technical Notes can be found at http:www.oasis-open.orgcommitteesuddi-specdoctns.htm . One of the most important TNs is Using WSDL in a UDDI Registry.

1.3.8. Benefits of UDDI Version 3

The most important features include: • User-friendly identifiers facilitate reuse of service descriptions among registries. • Support for digital signatures allows UDDI to deliver a higher degree of data integrity and authenticity. • Extended discovery features can combine previous, multi-step queries into a single-step, complex query. UDDI now also provides the ability to nest sub-queries within a single query, letting clients narrow their searches much more efficiently.

1.4. Subscriptions in Oracle Service Registry

Subscriptions are used to alert interested users in changes made to structures in Oracle Service Registry. The Oracle Service Registry Subscription API provides users the ability to manage save and delete subscriptions and evaluate notification. Notifications are lists of changes made within a specified time interval. The Subscription mechanism allows the user to monitor new, changed, and deleted entries for businessEntities, businessServices, bindingTemplates, tModels or publisherAssertions. The set of entities in which a user is interested is expressed by a SubscriptionFilter, which can be any one of the following UDDI v3 API queries: • find_business , find_relatedBusinesses, find_services, find_bindings, find_tmodel • get_businessDetail , get_serviceDetail, get_bindingDetail, get_tModelDetail, get_assertionStatusReport Note In Business Service Control, users can also create subscriptions also resources WSDL, XML, XSD and XSLT without a detailed knowledge of how resources are mapped to UDDI data structures.

1.4.1. Subscription Arguments

A subscription is the subscribers interest in changes made to entities as defined by the following arguments: • SubscriptionKey - The identifier of the subscription, as generated by the server when the subscription is registered. • Subscription Filter - Specifies the set of entities in which the user is interested. This field is required. Note that once the subscription filter is set, it cannot be changed. • Expires After - The time after which the subscription is invalid optional. • Notification Interval - How often the client will be notified optional. The server can extend it to the minimum supported notification interval supported by the server as configured by the administrator. For more information, please see Administrators Guide, Section 2, Registry Configuration . • Max Entities - how many entities can be listed in a notification optional. When the number of entities in a notification exceeds max entities, the notification will contain only the number of entities specified here or in the registry configuration. A chunkToken different from 0 will be specified in the notification. This chunkToken can be used to retrieve trailing entities. Page 158

1.4.1. Subscription Arguments