UDDI Utility Tools
The UDDI Utility Tools is a suite of functions we can use to migrate, move, or copy UDDI v2 entities, including child entities and their respective v2 entity keys, into a Version 3 UDDI registry.
To use the UDDI Utility Tools suite, run the UDDIUtilityTools.jar file. This file is in the app_server_root/UDDIReg/scripts directory. Alternatively, we can invoke all the functions of UDDI Utility Tools through the supplied public Java API.
The UDDI Utility Tools suite supplied in this release has the same functions as the version supplied in WebSphere Application Server v6.1. However, all UDDI Utility Tools functions in this release use the UDDI v2 API. Note that v2 API does not support publisher-assigned keys.
Use the UDDI Utility Tools to export from v2 and 3 registries (supplying only the v2 representation of the UDDI entity key) and import into the Version 3 registry, using v2 API types. Entities from a Version 3 registry are exported as v2 entities, so elements such as digital signatures are not present. See the topic about saving UDDI Version 3 entities with a supplied key for an example of how to use the Version 3 API to assign our own keys to Version 3 entities.
The UDDI Version 3 Publish API supports publisher-assigned keys, and to promote entities between Version 3 registries, we use normal API functions.
The UDDI Utility Tools suite also has the following uses:
- We can search and select entities from a source UDDI registry by specifying v2 keys or search criteria.
- We can publish canonical tModel entities in a UDDI registry, including child entities.
- We can persist UDDI (v2) entities in an intermediate XML representation so that we can customize and copy those entities to multiple target UDDI registries, by specifying v2 keys.
- We can update existing entities in a target UDDI registry, including child entities.
- We can delete selected entities from a target UDDI registry by specifying v2 keys.
The UDDI Utility Tools suite has five main functions:
- The export function gets a list of UDDI entities from a specified registry and writes them to the UDDI entity definition file, using the specified entity types and keys. The entity type for each key can be business, service, bindingTemplate, or tModel. The entity definition file contains XML that exactly describes each of the specified entities, according to the UDDI Utility Tools schema, which includes the UDDI v2 schema. The UDDI entity definition file separates entities by type, and automatically detects and records tModel entities that the specified entities reference. Use the "referenced tModels" section of the file to ensure that a target registry includes any referenced tModel entities before we import new entities to that registry.
- The import function detects whether a list of UDDI entities already exist in the target registry and, if they do not, create a minimal entity, or stub, with the specified key. The UDDI entities can be supplied through a UDDI entity definition file, or programmatically in a container object. The entities are then published, updating the stubs with the supplied data, and overwriting or ignoring existing entities, as specified. Note that the original key is maintained throughout.
- The promote function combines the export and import steps such that the specified entities are extracted (by key) from the source registry and then imported into the target registry in a single logical step. Optionally, we can generate a UDDI entity definition file.
- The delete function deletes the specified entities from the target UDDI registry. The entities to delete are specified as an entity type, or a list of entity types, and keys, in the same way as for the export function.
- Find matching entities
- The find matching entities function finds a set of entities that match the search criteria and generates a list of entity keys. The search criteria are UDDI Inquiry API objects for each of the various entity types. Use the resulting list of entity keys as input to the export, promote, and delete functions.
This function is available through only the programmatic API.
The following diagram shows relationship between the functions, their input and output, and the source and target UDDI registries:
Use the UDDI registry Migrate the UDDI registry