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

3. Demo Data

Demo data is pre-installed with Oracle Service Registry. There are two demo data sets: • demo data to demonstrate Business Service Control • demo data to demonstrate Registry Control and Demo Suite

3.1. Demo Data for Business Service Control

Demo data is pre-installed with Oracle Service Registry for use with the Business Service Control. This data describes a financial institution bank with several departments. It contains entities providing services for its operations. Entities providing services are modelled as service providers. There are the following providers and their services in the demo data: Account Services Account Services provides services related to account information, transfers, check orders, bill pay, online statements. • Account - The account service provides the account related operations :getAccount, listAccountDetail, listRelatedAccounts , listTransactionHistory. • Bill Payment - The bill payment service provides the ability to establish bill payment service, cancel bill payment service and get information about bill payment for a customer. Operations: authorizeAcctForBillPymt , cancelBillPymtSvc, createBillPymtSvc. • Check Order - This service supports new check orders, check reorders, check order inquiry. Operations: getLastCheckOrder , orderChecks, reorderChecks. • Direct Deposit Advance -This service supports the operations used to set up the advancement of money. Operation: addDirectDepositAdvance. • Notification Services - This service is used to provide notifications. Operation: sendAccountTransferNotification . • Stop Payment - This service allows stops to be set and maintained. Operations: addStopPaymentForCheck, cancelStopPay • Transfer Funds - This service allows funds to be transferred from one account to another. Operations: authorizeTransfer , sendInvoicePayment, transferFunds. Customer Management System Customer relationship and management system. • Add Customer - This service allows a customer to be added to the enterprise customer system. Operation: addCustomer . • Customer Notification - This service provides notification messages for various customer changes. Operations: customerNameChangeNotif , customerAddressChangeNotif. Outlet Locator Provides information about outlets and sites. • Outlet - The Outlet service gets all of the information about a Company outlet. Operation: getOutletDetail. • Site - This service gets information about a site. Operations: getSiteDetail, listSites, searchSites Page 166

3.1. Demo Data for Business Service Control