Before you use the UDDI Utility Tools, ensure that the required .jar files are available.
DB2® | Apache Derby | Oracle | |
---|---|---|---|
DBDriverLocation for class path | DB2_HOME/db2java.zip | app_server_root/derby/lib/derbyclient.jar | ORACLE_HOME/jdbc/lib/ojdbc6.jar |
Driver |
You 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 |
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.