Release Notes  Locate

What's New  Locate

  • 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 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 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 and/or managed servers.

  • Notable defects that have been corrected since previous release:

    • Probably generating duplicated table's primary keys.

    • Can publish a file from server's file system using URL file://

    • Cross-site scripting problem.

    • Arbitrary readObject code invocation possible with the embedded gzip/base64 serial object in param "carrybag".

    • Subscription: Restoring data is failed when Registry contains existing subscription.

    • 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.

Known Issues  Locate

UDDI Version 3 Specification  Locate

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.

UDDI Version 2 Specification  Locate

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.

Database  Locate

  • 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.

    • The JDBC Connection URL must be corrected before running Oracle Service Registry via the Administrator Console of WebLogic. The correct format of Connection JDBC URL is jdbc:db2://<Host Name>:<Port>/<Database Name>

Other  Locate

  • Use of SubjectAlternativeName in certificates is not yet supported. This has potential impact wherever SSL is used and the secure host has more than one hostname. See WSDL Publishing below. The result is a java.net.ssl.SSLException with a message that hostnames do not match.

  • Installation fails if the installation path contains non-ASCII characters;

  • Attempting to undeploy Oracle Service Registry from an application server may appear to have been successful but can leave files locked until the application server and its JVM exit. This means that an attempt to redeploy Oracle Service Registry to the application server will fail because these files exist and cannot be overwritten. A workaround is to restart the application server;

  • 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 Control.

  • 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 Oracle Service Registry that are not connected to a database. The exception does not affect the port configuration.

  • WSDL Publishing:

    • Unable to unpublish unreachable WSDLs in Registry Console.

    • Publishing a WSDL at a URL that has https as its protocol may fail because the server certificate uses SubjectAlternativeName to specify alternative hostnames. This is not yet supported as noted above. The result may be a WSDLException with the fault code INVALID_WSDL but the underlying cause is in fact a java.net.ssl.SSLException with a message that hostnames do not match.

Change Log  Locate

Oracle® Fusion Middleware Service Registry 11g (11.1.1)  Locate

  • The Database Persistent Configuration feature enables the simple configuration of cluster deployment. The database can also hold a history of configuration files. The administration console enables you to display the differences between current and past configurations and stored configuration collections.

  • Replications are improved and more reliable.

  • Asymmnetric Cluster Installation for WLS 10.3.1 with Templates - Installer produces files including a .war file and WebLogic Domain template and places them into the Oracle WebLogic Registry Home. Upon completion, you can run the Oracle WebLogic Configuration Wizard to deploy to the selected clusters and/or managed servers.

  • Database deadlock recovery and prevention.

    • User connects to Registry from multiple threads or computers using any operation (find, get, save, delete). Registry completes all operations even when there is deadlock in the database.

  • Bug fixes. Small improvements.

Oracle® Fusion Middleware Service Registry 10g Release 3 (10.3)  Locate

  • 2-way SSL support Client authentication.

  • Support Oracle RAC.

  • Remove HSQL and OLite databases.

  • Bug fixes. Small improvements.