Installation guide
This document explains how to install the UDDI server on various application servers and using
various databases.
The installation consists of two steps: Configure a war file, and deploy it to an application server.
Once the war file has been configured, it can be deployed to any number of servers. The server does
not contain any state.
Requirements
● JDK 5.0+
● 512 MB RAM for Java
● Ant 1.6
● Database server. Tested databases are Oracle 10i, Mysql 5.0, and PostgreSQL 8.1, 8.2, 8.3
● Application server. Tested servers are Tomcat 5.5/6.0, JBoss 4.0, WebSphere 6.1, and BEA
WebLogic 9.2. Only standard servlet support is required.
If you have a checkout of the server, run “ant build-war” in the root dir, copy target/dist/uddi.war to
install/ and then change to the install/ dir. Otherwise, unpack the distribution file and change to the
new dir (uddi-server-{timestamp}).
Databases
MySQL Community Server 5.0
Ensure that MySQL is properly installed. In this example MySQL is running a default installation
on Windows XP on localhost port 3306 with database uddi.
Set-up a new user account in MySQL: I ran the following
mysql> CREATE DATABASE uddi;
mysql> GRANT ALL PRIVILEGES ON uddi.* TO 'uddiuser'@'localhost' IDENTIFIED BY
'uddisecret';
mysql> FLUSH PRIVILEGES;
Note on setup: In order to perform when using find_* requests with many categories or identifiers,
Mysql needs to be tuned. In the server configuration file, insert this in the [mysqld] section:
optimizer_search_depth=4
If this is not set, some queries will take extremely long to complete, while the database takes all
available cpu time.
Which created the Manager user with password secret.
– Run ant in the current dir. This prompts for server configuration
– Use the following properties: when asked by the install script
– hibernate.driver=com.mysql.jdbc.Driver
– hibernate.dialect=org.hibernate.dialect.MySQLDialect
– hibernate.url=jdbc:mysql://localhost:3306/mysql
– hibernate.username=uddiuser
– hibernate.password=uddisecret
Adapt the url, username and password to your local installation.
Example:
U:\workspace\uddi-server-install-20070326-1329>ant
...
define-storagefactoryclass:
[input] Please select a Storage Factory Class.(LDAP,Hibernate,ldap,hibernate)
hibernate
get-hibernate-driver:
[input] Driver class:
com.mysql.jdbc.Driver
get-hibernate-dialect:
[input] Dialect:
org.hibernate.dialect.MySQLDialect
get-hibernate-url:
[input] Connection url:
jdbc:mysql://localhost:3306/uddi
get-hibernate-username:
[input] Username:
uddiuser
get-hibernate-password:
[input] Password:
uddisecret
get-server-host:
[input] Server host and port (eg localhost:8080):
localhost:8080
get-server-domain:
[input] Server domain (UDDI node id):
mydomain.com
get-server-root:
[input] Data root (LDAP path):
anything
get-schemaexport:
[input] Export schema? (true,false)
true
The war-file is now configured for MySQL. Deploy it to your application server. In the above
example, you can now access the administration console via localhost:8080/uddi . Default login is
admin/admin.
Automated configuration
Instead of entering each value manually when prompted, the configuration process can be
automated by using a build.properties file.
Copy one of the distributed build.properties.* to build.properties and edit it. The only value to leave
unchanged should be storageFactoryClass.
After this, run ant as usual. This should configure the system without prompting for values.
Application Servers
Make sure that your database/LDAP is installed and configured, and that the UDDI war file is
configured for this database/LDAP.
JBoss
Simply install JBoss and copy the configured war file to the deployment directory. In JBoss 4.0.1
on windows, this is
<JBOSS-INSTALLDIR>/server/default/deploy
Start JBoss.
IBM WebSphere Application Server 6.1
● Point your web browser to the WAS administration console (on my local installation this is:
https://localhost:9043/ibm/console/
● Select “Install new applications” in the “Applications” menu.
● Chose the configured war file from your file system. Select an appropriate context root, e.g.,
uddi, and press “Next”
● Select the appropriate WAS installation options, and finish configuration
● Remember to save the configuration.
● Select the “Enterprise applications” in the “Applications” menu. Select the Application
name that you just installed (uddi_war in my case), and press “start”; the UDDI server
should now be running.
● To run the UDDI server administration console, point your browser to the context root that
you selected. In my case this is:
http://localhost:9080/uddi/
BEA WebLogic 9.2
● Point your web browser to the WebLogic administration console.
● Select “Deployments” in the “domain structure” menu.
● Click the “Lock and edit” button.
● Click “Install” and navigate to your configured war file. I used “upload your file(s)” since
the navigation didn't work properly on my installation. Press next.
● Select “Install this deployment as an application”, and configure the installation options.
● Press “Finish” and then activate the changes.
● Go back to the “deployments” menu, select the application and press “start”; confirm.
Apache Tomcat 5.5/6.0
Simply drop the .war file into the deployment directory (<tomcat-install-dir>/webapps), and start up
tomcat.
UDDI Browser
The server does not contain any browsing capabilities. Instead, a separate application must be
installed. At the moment, the Novell UDDI Browser is recommended. It consists of a war file which
can be deployed on any server. If the UDDI server is installed at a location different from localhost:
8080/uddi, a properties file must be edited after deployment.
Bootstrapping
When installing a replica slave, it can take a very long time to do the first replication if the master
server contains a lot of data. The OpenUDDI server supports a bootstrapping process to speed this
up.
The process requires a XML data file with the master UDDI data. Two platorms are supported at
the moment: OpenUDDI and Oracle UDDI (Systinet). See the server administration guide for
information on how to export data from OpenUDDI, and the Oracle UDDI export guide for
information on how to export from Oracle UDDI. The following assumes that the data is placed in a
file in /home/uddi named export.xml.
Bootstrapping should be performed during server installation. After running ant normally, run 'ant
import'. This prompts for a master UDDI username and password and a file URL. The username
and password is used to configure a subscription automatically. The file URL must point to the data
file, in this example it would be file:///home/uddi/export.xml.
The bootstrap process can be run at any time, but be aware that it will delete any existing
subscriptions.