Business Service Console - The functionality of the Business Service Console has been extended in the following areas:
Approval Process - The approval process has been implemented in the Business Service Console for requestors and approvers. Requestors can create and submit requests, manage their requests, and clone requests to the request work area. Requestors can also send reminders to their approvers. Approvers can approve/reject requests and view approval histories.
Subscriptions and Notifications - The Business Service Console allows you to create and manage subscriptions for monitoring new, changed, and deleted entities. The following entities can be monitored: providers, services, interfaces, and endpoints, as well as resources (WSDL, XML, XSD and XSLT).
User Profiles - BEA AquaLogic Service Registry contains a list of predefined user profiles which differ in which main menu tabs will be available to them. Each user profile also contains a definition of default formats for result views. The registry administrator can adjust these user profiles.
Reports are based on taxonomic classifications.
Paging and large results set support - The Business Service Console supports paging for displaying large result sets. The maximum number of pages and number or rows per page can be configured for each component.
Overall performance of the Business Service Console has been increased by Business Service Console framework optimization.
Approval Process
Changed terminology - the staging registry has been renamed to publication registry; the production registry has been renamed to discovery registry.
New installation/configuration scenarios have been added. The approval process can be installed with multiple publication registries and the approval process can be performed in multiple steps.
Backup functionality - Backup functionality allows you to save the Systinet Registry data and configuration to a filesystem directory. Later the backup data can serve for a full restore of BEA AquaLogic Service Registry data and configuration.
Documentation
The following parts of the UDDI Version 3 specification are not implemented:
Inter-Node operation - this part of the specification is not implemented.
Replication Specification - The Replication Specification describes the data replication process and the programming interface required to achieve complete replication between UDDI Operators in the UBR (Universal Business Registry ~ UDDI operator cloud). This part of the specification is mandatory for members of the UBR and is not implemented.
Policy - The policy description is not defined.
Exclusive XML Canonicalization is used for canonicalization of digital signatures. Schema-centric XML Canonicalization is not yet implemented.
The following parts of the UDDI Version 2 specification are not implemented:
Operator Specification - This part of the specification is mandatory for members of the UBR and is implemented with the exceptions described in this section.
Custody transfer from version 2 is not implemented.
Replication Specification - The Replication Specification describes the data replication process and the programming interface required to achieve complete replication between UDDI Operators in the UBR. This part of the specification is mandatory for members of the UBR and is not implemented.
Sybase ASE (Adaptive Server Enterprise) has a limit of 16 sub-selects for queries (SELECT ... FROM ... WHERE EXISTS (SELECT...)). Because of this limit, some more complex queries (such as find by category bag with more keyed references) do not work.
There are the following caveats in data migration and backup:
Deletion history for subscriptions is not migrated and backed up.
Custody transfer requests are not migrated and backed up.
Migration and backup of approval requests and relationships between requestors and approvers are not yet implemented.
We do not recommend installing BEA AquaLogic Service Registry with the HSQL database under IBM Java 1.4.x since the installation may time out.
Selective One-way Replication has the following caveats:
Checked taxonomies are replicated as unchecked. Taxonomy data replication and change of taxonomy to checked must be done manually.
Custody transfer requests are not replicated.
Publisher assertions are not replicated.
Approval process has the following caveats:
Promotion of projected services is not supported.
Promotion of publisher assertions is not implemented yet.
LDAP
Dynamic groups in LDAP account backends are not processed.
The approximateMatch find qualifier is not supported in LDAP account backends. There is no wildcard that can represent any single character in the directory (LDAP or AD). % is mapped to *, it is not possible to map _.
Groups from disabled domains are visible in the Registry Console.
Intranet identity association is not implemented; the system#intranet group is reserved for future use.
Password structure and length checking, expiration, checking of repeated failed logins and IP mask restriction are not implemented.
The Signer tool does not support the refresh operation. If you start the Signer and then modify a UDDI structure, you must restart the Signer Tool.
The Setup tool throws an exception when you try to configure registry ports on BEA AquaLogic Service Registry that are not connected to a database. The exception does not affect the port configuration.
WSDL Publishing:
When you try to republish a WSDL to another provider, the new binding tModel references the old portType tModel instead of the new one.
Unable to unpublish unreachable WSDLs.
If you change the BEA AquaLogic Service Registry configuration using the Setup tool, demo data is always imported the registry database.