WAS v8.5 > Reference > Command-line utilities

UDDI Utility Tools configuration file

Configuration data for UDDI Utility Tools is in a configuration properties file, which describes the runtime environment, UDDI and database locations and access information, logging information, security configuration, entity definition file location, and other flags to control whether referenced entities can be imported, overwritten, or both.

A sample configuration properties file, UDDIUtilityTools.properties, is supplied with UDDI Utility Tools. By default, this file is in the app_server_root/UDDIReg/scripts directory. If we do not specify a properties path, by default, the configuration properties file is searched for in the current directory.

To set up and use the configuration file, use the following procedure:

  1. Modify the sample configuration properties file:

    • Set the class path, which must include the current directory (.), the UDDIUtilityTools.jar, and all the dependent jars, as listed in UDDI Utility Tools prerequisites. The class path must include the database driver JAR file, for example, db2java.zip.

    • If we are configuring a JSSE provider, add the .jar file containing the provider to the class path. To configure a JSSE provider, set the jsse.provider property. Default is com.ibm.jsse.IBMJSSEProvider. To specify the Federal Information Processing Standard (FIPS) JSSE provider, set the jsse.provider property to com.ibm.fips.jsse.IBMJSSEFIPSProvider.

    • Set other properties as required. For details, see the comments in the sample UDDIUtilityTools.properties file.

    • Change localhost to the name of your server.

    • Change the port number 9080 to your internal HTTP port.

  2. When you run UDDI Utility Tools, specify the modified configuration properties file.

Note: Use forward slashes in paths. Back slashes can be interpreted as escape sequences such as tab spaces. For example,

becomes

The following example shows the sample configuration properties file. 

##############################################
# Runtime environment                        #
# (if invoking using java -jar...)           #
# "X Y" required around paths with spaces.   #
# Replace WAS_HOME with your WebSphere       #
# Application Server home path.              #
# Replace DB2_HOME with the locations of DB2 #
# db2java.zip is for DB2 - replace this with #
# appropriate database driver file.          #
##############################################
classpath=.;WAS_HOME/UDDIReg/scripts/UDDIUtilityTools.jar;
WAS_HOME/plugins/com.ibm.ws.runtime.jar;WAS_HOME/plugins/com.ibm.uddi.jar;
WAS_HOME/dev/javaEE/j2ee.jar;"DB2_HOME/SQLLIB/java/db2java.zip"

##############################################
# SOAP entry points for source UDDI          #
############################################## 
fromInquiryURL=http://localhost:9080/uddisoap/inquiryapi
fromGetURL=http://localhost:9080/uddisoap/get

##############################################
# SOAP entry points for target UDDI          #
############################################## 
toInquiryURL=http://localhost:9080/uddisoap/inquiryapi
toPublishURL=http://localhost:9080/uddisoap/publishapi

##############################################
# UDDI registry user information             #
#                                            #
# Note: This information must match the user #
# information that was used to publish the   #
# entities on the target UDDI registry.      #
############################################## 
userID=UNAUTHENTICATED
password=NONE

##############################################
# Configuration for destination UDDI DB      #
############################################## 
dbDriver=COM.ibm.db2.jdbc.app.DB2Driver
dbUrl=jdbc:db2:uddi30
dbUser=db2admin
dbPasswd=db2admin

##############################################
# Security provider configuration            #
##############################################
# Indicates whether security is required on the target registry secure.connection=true

# The location of the truststore if security is required trustStore.fileName=TrustFile.jks

# The password for the trust store
trustStore.password=WebAS

# The JSSE Provider class name jsse.provider=com.ibm.jsse.IBMJSSEProvider

##############################################
# Trace and message logging configuration    #
############################################## 
# detail level of message output (all functions)
verbose=true

# detail level of trace output.
# 1: severe
# 2: normal # 3: detail traceLevel=3

# path to message log file (relative or absolute)
messageLogFileName=logs/messages.log

# path to trace.log file (relative or absolute)
traceLogFileName=logs/trace.log

############################################## 
# Miscellaneous Options                      #
############################################## 
# indicates whether existing entities are overwritten (import/promote)
# Note: tModels in referencedTModels section are never overwritten, 
#       regardless of this setting. To overwrite tModels, they must 
#       be present in the tModels section.
overwrite=false   

# indicates whether referenced entities are imported (import/promote)
importReferencedEntities=true

# location of entity definition file, used for (export/import)
UddiEntityDefinitionFile=definitions/entities01.xml

# namespace prefix to use in definition file (export)
namespacePrefix=promote


Related


Use the UDDI registry


Reference:

UDDI Utility Tools prerequisites
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


+

Search Tips   |   Advanced Search