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.
DB2 | Cloudscape | Oracle | |
---|---|---|---|
DBDriverLocation for class path | DB2_HOME/db2java.zip | app_server_root/cloudscape/lib/otherJars/db2jcc.jar, app_server_root/cloudscape/lib/db2jcc_license_c.jar | ORACLE_HOME/jdbc/lib/ojdbc14.jar |
Driver | COM.ibm.db2.jdbc.app.DB2Driver, or com.ibm.db2.jcc.DB2Driver if you are using a remote DB2 database (you can also set up a local alias to the remote database 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 |
DB2 | Cloudscape |
|
---|---|---|
DBDriverLocation for class path on the z/OS platform | DB2_HOME/jcc/classes/db2jcc.jar, DB2_HOME/jcc/classes/db2jcc_license_cisuz.jar | app_server_root/cloudscape/lib/otherJars/db2jcc.jar, app_server_root/cloudscape/lib/db2jcc_license_c.jar |
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 |
The Security provider configuration section in the above properties file shows the location of the default DummyClientTrustFile.jks file. If you are using 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 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.