Java WSDP Registry Server Home

Contents

• Read This Section First
• What This Release Includes
• Setting the Logging Level for the Registry Server
• Using the Registry Server with the Security Manager
• Current Limitations
• Known Bugs

Before you work with this release of the Java^TM Web Services Developer Pack (Java WSDP) Registry Server, make sure that you have installed the required software and are on a supported operating system. You can find this information in the Java WSDP home page and Release Notes and the Java WSDP Registry Server home page.

Note: The file <JWSDP_HOME>/webapps/registry-server.war may only be used for the purposes of designing, developing, and testing programs.

This release includes

• The Java WSDP Registry Server 1.0_02 release
• The Xindice database, the repository for registry data
• A tool named Indri that allows you to create and inspect database data using a graphical user interface

You can also use the Registry Browser and sample programs provided by the Java API for XML Registries (JAXR) to create and query registry data.

This release implements Version 2 of the Universal Description, Discovery and Integration (UDDI) project, including

• UDDI Version 2.00 API Specification Errata 3
• UDDI Version 2.00 Data Structure Reference Errata 2

The release contents are arranged in the following structure within the Java WSDP installation:

At this release, the Java WSDP supports the Jakarta Commons Logging API. For details about changing the general default logging level, see the Java WSDP Release Notes. This section describes how to modify the logging level for the Registry Server.

You can use either of the following methods to specify the logging level for the Registry Server:

• Before you start Tomcat, edit the <JWSDP_HOME>/conf/jwsdp.properties file. To change the default level for the Registry Server to debug, for example, specify the following:

  org.apache.commons.logging.simplelog.log.com.sun.registry_server=debug
  

• If you use the Ant tool, you can use a <sysproperty> tag to specify logging levels for the java built-in task. For the Registry Server, use the following tag:

  <sysproperty key="org.apache.commons.logging.simplelog.log.com.sun.xml.registry_server" 
        value="debug"/>
  

You can specify any of the following logging levels:

fatal
error
warn
info
debug
trace

The default level is warn.

Logging output appears in the file <JWSDP_HOME>/logs/catalina.out.

grant codeBase "file:${catalina.home}/work/Standard Engine/localhost/registry-server/WEB-INF/classes/-" {
   permission java.io.FilePermission "${catalina.home}/common/endorsed/xercesImpl.jar", "read";
   permission java.io.FilePermission "${catalina.home}/common/endorsed/xalan.jar", "read";
   permission java.io.FilePermission "${catalina.home}/bin/orb.properties", "read";
   permission java.util.PropertyPermission "*", "read, write";
   permission java.net.SocketPermission "*", "listen,connect,resolve";
};

The 1.0_02 release of the Java WSDP Registry Server has the following limitations:

• The find_relatedBusinesses message is not supported.
• For <find_*> messages, the find qualifiers orLikeKeys, combineCategoryBags, and serviceSubset are not supported. All other find qualifiers are supported.

At this release, the Java WSDP Registry Server has the following known issue:

• Because the find_relatedBusinesses request message is not supported in this release (see Current Limitations), use of the JAXR API findAssociations method will fail with the Registry Server. The Registry Server will return an E_unsupported message in a SOAP Fault if find_relatedBusinesses is used.