Suppressing Empty Notifications Subscriptions in Oracle Service Registry

1.4.5. Related Links

• To manage subscriptions via the Business Service Control, see the section Business Service Control Subscriptions . • To manage subscriptions via the Registry Control, see the Registry Control Reference . • To use and manage subscriptions, see the Subscription API . • More details about subscriptions can be found in the Subscription API [http:uddi.orgpubsuddi-v3.00-published- 20020719.htm_Toc42047327] chapter of the UDDI v3 Specification.

1.5. Approval Process in Oracle Service Registry

The approval process provides functionality to ensure consistency and quality of data stored in Oracle Service Registry. There are two registries in the approval process: • a publication registry is used for testing and verification of data; • a discovery registry only contains data that has been approved and promoted from the publication registry. See Section 5, Approval Process Registry Installation in the Installation Guide for details of how to install and configure these registries. The approval process includes two types of users: • A requestor is a user of the publication registry who can request approval of data for promotion to the discovery registry; • An approver is a user who can approve or reject requests for promotion of data. Administrators can specify: • the users or groups of users who are approvers; • the users or groups of users whose requests they can approve; Every user can ask for approval, but to have data considered for promotion, a user must have an administrator-assigned approver. For more information see Section 1.7, Approval Process Management in the Administrators Guide . Page 160

1.5. Approval Process in Oracle Service Registry

Figure 1. Approval Request Lifecycle Approval requests have a lifecycle shown in Figure 1 . A requestor can create a request. Once the request is created, the requestor can add UDDI data structures described in Section 1.3.1, UDDI Data Model or resources WSDL, XML, XSD and XSLT to the request. Note that the requestor does not need to know how resources are mapped to UDDI data structures. When the requestor adds a resource to the request, all underlying UDDI structures bindings, tModels the resource represents are automatically added to the request. Once the requestor specifies all entities to promote, the request may be submitted for approval. The approver will review incoming requests, and then can approve or reject the request. If the approver approves the request, the requested data is immediately promoted to the discovery registry. If the requestor is not satisfied with the approvers response time, this user can remind the approver to review the requests. The requestor can also cancel submitted requests. In the following section, we will look at requestors and approvers actions in detail.

1.5.1. Requestors Actions

A requestor may perform the following actions: • Submit a request for approval of data promotion After submitting the request, all data referenced in the request is blocked locked for writing until the request is either canceled by the requestor, approved for promotion, or rejected by the approver. Note A requestor may request approval for the promotion of the same set of data several times, and may have several unprocessed requests at one time. • Find request. Page 161

1.5.1. Requestors Actions