Installation Guide - UDDI Browser

This document describes how to install UDDI browser, and how to make UDDI browser work in the OMII client environment that requires all SOAP messages signed using the X509 certificate managed by the OMII client.

Prerequisite

1. Download UDDI Browser 0.2. When this document is being written, it is at http://prdownloads.sourceforge.net/uddibrowser/ub-0.2-bin.zip?download
2. Install OMII client 2.0 according to OMII's documentation. Assume it is installed at the "/OMIICLIENT/" directory.

Installation

The installation is straightforward. Just unzip the previously downloaded zip file. Assume it is unzipped to the "/ub/" directory. In the "/ub/bin/" directory, you will see two files: "ub.bat" and "build.xml". On the Windows platform, invoke "ub.bat" to run UDDI Browser. Or, on both Windows and Linux/Unix, use "ant" to run UDDI browser.

Make SOAP message signed for UDDI browser

By default, UDDI Browser does not support signing SOAP message using X509 certificate that is standardized in WS-Security. In this section, we show how to configure UDDI browser in order to make that SOAP messages sent and received by UDDI browser are signed using the X509 certificate managed by the OMII client environment.

1. Modify the "/ub/config/saop-transport.prop" file: set the value of the property "TransportClassName" to be "org.uddi4j.transport.ApacheAxisTransport".
2. Copy all the files in the "/OMIICLIENT/conf" directory to "/ub/bin/" directory.
3. Add the following content to the "/ub/bin/build.xml" file, before "</project>":

   <property name="omii.client.home" value="/OMIICLIENT"/>
   
   <path id="omii.classpath">
   	<pathelement location="bin"/>
   	<fileset dir="${omii.client.home}/lib"> 
   		<include name="*.*"/>
   	</fileset>
   	<path refid="classpath"/>
   </path>
   
   <target name="omii">
   	<java classname="org.uddibrowser.UDDIBrowser" fork="yes" failonerror="yes">
   	<sysproperty key="uddibrowser.configdir" value="config"/>
   	<classpath refid="omii.classpath"/> </java>
   </target>
   

4. Make sure the "server-config.wsdd" file at the Grimoires server contains the following line:

    <parameter name="enableNamespacePrefixOptimization" value="false"/> 

      This line should be inside the "<globalConfiguration>" element.