Oracle Service Registry Features Overview

• Selective Replication among multiple registries allow for automated propagation between different registries for e.g. between internal and external registries. • Advanced Taxonomy Management for enforcement of well-defined taxonomies. • Powerful Management for granular control, logging and auditing of the publishing and discovery processes. • Performance Scalability UDDI provides maximum performance and scalability by efficient implementation of web services stack and database algorithms and by supporting of a load balancing and clustering mechanism. Oracle Service Registry is a platform-independent solution that can easy be deployed in a wide variety of settings. Crucially, Oracle Service Registry also integrates with LDAP directories, including Oracle Internet Directory and Microsoft ActiveDirectory.

2. Release Notes

2.1. Whats New

• The database installation screen offers a new option for Oracle Database to create a new tablespace with a specified location for the data file. The name of data file was previously derived from the name of the tablespace. Now, you can specify any name including a logical name of a disk group. The disk groups are defined in Oracle Automatic Storage Management. This option is useful for Oracle RAC installation where using disk groups is mandatory. • The new Database Persistent Configuration feature changes the way configuration information is stored and updated. Previously, configuration data was stored in files only. When the product was redeployed on an application server modifications to configuration files were lost. Now configuration data persists both in files and in the database. Beginning with this release the database becomes the primary store for configuration information. This change has several advantages. Cluster configurations are now easier to configure and no longer need to rely on SOAP messaging between nodes. Configuration Management is now available in the Administration Console. This enables administrators to view current and past configurations; to compare the differences between them; and to reactivate past configurations whenever necessary. Read more in Section 3, Configuration in Database . • Replications are improved and more reliable. Previously the scheduled time was specified by interval period. However, the exact time when the replication would start was uncertain as this was calculated from the Registry server start time. Now the time is specified in a more flexible way. Replications have been made transactional. Either all replicated entities are transferred successfully or none at all. Replications can optionally preserve the name of the owner of the replicated entity. A replication entry can use several subscriptions at once. The result of a replication invoked by an administrator is presented as a color coded report in the console. This report is available in an HTML file inside the log directory for scheduled replications. Detailed documentation is in Section 1.6, Replication Management • Installation on Oracle WebLogic offers a new installation method: Domain Template installation. Using this approach, the Installer produces all the files including a .war file and a WebLogic Domain Template. It then places them into the Oracle WebLogic Registry Home. Upon completion you can run the Oracle WebLogic Configuration Wizard to deploy to selected clusters andor managed servers. • Notable defects that have been corrected since previous release: • Probably generating duplicated tables primary keys. • Can publish a file from servers file system using URL file: • Cross-site scripting problem. • Arbitrary readObject code invocation possible with the embedded gzipbase64 serial object in param carrybag. • Subscription: Restoring data is failed when Registry contains existing subscription. Page 2

2.1. Whats New

• Migrating fails when administrator accounts are different. • Replication cannot run successfully if target registry configured with MS SQL database. • Migrating fails when the registry configured with DB2 database and the previous registry contains subscription.

2.2. Known Issues

2.2.1. UDDI Version 3 Specification

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 [http:www.w3.org200110xml-exc-c14n] is used for canonicalization of digital signatures. Schema-centric XML Canonicalization is not yet implemented.

2.2.2. UDDI Version 2 Specification

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.

2.2.3. Database

• 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. • There are the following issues with creating JDBC Data Source on DB2 database in case of domain configuration. • At the Configuration Wizard • Information user entered during installation is not filled correctly at the Configure JDBC Data Sources page of the wizard. User must re-enter these values again. • However, the JDBC Connection URL will be generated with wrong format jdbc:db2:Database Name in the Test JDBC Data Sources window. This causes failed on test connection at the Test JDBC Data Sources page. Page 3

2.2.3. Database