test

Service Registry 3.1 Release Notes for Microsoft Windows

Chapter 1 Service Registry 3.1 Release Notes

These release notes contain important information available at the time of release of Service Registry 3.1. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Service Registry.

The most up-to-date version of these release notes can be found at the Sun documentation web site at http://docs.sun.com. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.

These release notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.

Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

What's New in Service Registry 3.1

This section provides information related to new features, functionality, and supported products in Service Registry 3.1.

New Access Port for Service Registry

The Service Registry default access port value has changed because the previous port value, 6060, conflicted with a value that was registered with the Internet Assigned Numbers Authority (IANA) for the use of the X Window System (X11). The new default access port value is 6480. All default Service Registry ports are now registered with IANA.

Any existing clients that use the Java API for XML Registries (JAXRTM) should be changed to use the new port value. The properties javax.xml.registry.queryManagerURL and javax.xml.registry.lifeCycleManagerManagerURL specify this port value for JAXR clients. If these properties are defined in a properties file, you do not have to recompile the clients.

Installation Path Names for Service Registry

The installation path names for Service Registry have changed, as shown in the following table.

Table 1–1 Installation Paths for Service Registry

Description 

Java ES4 Path Name 

Java ES5 Path Name 

Base Installation Directory 

C:\Sun\ServiceRegistry

C:\Program Files\Sun\JavaES5\srvc-registry

Domain and Data Installation Directory 

C:\Sun\ServiceRegistry

C:\Program Files\Sun\JavaES5\srvc-registry\data

New Configuration Target Name

In the previous Service Registry release, the name of the Ant target you used to configure Service Registry was install. In this release, the target name is configure. The install target is still supported for backward compatibility, but might be removed in a future release. See Chapter 1, Configuring and Setting Up Service Registry, in Service Registry 3.1 Administration Guide for details.

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. For information on Sun's commitment to accessibility, visit http://sun.com/access.

Implementation-Specific API

Service Registry includes an implementation of version 1.0 of the Java API for XML Registries (JAXR) specification. JAXR version 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 version 1.0.

Default Paths and File Names

The following table describes the default paths and file names that are used in this book.

Table 1–2 Default Paths and File Names

Placeholder 

Default Value 

Description 

ServiceRegistry-base

C:\Program Files\Sun\JavaES5\srvc-registry

The base installation directory for Service Registry. 

DomainRegistry-base

C:\Program Files\Sun\JavaES5\srvc-registry

The directory where the Application Server domain for Service Registry is located and where the Service Registry database is located. 

Ant-base

ServiceRegistry-base\install\ant

The directory where the Java ES version of the Ant tool is located.

Hardware and Software Requirements

This section lists the requirements that must be met before installing Service Registry 3.1.

For the most part, the requirements for Service Registry are the same as the requirements for Sun Java System Application Server. The disk space requirements in the following table are in addition to the disk space requirements for Application Server.

Table 1–3 Hardware and Software Requirement

Component 

Requirement 

Operating System 

Windows 2000 Advanced Server SP4 

Windows XP SP2 

Windows 2003 Enterprise Server (32 bit) 

Windows 2003 Enterprise Server (64 bit) 

Minimum Memory 

512 MByte 

Recommended Memory 

1 GByte 

Minimum Disk Space 

65 MByte free 

Recommended Disk Space 

100 MByte free 

Java Virtual Machine (JVM) 

J2SETM release 5_02

Features Nearing End of Life

User Registration Mechanism

This release of Service Registry relies on its own user management and authentication mechanism.

Service Registry 3.1 Documentation

The Service Registry documentation set is available at http://docs.sun.com/coll/1314.2.

Bugs Fixed in This Release

The following table describes the bugs that were reported at Service Registry 3 and that have been fixed or closed in Service Registry 3.1.

Table 1–4 Bugs Fixed or Closed in This Release

Bug Number 

Description 

6290339 

EmailAddress objects cannot be retrieved for Organization objects

6297023 

ClassificationScheme display persists between publish operations

6298946 

Attempt to create reference between Organization objects causes error

6303812 

Duplicate user name causes unclear error message 

6305210 

Registry cannot use English locale if application server domain uses non-English locale 

6312083 

Some searches return unexpected results 

6312094 

Registration wizard ignores required values when creating certificate distinguished name 

6313327 

Service Registry configuration fails after reinstallation 

6313791 

Administration tool fails when -alias option is used

6318002 

Errors occur after creation of ExtrinsicObject or ExternalLink with invalid concept

6323057 

Deleting AuditableEvent for object creation causes exceptions

6324423 

Attempt to view repository item before clicking the Apply button causes error 

6338836 

Problem while creating user account using upload certificate option 

6397404 

WSDL cataloger does not inform user of missing dependencies 

6415812 

java.lang.OutOfMemoryError: PermGen space error

6430997 

Some web console strings are not localized 

6436398 

Web console does not display localized classification schemes and nodes 

6438523 

Set or Change Status combo box not getting updated 

6443263 

Clicking an association results in exception in server log 

6456272 

Clicking the Delete button in the slots tab throws an exception 

6466376 

WSDL cataloger fails to replace temporary IDs 

6470179 

Clicking the Remove button in the Association tab displays an error message 

6472233 

Could not create predefined query 

6477124 

Clicking the Apply button does not persist changes made in the Details page 

Known Issues and Bugs

The following known issues and bugs affect the operation of the Service Registry 3.1 release.

6248218: Versioned RegistryPackage Loses Its Contents

Problem Summary: If versioning is enabled and if you change a RegistryPackage object so as to create a new version of the object, all the package contents disappear from the new version.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6248293: Classification Is Added to Both Old and New Versions of Object

Problem Summary: If versioning is enabled, and if you add a classification to one version of the object and save the object, the classification now exists in both the old version and the new version.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6248418: Adding Classification, ExternalIdentifier, or Slot Deletes ExternalLink

Problem Summary: If versioning is enabled, and if you add a Slot, Classification, or ExternalIdentifier to an object that has an ExternalLink, the ExternalLink disappears from the new version of the object.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6359188: Attempt to Create Association To or From a Deprecated Object Owned by User Does Not Cause IllegalStateException

Problem Summary: The JAXR specification does not allow a user to create an association either to or from an object that is deprecated. However, the Service Registry JAXR provider permits a user to create such an association if the user owns the deprecated object.

6374079: Person and User Details Areas Aren't Identical

Problem Summary: The Details area for a Person object does not allow the user to add a PostalAddress, EmailAddress, or TelephoneNumber, although a Person object contains all those attributes.

Workaround: Create a User object instead of a Person object. You can add all these attributes to a User object.

6407168: Admin Tool add association Command Outputs Misleading Errors

Problem Summary: An attempt to issue the Admin Tool command add association to create an association that the user is not authorized to perform results in a misleading error message. For example, if a user who is not an administrator tries to create an association of type HasMember, the following error message appears:

No Concept object exists for type: HasMember

6407974: Many Files Remain in Temporary Directory

Problem Summary: The WSDL cataloguing service leaves XML and XSLT files on the server, in the directory specified by the java.io.tmpdir property of the install.properties file. In addition, the user authentication process leaves files that begin with .omar and have the suffix .jks in the same directory. These files are not deleted until the Registry domain is stopped.

Workaround: Files with names similar to the following examples can be deleted. The n variable represent a number.

CanonicalXMLValidationService_OutputFilennnnn.xml
InvocationControlFile_WSDLValidationnnnnn.xslt

6422192: NullPointerException When Using Service Registry 3.1 Admin Tool With Service Registry 3.0

Problem Summary: If you use the Service Registry 3.1 Admin Tool with a deployed Service Registry 3.0 version commands such as cp and rm result in a NullPointerException.

Workaround: Use the Service Registry 3.1 Admin Tool only with Service Registry 3.1, and use the Service Registry 3.0 Admin Tool with Service Registry 3.0.

6436598: WSDL Cataloguer Does Not Delete or Update Catalogued Objects When Source Object Is Deleted or Updated

Problem Summary: When you use the WSDL cataloging service to create a service by publishing a WSDL file to the Registry, the Registry creates a large number of objects that are part of the service. When you delete or update the service or the WSDL file, these objects are not deleted or updated. You must delete or update these objects individuallywhen the service or the WSDL file is deleted or updated.

Workaround: None.

6487653: Set or Change Status Button on Object Creation Does Not Work

Problem Summary: While you create an object, the Set or Change Status button is not dimmed. However, you cannot set or change the status of an object that has not yet been created. If you click this button, an error message appears, stating that the object cannot be found.

Workaround: Do not click the Set or Change Status button on an object that you are creating. Click Apply to complete the creation of the object, then search for the object and change its status.

6499274: Status of Modified Object Is Null

Problem Summary: New objects have the the status Submitted. After you modify and save the object, however, its status changes to null. The object should continue to have the status Submitted.

Workaround: None.

6500654: Description and Button in Select Classification Node Window Do Not Match

Problem Summary: If you click the Select Classification Node button in the Search area, the text says to click OK after choosing a concept, but the button is labelled Close.

Workaround: None.

6500668: User Registration Wizard Does Not Explain Meaning of Asterisk

Problem Summary: In the Web Console, the New User's Details form and the User Authentication Details form contain asterisks, but the forms do not explain that an asterisk indicates a required field.

Workaround: The online help states which fields are required.

6502100: WSDL Cataloguer Does Not Handle java.io.tmpdir With Trailing Forward Slash

Problem Summary: An attempt to use the WSDL cataloguer on a zip file fails if the JVM property java.io.tmpdir is set to a value that ends with a forward slash (/). The symptom of the failure is a CatalogingException with a message that states that the cataloguer could not find one of the files in the request.

This problem does not occur on Linux, where the default setting of java.io.tmpdir does not end with a forward slash.

Workaround: Change the value of java.io.tmpdir so that it does not end with a forward slash.

    Perform the following steps:

  1. Log in to the Application Server Admin Console as described in To Use the Application Server Admin Console in Service Registry 3.1 Administration Guide.

  2. Expand the Configurations node.

  3. Expand the server node, server-config (Admin Config).

  4. Click JVM Settings.

  5. Click the JVM Options tab.

  6. Click Add JVM Option.

  7. In the text field, type the following:

    -Djava.io.tmpdir=c:\DOCUME~1\ADMINI~1\LOCALS~1\Temp

  8. Click Save.

  9. Follow the instructions in To Stop and Restart the Application Server Domain for the Registry in Service Registry 3.1 Administration Guide.

After performing these steps, you should be able to publish a zip file that contains multiple WSDL files.

Localization Issues

The following bugs in Service Registry 3.1 are related to localization.

6276676: Localized Strings Missing From Web Console

Problem Summary: In the Web Console, the following strings that should be localized appear in English:

In addition, some labels remain in the previous language when you switch the browser locale and reset the language.

6493416: Online Help Link Leads to English Page

Problem Summary: If you are using the Web Console in a non-English locale for which online help is available, the Bookmark and Relate Help link on the Search Results page leads to a page in the English help rather than the help for your locale.

Workaround: None.

6496070: Event Type Names Are Not Translated for Any Locale

Problem Summary: In the Web Console, if you click the Audit Trail tab for an object in the Details area, the text in the Event Type field (Created, Updated, and so on) always appears in English.

Workaround: None.

6499672: Two Online Help Pages Are Missing in Non-English Locales

Problem Summary: In the Web Console online help, the last two sections are missing from the last chapter (Troubleshooting) in all locales except English.

Workaround: The sections can be found in the online manual, but only in English; see Service Registry 3.1 User’s Guide.

6500664: Untranslated Strings in Online Help in Japanese Locale

Problem Summary: In the online help for the Web Console, cross-references to other books (for example, the Service Registry 3.1 Administration Guide) are not translated into Japanese.

Workaround: None.

6500673: Name and Postal Addresses Order Is Incorrect in Japanese Locale

Problem Summary: In the User Registration Wizard of the Web Console, the order of the name and postal address fields is not localized for the Japanese locale.

Workaround: None.

6500677: Bad Link in Online Help in Japanese Locale

Problem Summary: In the Preface of the online help for the Web Console in the Japanese locale, if you reach the “Default Paths and File Names” section and click the Next link, a Page Not Found error appears. The link is to a nonexistent page.

Workaround: None.

6507818: Service Registry User Guide is Missing For all Non-English Locales

Problem Summary: Service Registry User Guide is missing for all non-English locals on Windows.

Workaround: None.

6510165: Object Names in Details Tabs Are Not Translated

Problem Summary: In the Details area for an object in the Web Console, the name of the object in the Details tab is not translated. Instead, the Java object name is used. Also, in the French locale, the word order is incorrect.

Workaround: None.

Documentation Issues

The following bugs in Service Registry 3.1 are related to documentation.

6500315: One Online Help Page Is Missing

Problem Summary: In the Web Console online help, the “Searching Sun Product Documentation” section is missing from the Preface in all locales.

Workaround: The complete Preface can be found online in English in the Service Registry 3.1 User’s Guide.

6501734: Online Help Has Wrong Name for Explore Directory

Problem Summary: In the Web Console, the online help for the Explore tab incorrectly refers to the root directory name as root. It should be registry.

Workaround: The correct documentation is in Service Registry 3.1 User’s Guide.