test

Service Registry 3.1 Release Notes

Chapter 1 Service Registry 3.1 Release Notes

Service Registry is an ebXML Registry: a federated registry and repository that manages all types of electronic content described by standard and extensible metadata. It provides federated, secure information management of Service Oriented Architecture (SOA) and other content and metadata. It supports the ebXML Registry 3.0 and UDDI 3.0 registry protocols.

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 (JAXR) 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, there is no need to recompile the clients.

New Package Names and Installation Path Names for Service Registry

The Service Registry packages have been renamed as shown in Table 1–1.

Table 1–1 Service Registry Package Name Changes

Package description 

Java ES 4 Package Name 

Java ES 5 Package Name 

Deployment Package on Solaris OS 

SUNWsoar-server

SUNWsrvc-registry-deploy

Deployment Package on Linux and HP-UX systems 

sun-soarserver

sun-srvc-registry-deploy

Development Package on Solaris OS 

SUNWsoar-sdk

SUNWsrvc-registry-dev

Development Package on Linux and HP-UX systems 

sun-soarsdk

sun-srvc-registry-dev

The installation path names for Service Registry have also changed, as shown in Table 1–2.

Table 1–2 Service Registry Installation Path Name Changes

Description 

Java ES 4 Path Name 

Java ES5 Path Name 

Base Installation Directory on Solaris OS 

/opt/SUNWsoar

/opt/SUNWsrvc-registry

Base Installation Directory on Linux and HP-UX systems 

/opt/sun/SUNWsoar

/opt/sun/srvc-registry

Domain and Data Installation Directory on Solaris OS 

/var/opt/SUNWsoar

/var/opt/SUNWsrvc-registry

Domain and Data Installation Directory on Linux and HP-UX systems 

/var/opt/sun/SUNWsoar

/var/opt/sun/srvc-registry

New Configuration Target Name

At the previous release, the name of the Ant target you used to configure Service Registry was install. At this release, the target name is configure. The install target is still supported for backward compatibility, but may 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 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.

Default Paths and File Names

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

Table 1–3 Default Paths and File Names

Placeholder 

Description 

Default Value 

ServiceRegistry-base

Represents the base installation directory for Service Registry. 

Solaris OS: /opt/SUNWsrvc-registry

Linux and HP-UX systems: /opt/sun/srvc-registry

RegistryDomain-base

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

Solaris OS: /var/opt/SUNWsrvc-registry

Linux and HP-UX systems: /var/opt/sun/srvc-registry

Ant-base

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

Solaris OS: /usr/sfw/bin/

Linux and HP-UX systems: /opt/sun/share/bin

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 Table 1–4 are in addition to the disk space requirements for Application Server.

Table 1–4 Supported Operating Systems

Operating System 

Minimum Memory 

Recommended Memory 

Minimum Disk Space 

Recommended Disk Space 

JVM 

Sun Solaris 9, 10 (SPARC, x86) 

640 MB 

1 GB 

80 MB free 

120 MB free 

J2SE 1.4.2_10, J2SE 5_09 

Redhat Enterprise Linux 3.0 U1, 4.0  

640 MB 

1 GB 

65 MB free 

100 MB free 

J2SE 1.4.2_10, J2SE 5_09 

HP-UX 11i (11.11) v1 

640 MB 

1 GB 

65 MB free 

100 MB free 

J2SE 5_03 

Patches and Required Firmware Levels

No additional patches beyond what is documented for Java Enterprise System.

Service Registry 3.1 Documentation

The Service Registry documentation set is available at http://docs.sun.com/coll/1314.2. To learn about Service Registry, refer to the books listed in the following table.

Table 1–5 Service Registry Documentation

Document Title 

Contents 

Service Registry 3.1 Release Notes

Contains the latest information about Service Registry, including known problems. 

Service Registry 3.1 Administration Guide

Describes how to configure Service Registry after installation and how to use the administration tool provided with the Registry. It also describes how to perform other administrative tasks. 

Service Registry 3.1 User’s Guide

Describes how to use the Service Registry Web Console to search Service Registry and to publish data to it. 

Service Registry 3.1 Developer’s Guide

Describes how to use the Java API for XML Registries (JAXR) to search Service Registry and to publish data to it. 

Related Books

When you install Service Registry, it is deployed to the Sun Java System Application Server. For information about administering Application Server, refer to Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

The Java ES documentation set describes deployment planning and system installation. The URL for system documentation is http://docs.sun.com/coll/1286.2. For an introduction to Java ES, refer to the books in the order in which they are listed in the following table.

Table 1–6 Java Enterprise System Documentation

Document Title 

Contents 

Sun Java Enterprise System 5 Release Notes for UNIX

Sun Java Enterprise System 5 Release Notes for Microsoft Windows

Contains the latest information about Java ES, including known problems. In addition, components have their own release notes listed in the Release Notes Collection (http://docs.sun.com/coll/1315.2).

Sun Java Enterprise System 5 Technical Overview

Introduces the technical and conceptual foundations of Java ES. Describes components, the architecture, processes, and features. 

Sun Java Enterprise System Deployment Planning Guide

Provides an introduction to planning and designing enterprise deployment solutions based on Java ES. Presents basic concepts and principles of deployment planning and design, discusses the solution life cycle, and provides high-level examples and strategies to use when planning solutions based on Java ES. 

Sun Java Enterprise System 5 Installation Planning Guide

Helps you develop the implementation specifications for the hardware, operating system, and network aspects of your Java ES deployment. Describes issues such as component dependencies to address in your installation and configuration plan. 

Sun Java Enterprise System 5 Installation Guide for UNIX

Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Guides you through the process of installing Java ES. Also shows how to configure components after installation, and verify that they function properly. 

Sun Java Enterprise System 5 Installation Reference for UNIX

Gives additional information about configuration parameters, provides worksheets to use in your configuration planning, and lists reference material such as default directories and port numbers on the Solaris Operating System and Linux operating environment. 

Sun Java Enterprise System 5 Upgrade Guide for UNIX

Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows

Provides instructions for upgrading to Java ES 5 from previously installed versions. 

Sun Java Enterprise System 5 Monitoring Guide

Gives instructions for setting up the Monitoring Framework for each product component and using the Monitoring Console to view real-time data and create monitoring rules. 

Sun Java Enterprise System Glossary

Defines terms that are used in Java ES documentation.

The URL for all documentation about Java ES and its components is http://docs.sun.com/prod/entsys.5.

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–7 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

6298088 

Multibyte file names not supported for extrinsic objects 

6298946 

Attempt to create reference between Organization objects causes error

6301689 

Content version comment lost when adding new repository item to extrinsic object 

6303812 

Duplicate user name causes unclear error message 

6305138 

UDDI resource bundle is not localized 

6305210 

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

6307262 

Queries by name retrieve multiple copies of each canonical ClassificationScheme

6312083 

Some searches return unexpected results 

6312094 

Registration wizard ignores required values when creating certificate distinguished name 

6312531 

Attempts to set URIs for ExternalLink and ServiceBinding objects fail

6313327 

Service Registry configuration fails after reinstallation 

6313372 

Online help string has an incorrect French translation 

6313791 

Administration tool fails when -alias option is used

6316300 

Objects created in non-default locale have no names 

6317212, 6317242, 6317489, 6317568, 6322668, 6325023 

Web Console contains unlocalized strings for non-English locales 

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 apply button causes error 

6324437 

Pinned objects are duplicated in subsequent searches 

6325095 

Explorer displays incorrect data 

6325116 

Admin Tool starts incorrectly with -locale option

6329272 

Reinstallation of Service Registry deletes an existing repository database 

6330540 

Login immediately after server restart causes exception 

6331538 

Unable to add ClassificationNode to existing node

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, then 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 has Side Effect of Deleting ExternalLink

Problem Summary: If versioning is enabled, and if you add a Slot, a Classification, or an 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 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: In the Web Console, 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

6407195: Most Admin Tool Commands Ignore lcd Setting

Problem Summary: If you use the Admin Tool lcd command to set your current local directory, the cp command accepts path name arguments relative to this directory. Most other commands, however, do not do so (add user, import, and keystoreMover, for example). For these commands you need to specify an absolute path name.

6407974: Many Files Left Around in Temporary Directory

Problem Summary: The WSDL cataloging 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 like the following can be deleted. The characters ????? represent a 5–digit number.

CanonicalXMLValidationService_OutputFile?????.xml
InvocationControlFile_WSDLValidation?????.xslt

6436598: WSDL Cataloger Does Not Delete or Update Cataloged 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; instead, they must be deleted or updated individually. The cataloged objects should be deleted or updated when the service or the WSDL file is deleted or updated.

6479361: FindAllMyObjects Display Should Not Include the Caller's User

Problem Summary: When a user selects and executes the FindAllMyObjects query in the Web Console, the results display includes the User object for the user who executed the query, along with all other objects owned by the user. If the user inadvertently deletes this object, major problems result: the user can no longer perform any actions on objects that he or she published as that user, and he or she must perform user registration again in order to publish more objects. The FindAllMyObjects query should not display this User object. Only the GetCallersUser query should display this object.

Workaround: Be careful not to delete your own User object.

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

Problem Summary: While a user is creating an object of any type in the Web Console, the Set or Change Status button is not grayed out. However, it is not possible to set or change the status of an object that has not yet been created. If the user clicks 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, 6501767: Status of Modified Object is Null

Problem Summary: If you create an object, it has the status Submitted. After you modify it and save it, however, its status changes to null. It should continue to have the status Submitted.

In the Web Console, after you modify the object, the text in the Status pull–down menu changes from Submitted to Select Status (bug 6501767).

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 of the Web Console, the text says to click OK after choosing a concept, but the button is labelled Close.

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 Cataloger Does Not Handle java.io.tmpdir with Trailing Forward Slash

Problem Summary: On the Solaris, HP-UX, and Windows platforms, an attempt to use the WSDL cataloger 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 cataloger 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 (all on one line):

    On Solaris OS and HP-UX: -Djava.io.tmpdir=/var/tmp

    On Windows: -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.

6507387: If Versioning Is Enabled, Attempt to Add Existing Service to Organization Fails

Problem Summary:If you enable versioning and use the JAXR provider to create an Organization object to which you add an existing Service object before saving the Organization, the program fails with a stack trace.

6513883: On HP-UX Systems, User Registration Fails with Internet Explorer 6

Problem Summary: If you perform user registration in the Web Console on an HP-UX system using Internet Explorer 6, you will have problems accessing the generated certificate. Specifically, if you register, download the generated certificate, and then import it into Internet Explorer 6, you may be able to log in to Service Registry once, but subsequent attempts to log in will fail. Assertion failures appear in the server log file.

Workaround: Use a different browser, such as Firefox, to access the Web Console on HP-UX systems.

Compatibility Issues

This section describes the following issues related to compatibility:

Features Nearing 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).

Bugs Related to Compatibility

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

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

6463868: Client Program or Server That Uses JDK 1.6 Results in Errors

Problem Summary: If a JAXR client program runs in a JDK 1.6 environment, or if Service Registry is deployed on a system that is running JDK 1.6, runtime errors result when the program performs a query or publish operation. The underlying problem is that JDK 1.6 uses version 1.3 of the SOAP with Attachments API for Java (SAAJ), while Application Server uses version 1.2.

Workaround: There are two types of workarounds required, one for the client system and one for the server.

ProcedureTo Perform the Client System Workaround

The client system workaround is required if the client system is running JDK 1.6. This workaround involves the following tasks:

  1. Make sure that your classpath includes the following JAR files:

    On Solaris OS:

    /usr/share/lib/saaj-api.jar
/usr/share/lib/saaj-impl.jar

    On Linux and HP-UX systems:

    /opt/sun/share/lib/saaj-api.jar
/opt/sun/share/lib/saaj-impl.jar

    For example, if your Ant targets for a Linux system include a setting like the following, your classpath is correct:

    <path id="classpath">
  <fileset dir="/opt/sun/share/lib">
    <include name="*.jar"/>
  </fileset>
  ...
</path>

  2. Add the following <sysproperty> tags to the <java> targets in your build.xml files:

    <sysproperty key="javax.xml.soap.MessageFactory" 
   value="com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl"/>
<sysproperty key="javax.xml.soap.MetaFactory" 
   value="com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl"/>
<sysproperty key="javax.xml.soap.SOAPConnectionFactory" 
   value="com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory"/>
<sysproperty key="javax.xml.soap.SOAPFactory" 
   value="com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl"/>

ProcedureTo Perform the Server System Workaround

The server system workaround involves the following tasks:

  1. Change to the Application Server lib directory.

    On Solaris OS: cd /opt/SUNWappserver/appserver/lib

    On Linux and HP-UX systems: cd /opt/sun/appserver/lib

  2. Make backup copies of the two SAAJ JAR files in the Application Server lib directory. For example:


    cp saaj-api.jar saaj-api.jar.v1.2
cp saaj-impl.jar saaj-impl.jar.v1.2

  3. Copy the SAAJ 1.3 JAR files to the Application Server lib directory.

    On Solaris OS: 


    cp /usr/share/lib/saaj-api.jar .
cp /usr/share/lib/saaj-impl.jar .

    On Linux and HP-UX systems: 


    cp /opt/sun/share/lib/saaj-api.jar .
cp /opt/sun/share/lib/saaj-impl.jar .

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

  5. Expand the Configurations node.

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

  7. Click JVM Settings.

  8. Click the JVM Options tab.

  9. Click Add JVM Option.

  10. In the text field, type the following:


    -Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

  11. Click Add JVM Option again.

  12. In the text field, type the following:


    -Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl

  13. Click Save.

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

6475651: Java ES 2005Q4 Service Registry Login Fails After Application Server Upgrade

Problem Summary: If you installed and used the previous version of Service Registry (from Java ES 2005Q4), and you now upgrade to the Java ES 5 version of Application Server but do not upgrade to the Java ES 5 version of Service Registry, a login failure occurs if you try to use the same certificate you previously created with the Web Console.

Workaround: Edit the web.xml file and the security policy file for Service Registry.

    To stop the Application Server domain for the Registry and edit the web.xml file, follow these steps:

  1. Change to the Service Registry install directory:

    On Solaris OS: cd /opt/SUNWsoar/install

    On Linux and HP-UX systems: cd /opt/sun/SUNWsoar/install

  2. Stop the Application Server domain for the Registry:

    Ant-base/ant -f build-install.xml appserver.domain.stop

  3. Change to the directory RegistryDomain-base/domains/registry/applications/j2ee-modules/soar/WEB-INF/.

  4. Open the file web.xml in a text editor.

  5. Inside the <security-constraint> tag, after the </web-resource-collection> tag, insert the following:

    <auth-constraint>
  <role-name>have.client.cert</role-name>
</auth-constraint>

  6. After the </security-constraints> tag, insert the following:

    <error-page>
  <error-code>400</error-code>
  <location>/registry/thin/AuthenticateError.jsp</location>
</error-page>
<security-role>
  <description>all subjects who have client certificates</description>
  <role-name>have.client.cert</role-name>
</security-role>

  7. Save and close the web.xml file.

    To edit the security policy file and restart the domain, follow these steps:

  1. Change to the following directory:

    On Solaris OS: cd /var/opt/SUNWsoar/domains/registry/config

    On Linux and HP-UX systems: cd /var/opt/sun/SUNWsoar/domains/registry/config

  2. Open the file server.policy in a text editor.

  3. Add the following grants to this file:

    grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/soar/WEB-INF/lib/-"{
       permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};

grant codeBase "file:${com.sun.aas.instanceRoot}/generated/jsp/j2ee-modules/soar/-" {
      permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
};

  4. Save and close the server.policy file.

  5. Restart the Application Server domain for the Registry:

    Ant-base/ant -f build-install.xml appserver.domain.start

  6. Open your web browser to the URL http://localhost:6060/soar. You should now be able to log in and publish.

6491246: Upgrade Fails on HP-UX Platform

Problem Summary: If you installed and used the previous version of Service Registry (from Java ES 2005Q4) on an HP-UX system, and you now upgrade to the Java ES 5 version of Service Registry, the installation fails with an error message stating that the problem is with HADB (High Availability Database). The problem is that the HADB packages were installed in what the Java ES 5 installer sees as a non-default location.

The problem also occurs if you uninstall the Java ES 2005Q4 version of Application Server and then install the Java ES 5 versions of Service Registry and Application Server.

Workaround: If you uninstalled Application Server, you must remove the sun-hadb packages before you reinstall.

If you are upgrading directly from the Java ES 2005Q4 version of Service Registry to the Java ES 5 version, the steps are more complicated:

  1. Remove the sun-hadb packages.

  2. Install the Java ES 5 versions of Service Registry and Application Server.

  3. Edit the file /opt/sun/appserver/config/asenv.conf as follows:

    • Change the line

      AS_ANT="/opt/sun/share/lib/ant/bin"

      to

      AS_ANT="/opt/sun/bin"

    • Change the line

      AS_ANT_LIB="/opt/sun/share/lib/ant/lib"

      to

      AS_ANT_LIB="/opt/sun/share/lib"

    • Add the following two lines:

      AS_DERBY_INSTALL="/opt/sun/javadb"
AS_MFWK_HOME=/opt/sun/mfwk/share

  4. In the directory /opt/sun/appserver/lib, create a subdirectory named endorsed.

  5. Copy the file /opt/sun/javadb/lib/derby.jar into the directory /opt/sun/appserver/lib/endorsed.

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, when you switch the browser locale and reset the language, some labels remain in the previous language.

Workaround: Click Logout or End Session, then restart the session or log in again.

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.

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.

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 Chapter 4, Troubleshooting, in 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.

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 on the New User's Details form is not localized for the Japanese locale.

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.

6509544: Some Error Messages Are Not Translated

Problem Summary: Some error messages have not been translated into non-English locales. For example, the error messages you see if you try to create an extrinsic object without specifying a repository item, or if you try to modify an object that you do not own, have been only partly translated.

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.

6510540: One Line of Redirect Page Is Not Translated into Japanese

Problem Summary: In the Web Console, on the redirect page that appears when you log in to the Registry, the last line has not been translated into Japanese.

6515105: User Registration Text Field Is Missing in Some Locales

Problem Summary: In the User Registration Wizard of the Web Console, the text field for State or Province is missing from the New User's Details form in the French, German, and Spanish locales.

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, one section (“Searching Sun Product Documentation”) 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 Using the Explore Tab in Service Registry 3.1 User’s Guide.