Network Deployment (Distributed operating systems), v8.0 > Reference > Command-line utilities

UDDI Utility Tools prerequisites

Before you use the UDDI Utility Tools, ensure that the required .jar files are available.

To run the UDDI Utility Tools, use the IBM Development Kit for Java code that is supplied with WAS. This development kit is in...

WAS_HOME/java/bin

Ensure that the following .jar files are available to the UDDI Utility Tools. We 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...

WAS_HOME/UDDIReg/scripts

com.ibm.uddi.jar

This file contains the UDDI4J classes and is in...

WAS_HOME/plugins

j2ee.jar

This file contains some required Java platform for enterprise applications classes, and is in...

WAS_HOME/lib

com.ibm.ws.runtime.jar

This file is the Apache SOAP implementation and is in...

WAS_HOME/plugins

DbDriver

This driver is needed for the UDDIUtilityTool to connect to your target database. See the following table for the values specify for your chosen database:

DbDriver values for databases. The table details the values needed to connect to different databases.

	DB2	Apache Derby	Oracle
DBDriverLocation for class path	DB2_HOME/db2java.zip	WAS_HOME/derby/lib/derbyclient.jar	ORACLE_HOME/jdbc/lib/ojdbc6.jar
Driver	COM.ibm.db2.jdbc.app.DB2Driver, or com.ibm.db2.jcc.DB2Driver for a remote DB2 database. We can also set up a local alias to the remote database by using the DB2 client.	com.ibm.db2.jcc.DB2Driver	oracle.jdbc.OracleDriver
URL	jdbc:db2://host:database_name	jdbc:db2j:net://host:1527/database_name	jdbc:oracle:thin:@host:1521: database_name

where:

• WAS_HOME is the directory location of WAS.
• DB2_HOME is the directory location of DB2, for example c:\Program Files\SQLLIB\java12\
• ORACLE_HOME is the directory location of Oracle, for example c:\oracle\ora92\
• database_name is the name of the database. For Apache Derby, 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/sqllib/lib to your 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 v2 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.
Access control for UDDI registry interfaces
Use the UDDI registry

Related

UDDI Utility Tools configuration file
UDDI entity definition file
UDDI Utility Tools at a command prompt
UDDI Utility Tools through the API
Save UDDI v3 entities with a supplied key
UDDI Utility Tools limitations and resolutions
UDDI Utility Tools
Derby Server and Administration Guide

+

Search Tips   |   Advanced Search