Backing up and restoring UDDI publication links
When you save a gateway configuration,
the deployment details through which a deployed Web service has been published
to UDDI by the gateway are not saved. Here are the reasons for not backing
up these details:
- When a gateway is upgraded, or otherwise
removed without first using the gateway administrative console to un-publish
each Web service from UDDI, then the associated entries in UDDI registries
are not removed.
- When a gateway is restored,
if the UDDI publication details are also restored, then the Web
services are re-published to UDDI by the gateway.
- When a gateway publishes the same service twice to a UDDI registry, the
registry does not overwrite the initial publication. The registry creates
a second copy of the TModel and Service Definition.
- When a gateway removes a service from a UDDI registry, it only removes
the last one published. This means that it can leave behind outdated TModels
and Service Definitions.
To preserve the integrity of the UDDI registries, restoring the gateway
does not automatically re-publish any Web services to UDDI. But if you know
that a service has been un-published from UDDI (for example because you removed
it manually before backing up the gateway configuration) then you can safely
re-publish it to UDDI after the configuration is restored.

Backing up and restoring a gateway configuration
Searchable topic ID:
cwsg_save_restore_uddi
Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/cwsg_save_restore_uddi.html