Apache jUDDICommunity Documentation

Chapter 2. Getting Started

2.1. What Should I Download?
2.2. Using the JAR
2.3. Using the WAR File
2.4. Using the Tomcat Bundle
2.5. Using jUDDI Web Services

The jUDDI server deploys as a WebARchive (war) named juddiv3.war. Within jUDDI, there are three downloadable files (juddi-core.jar, juddi.war, and juddi-tomcat.zip). You should determine which one to use depending on what level of integration you want with your application and your platform / server choices.

JUDDI also ships with client side code, the juddi-client.jar. The jUDDI server depends on the juddi-client.jar in situations where one server communicates to another server. In this setup one server acts as a client to the other server. The juddi-client.

The juddi-core module produces a JAR which contains the jUDDI source and a jUDDI persistence.xml configuration. jUDDI's persistence is being actively tested with both OpenJPA and with Hibernate. If you are going to use only the JAR, you would need to directly insert objects into jUDDI through the database back end or persistence layer, or configure your own Web Service provider with the provided WSDL files and classes.

As with the JAR, you need to make a decision on what framework you would like to use when building the WAR. jUDDI's architecture supports any JAX-WS compliant WS stack (Axis, CXF, etc). The jUDDI 3.0.GA release ships with CXF in the Tomcat bundle, but any docs or descriptors to support other WS stacks would be welcome contributions. Simply copy the WAR to the deploy folder of your server (this release has been tested under Apache Tomcat 6.0.20), start your server, and follow the directions under “using jUDDI as a Web Service”.

The jUDDI Tomcat bundle packages up the jUDDI WAR, Apache Derby, and a few necessary configuration files and provides the user with a pre-configured jUDDI instance. By default, Hibernate is used as the persistence layer and CXF is used as a Web Service framework. To get started using the Tomcat bundle, unzip the juddi-tomcat-bundle.zip, and start Tomcat :

% cd apache-tomcat-6.0.20/bin
% ./startup.sh

It is suggested that you use JDK 1.6 with the Tomcat 6 bundle. On Mac OS X you can either change your JAVA_HOME settings or use /Applications/Utilities/Java Preferences.app to change your current JDK.

Once the server is up and running can make sure the root data was properly installed by browsing to http://localhost:8080/juddiv3

You should see the screen show in Figure 2.1, “jUDDI Welcome Page”.


Once the jUDDI server is started, you can inspect the UDDI WebService API by browsing to http://localhost:8080/juddiv3/services

You should see an overview of all the Services and their WSDLs.


The services page shows you the available endpoints and methods available. Using any SOAP client, you should be able to send some sample requests to jUDDI to test: