Service Registry Release Notes for Microsoft Windows

These Release Notes contain important information available at the time of release of Service Registry 3 2005Q4 for Microsoft Windows. Known issues and limitations, and other information are addressed here. Read this document before you begin using Service Registry 3.

Release Notes Revision History

Table 1 Revision History
Date	Description of Changes
February 2006	Revenue release.
November 2005	Initial release

About Service Registry 2005Q4

This section provides information related to the features, functionality, and supported products in Service Registry 3 2005Q4. This section covers the following:

Implementation-Specific API

Service Registry includes an implementation of version 1.0 of the Java API for XML Registries (JAXR) specification. JAXR 1.0 was written to support the UDDI and ebXML Registry 2.0 specifications. The implementation of JAXR in Service Registry includes nonstandard extensions to JAXR 1.0. These API extensions will be contributed to a future version of the JAXR specification for consideration as additions to the future JAXR standard.

These API extensions are subject to change in future releases of Service Registry. Sun will make every effort to maintain backward compatibility for these APIs in future releases of Service Registry. In some cases backward compatibility may not be possible. Customers who decide to use these API extensions are advised to be aware of the potential for changes to these extensions within the Service Registry JAXR provider at future releases.

Features Nearing the End of Life

User Registration Mechanism

This release of Service Registry relies on its own user management and authentication mechanism. The plan is to update the Registry at a future release to a SAML-based mechanism (as specified in the ebXML Registry standard, of which this component is an implementation) and to use the Access Manager for user management and authentication at that release and thereafter.

At this release, Service Registry customers have their registered user information maintained by Service Registry. At a future release and thereafter, customers will have this information maintained by Access Manager. Customers who upgrade to one of these future versions of Service Registry will need to migrate their user information to Access Manager in order to maintain the connections (for example, audit trails) established between registered users and Registry contents. Sun intends to provide a migration tool to facilitate this transition.

Hardware and Software Requirements

Table 2 Hardware and Software Requirements
Components	Platform Requirement
Operating System	Microsoft Windows 2000 Advanced Server, Service Pack4 Microsoft Windows 2003 Enterprise Server Microsoft Windows XP Professional, Service Pack 2
RAM	512 MB
Disk Space	200 MB

Bugs Fixed in This Release

The following table describes the bugs that have been fixed in Service Registry 3 2005Q4.

Table 3 Fixed Bugs in Service Registry 3 2005Q4
Bug Number	Description
6348529	Installation on Windows gets stuck on Service Registry Post installation Configuration
6327977	Service Registry uninstallation prompts for restart.

Important Information

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html.

Known Issues and Limitations

This section describes the known issues and limitations of Service Registry 3 2005Q4 release for Microsoft Windows.

EmailAddress Objects Cannot Be Retrieved for Organization Objects (6290339)

The JAXR provider cannot retrieve email addresses from an Organization object. If you publish an Organization object with an email address, the publish appears to succeed, but the OrganizationImpl.getEmailAddresses method returns no results. This problem also results in an empty display in the Web Console.

Attempt to Create Reference Between Organization Objects Causes Error (6298946)

In the Web Console, if you select the Pick checkboxes for two Organization objects and click Relate, then click Save to save the default relationship (an object reference), the Web Console reports an error, but without a detailed error message. A stack trace appears in the server log.

Duplicate User Name Causes Unclear Error Message (6303812)

In the Web Console, when a user attempts to create a user account with a generated certificate and specifies an alias that is already known to the server, the following error appears in the Web Console on the Step 3 page:

Caused by: java.lang.Exception: Key pair not generated, alias name already exists.

Registration Wizard Ignores Required Values When Creating Certificate Distinguished Name (6312094)

In the Web Console, the User Registration Wizard uses some of the optional values you specify on the New User’s Details page (City, State or Province, and Country) when it creates the Distinguished Name (DN) for the certificate it generates. However, the Wizard ignores all but one of the required values you specify on the User Authentication Details page. (The only value it uses is the Name value.)

To include a city, state or province, or country in the certificate DN, specify those values on the New User’s Details page in addition to the User Authentication Details page.

Service Registry Configuration Fails After Reinstallation (6313327)

If you use the Java Enterprise System uninstaller to uninstall Service Registry, then reinstall and perform post-install configuration, the configuration script fails with an error:

The problem is that the uninstaller does not stop or remove the Application Server domain for the Registry. This task must be performed manually.

Before you reinstall Service Registry, stop the Application Server domain for the Registry, then delete the domain. See “Reinstalling Service Registry” in Service Registry 3 2005Q4 Administration Guide for details.

Administration Tool Fails When -alias Option Is Used (6313791)

If you try to use the Admin Tool to perform tasks that require administrator permission, a stack trace and NoClassDefFoundError occur. The reason for the error is that a file is missing from the manifest classpath of the Admin Tool JAR file.

Errors Occur After Creation of ExtrinsicObject or ExternalLink with Invalid Concept (6318002)

In the Web Console, if you create an ExtrinsicObject and select a concept that is under a concept other than ExtrinsicObject, the creation appears to succeed, but in fact errors have occurred. The same problem occurs if you create an ExternalLink and select a concept that is under a concept other than ExternalLink.

If the concept is another subconcept under RegistryObject, the main effect is that the new object cannot be found when you search for it. If the concept is under a ClassificationScheme other than ObjectType, the database is corrupted. Runtime errors occur (InvocationTargetException) when you restart the server.

The object type concept must be a subconcept within the ExtrinsicObject or ExternalLinkconcept, but the Web Console does not enforce this requirement.

Use the Admin Tool to find the object or objects that use the wrong concept. Use the select command to find the objects and the rm to delete them. The steps for this task follow.

Restart Service Registry as described in “To Stop and Restart the Application Server Domain for the Registry” in Service Registry 3 2005Q4 Administration Guide.

Start the Admin Tool, either as a registry administrator or as the owner of the corrupted objects, as described in “Starting the Admin Tool” in Service Registry 3 2005Q4 Administration Guide.

Go to the top-level location in the database: admin> cd /

Use the select command to list the objects to be removed.

If you started the tool as a registry administrator, use the following command (all on one line):

admin> select ro.* FROM RegistryObject ro, ClassificationNode cn WHERE ro.objectType = cn.id AND NOT ( cn.path = ’/urn:oasis:names:tc:ebxml-regrep:classificationScheme:ObjectType/RegistryObject’

or cn.path like

’/urn:oasis:names:tc:ebxml-regrep:classificationScheme:ObjectType/RegistryObject/%’ )

If you started the tool as the owner of the objects, use the following command (all on one line):

admin> select ro.* FROM RegistryObject ro, ClassificationNode cn, AffectedObject ao, AuditableEvent ae WHERE ro.objectType = cn.id AND ae.user_ = $currentUser AND ao.id = ro.id AND ao.eventId = ae.id AND NOT

( cn.path = ’/urn:oasis:names:tc:ebxml-regrep:classificationScheme:ObjectType/RegistryObject’

or cn.path like

’/urn:oasis:names:tc:ebxml-regrep:classificationScheme:ObjectType/RegistryObject/%’ )

admin> rm urn1 urn2 ...

Deleting AuditableEvent for Object Creation Causes Exceptions (6323057)

If you delete an AuditableEvent whose Affected Objects list contains one or more objects that you own, the audit trail for the affected objects is corrupted. In particular, severe problems occur if you delete the Created event for your own User object. For example, after you delete this event, runtime exceptions occur whenever you perform the FindAllMyObjects search.

Attempt to View Repository Item Before Clicking Apply Button Causes Error (6324423)

In the Web Console, if you create an ExtrinsicObject and add a repository item, the View Repository Item Content link becomes active as soon as you upload the file, before you click either the Save or the Apply button. If you click the link before you click Apply, an error 404 message appears. The link should not become active before it is a valid link.

ClassificationScheme Display Persists Between Publish Operations (6297023)

In the Web Console, if you publish an object such as an ExtrinsicObject or ExternalLink that involves choosing a concept from a ClassificationScheme, the next time you publish another object the ClassificationScheme window is open at the same location, even if the second object is of a different object type.

Similarly, if you perform a search by classification, perform some other operation (such as a publish operation) that closes the Search form, then open the Search form again, the ClassificationScheme display is the same as when the Search form was closed.

Some Searches Return Unexpected Results (6312083)

In the Web Console, searches by name for Person or User objects fail to return any of the predefined users in the database, or any Person or User that has a PersonName defined instead of a Name. In addition, searches for objects whose names contain a particular number of characters (for example, using a search string of "__" to find two-character names) return many objects whose names contain other than the specified number of characters.

Problem while creating user account using upload certificate option (6338836)

In the Web Console, the user registration fails with upload third party certificate option because of Authentication failure. Registration fails with an error: “Operation failed due to authentication failure. Authentication failed because you do not have a client certificate loaded in your web browser.”

Use the registry generated certificate for creating user accounts. Follow the instructions in Service Registry 3 2005Q4 User Guide.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Service Registry, contact Sun customer support using one of the following mechanisms:

To assist you best in resolving problems, please have the following information available when you contact support:

Description of the problem, including the situation where the problem occurs and its impact on your operation

Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

Detailed steps on the methods you have used to reproduce the problem

Any error logs or core dumps

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions.

To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the guide or at the top of the document.

Additional Sun Resources

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.