+

Search Tips   |   Advanced Search

UDDI Utility Tools at a command prompt

We can start UDDI Utility Tools at a command prompt. In some situations, there are prerequisites before running the command.

Ensure that you are using the correct level of Java code by setting the PATH statement to include the Java code supplied with WebSphere Application Server. For example, from the command line, type:


(zos)

For DB2 on the UNIX or Linux operating systems, before you use the command to start UDDI Utility Tools, run the db2profile script. The db2profile script is in the DB2 instance home directory under sqllib. To invoke the script, type the following. Notice that a single space character follows the period (.).

The DB2 user must have a db2profile at $HOME/sqllib/db2profile.

Use one of the following approaches to start UDDI Utility Tools:

Usage of UDDIUtilityTools.jar:

    java -jar UDDIUtilityTools.jar {function} [options]

Functions:

  -promote <entity source>  Promote entities between registries   -export <entity source>   Extract entities from a registry to XML   -delete <entity source>   Delete entities from a registry   -import                    Create entities from XML to a registry  where <entity source> is one of:
  -tmodel|-business|-service|-binding <key> Specify a single entity type and key   -keysFile | -f <filename> Specify a file containing entity types and keys

Options:

  -properties <filename>    Specify the path to a configuration file  -overwrite | -o            Overwrite an entity if it already exists
  -log | -v                  Output verbose messages
  -definitionFile <filename> Specify the path to a UDDI entity definition file  -importReferenced          Import entities referenced by source entities

The following command-line options override property settings in the configuration file:


Examples

(dist) The following examples use the Windows operating systems file system.

Export a single business to the entity definition file specified in a properties file in the current directory.

Export a single business to the entity definition file specified in a properties file in the current directory and use a keys file to specify the entities to export.

Export a single business to the entity definition file specified in a properties file in the current directory and use a keys file to specify the entities to export. Also, display verbose output on the command line.

Import the contents of the default entity definition file specified in a UDDIUtilityTools.properties file in the current directory.

Import the contents of the default entity definition file specified in a UDDIUtilityTools.properties file in the current directory and import referenced tModel entities into the target registry.

Import the entities from an entity definition file at the specified location.Note the use of forward slashes even though this is an example on a Windows operating systems file system.

Import the entities from the default entity definition file including referenced tModel entities. The overwrite options specifies that any entities, excluding referenced tModel entities found in the target registry, are overwritten.

Promote a single service from a source to a target registry using the properties file at a specified location.

Promote a set of entities specified in a keys file.

Promote a set of entities specified in a keys file and overwrite existing entities in the target registry.

Promote a set of entities specified in a keys file, including referenced tModel entities.

Promote a set of entities specified in a keys file, but also create an entity definition file containing the promoted entities.

Logically delete a single tModel entity. We cannot physically delete tModel entities.

Delete all the entities specified in the keys file. Except for tModel entities, all other entities are physically deleted from the target registry.


A keys file example

The following example shows the keys to export, promote, or delete from the target registry: 

#
# Keys of entities to be exported, promoted from source registry or deleted  # from target registry #
# Note: keys must be comma separated and on SAME line # Note: property names are case sensitive. ('tmodels=' are ignored)
 businesses=97C77097-AC6C-4CA0-A6C4-452F7045C470,  4975E949-581F-4FCA-AD5F-E08280E05F9F
services=BB3864BB-1578-4833-8179-14391F14791F
bindings=
tModels=273F1727-7BFF-4FB5-A1FD-BA5C45BAFD9C

If the importReferenced property is set to true, the list of tModel entities in the referencedTModels section is imported to the target registry. If the referencedTModel is new, minimal entities are created. If the referencedTModel already exists, it is never overwritten, regardless of the overwrite property value. This approach prevents commonly referenced tModel entities, such as categorization tModel entities, from being updated unnecessarily.

To update a referencedTModel, you must manually move the referencedTModel definition to the tModel entities section in the entity definition file and set overwrite to true.


Subtopics


Related tasks

  • Use the UDDI registry

  • UDDI Utility Tools prerequisites
  • UDDI Utility Tools configuration file
  • UDDI entity definition file
  • UDDI Utility Tools through the API
  • Save UDDI Version 3 entities with a supplied key
  • UDDI Utility Tools limitations and resolutions