Java Reference
In-Depth Information
pany that you do not intend for public consumption. As your organization grows its SOA,
you need to have a single location that catalogs your services. The process of service enable-
ment in your organization is likely to graph like a hockey stick. That is, it can take a while
for people to understand SOA, see the value, get the infrastructure set up, and deliver some
services. But once it takes seed in an organization, SOA can blossom fairly quickly. You need
a way to manage service proliferation so that developers do not create redundant services.
NOTE
If you are looking at repository products, many of them will fold a registry into the repository, so you
may not require separate installations. You might look into products that combine a registry with an
ebXML repository, as ebXML offers a more robust set of features.
Getting jUDDI
The current releases of jUDDI are available for download from
http://ws.apache.org/juddi/re-
leases.html
.
As of this writing, the current release is 2.0rc5, available as a WAR for installation
in a container such as Tomcat, and as a standalone JAR. jUDDI is a frontend to a relational
database, accessed with JDBC. So aside from the jUDDI bundle, you need to connect to one
of the supported databases as well.
Deploying jUDDI on Tomcat
Let's look at how to set up jUDDI on Tomcat. These instructions work with jUDDI WAR
2.0rc5 and Tomcat 6.0.16. Once you have downloaded jUDDI and have Tomcat running, here
are the steps to set it up:
1. Rename the file “juddi”, as this will make configuring the datasource and other items easi-
er. There are a number of properties that expect your installation to be at <host>/juddi. Of
course, you can change all of those if you prefer. They can be found under the root of the
WAR in juddi.properties.
2. Copy juddi.warinto the tomcat-home/webappsdirectory. It will deploy automatically.
3. Visit the jUDDI homepage in your new installation at
http://localhost:8080/juddi-
web-2.0rc5
.
4. Click the “validate” link. You will see the “happy jUDDI” page indicating whether jUDDI
was able to find all of the components necessary to run.
If your database is not set up or is set up incorrectly, you may see an error such as this one on
the “happy jUDDI” page:
