Before you use the UDDI Utility Tools, ensure that the
required .jar files are available.
To run the UDDI Utility Tools,
you must use the IBM® Development
Kit for Java code that is supplied
with WebSphere® Application
Server. This development kit is in the app_server_root/java/bin
directory.
Ensure that the following .jar files are available
to the UDDI Utility Tools. You must specify the locations of the .jar
files in the class path in the UDDI Utility Tools properties file:
- UDDIUtilityTools.jar
- This file is the UDDI Utility Tools .jar file and is in the app_server_root/UDDIReg/scripts
directory.
- com.ibm.uddi.jar
- This file contains the UDDI4J classes and is in the app_server_root/plugins
directory.
- j2ee.jar
- This file contains some required Java platform
for enterprise applications classes, and is in the app_server_root/lib
directory.
- com.ibm.ws.runtime.jar
- This file is the Apache SOAP implementation and is in the app_server_root/plugins
directory.
- DbDriver
- This driver is needed for the UDDIUtilityTool to connect to your
target database. See the following table for the values you must specify
for your chosen database:
Table 1. DbDriver
values for databases. The table details the values needed
to connect to different databases.
|
DB2® |
Apache Derby |
DBDriverLocation for class path |
DB2_HOME/jcc/classes/db2jcc.jar, DB2_HOME/jcc/classes/db2jcc_license_cisuz.jar |
app_server_root/derby/lib/derbyclient.jar, app_server_root |
Driver |
com.ibm.db2.jcc.DB2Driver |
com.ibm.db2.jcc.DB2Driver |
URL |
jdbc:db2://host:database_port/database_location |
jdbc:db2j:net://host:1527/database_name |
where:
- app_server_root is
the directory location of WebSphere Application
Server.
- DB2_HOME is the directory location of DB2, for example c:\Program
Files\SQLLIB\java12\
- database_port is the port that
the DB2 database is listening
on.
- database_name is the name of
the Apache Derby database. Ensure that database_name includes
the path to the database, for example profile_root/databases/com.ibm.uddi/UDDI30
Notes:
- For Apache Derby, make the database network-enabled so that it
can handle multiple connections. For further details, refer to the
section about managing the Derby Network Server in the Derby Server
and Administration Guide.
- For DB2,
add DB2_HOME/icc/lib to your LD_PATH_LIBRARY (or LD_LIBRARY_PATH)
and LIBPATH environment variables.
The Security provider configuration section
in the configuration properties file shows the location of the default
DummyClientTrustFile.jks file. If you use your own truststore, ensure
that the location is placed here.
The UDDI Utility Tools use
UDDI Version 2 SOAP Inquiry and Publish interfaces. These APIs are
protected, as described in the topic about access control for UDDI
registry interfaces. The UDDI Utility Tools also access the UDDI registry
database through the database driver, and access to the database is
controlled by the database management system.