Synchronization of Data Approval Process in Oracle Service Registry

• If an entity exists only on the discovery registry then it is copied to the publication registry. • If an entity exists only on the publication registry then it is preserved. • If an entity exists on both registries, then the publication registry takes priority over the discovery registry. Publication Priority Example Before synchronization, structures A and X exist on the publication registry and structures X and B exist on the discovery registry. The Publication Priority synchronization copies structure B to the publication registry. Structure X on publication registry remains the same because when the same entity exists on both servers, Publication Priority synchronization favors the publication registry. Partial Discovery Priority Partial discovery priority has the following rules: • If an entity exists only on the discovery registry, then it is copied from the discovery registry to the publication registry. • If an entity exists only on the publication registry then it is preserved. • If an entity exists on both registries, then data on the publication registry is overwritten by data from the discovery registry. Partial Discovery Example Before this synchronization, structures A and X exist on the publication registry and structures X and B exist on the discovery registry. Partial discovery synchronization copies structure B to the publication registry and overwrites the version of structure X on the publication registry with that from the discovery registry. Full Discovery Priority Under this synchronization scenario, all the users data on the publication registry is deleted, and all the users data from discovery registry is copied to the publication registry. After full discovery priority synchronization, data on the discovery and publication registries is identical. Important The Oracle Service Registry administrator cannot execute full discovery priority synchronization. Full Discovery Example Before synchronizing, structures A, X, Y and B exist on the publication registry and structures A, X and B exist on the discovery registry. Full discovery synchronization deletes structures A, X, Y and B from the publication registry, and replaces them with A, X, and B from the discovery registry.

1.5.4. Mail notification in approval process

Mails are sent in approval process for notification of involved parties. Approvers are notified via mail that requestors ask for their approval, cancel approval requests and so on. Requestors are notified via mail that approvers approve requests, reject requests and so on. Mails form is determined by XSL transformation and so it can be changed. Page 164

1.5.4. Mail notification in approval process

By default the following transformation are used. They are specified by the key of appropriate tModel. uddi:systinet.com:approval:defaultRequestEmailXSLT is used for notifications of aprovers about requestors submission of approval requests. uddi:systinet.com:approval:defaultMessageEmailXSLT is used for notifications of approvers and requestors about approval requests cancellation, approval or rejection. User can change mails form in case that he defines his transformations for himself. In such a case these transformations are taken into the account instead of default ones. User can set special properties into its account. Property whose name is approval.email.approver.request.tranformation determines custom transformation for mail notification about newly created approval requests. If approver set value of this property to the key of XSL transformation, then this transformation is used for mail notification he receives. In a similar way, property whose name is approval.email.approver.message.tranformation specifies custom transformation for notification mails about requests cancellation, approval or rejection. If user wants to receive other mails than default ones he sets this property to the key of new transformation. Note If you are using approval process from the Registry Control, the form of mail notifications is determined by approval.email.approval.message.tranformation.60 property. By default transformation defined by uddi:systinet.com:approval:defaultMessageEmailXSLT_60 tModel is used.

1.5.5. Related Links

• Installation of publication and discovery registries - Installation Guide, Section 5, Approval Process Registry Installation • Approval process via Business Service Control - Users Guide, Section 4.8, Approval Process • Configure requestors and approvers - Administrators Guide, Section 1.7, Approval Process Management

2. Registry Consoles

Oracle Service Registry provides two user interfaces. • Business Service Control Using the Business Service Control developers, architects and business users can browse the various perspectives of the registry including business-relevant classifications such as service and interface lifecycle, compliance or operationalreadiness status. They can browse information through business-relevant abstractions of SOA information such as schemas, interface local names or namespaces. The Business Service Control also provides easy to use and customizable publication wizards. The Business Service Control can be found at http:hostname:portcontextuddibscweb. Host name and port are defined when Oracle Service Registry is installed. The default port is 7101 or 8888 depending on application server setting. The context is specified during installation and defaults to registry. See Section 4, Business Service Control • Registry Control Using the Registry Control users can browse and publish registry contents, create subscriptions and perform ownership changes. The Registry Control is the primary console for administrators to perform registry management. The Registry Control can be found at http:hostname:portcontextuddiweb. Host name and port are defined when Oracle Service Registry is installed. The default port is 7101 or 8888 depending on application server settings. See Section 5.5.2, Registry Console Overview Note Make sure your browser allows HTTPS connections, supports JavaScript and does not block popup windows. Page 165

2. Registry Consoles