Backing up and restoring the UDDI Registry database

 

Overview

If you want to protect the data in your UDDI Registry database, one can back up and restore the database using the facilities of the database product your UDDI node is on.

Cloudscape

To backup a Cloudscape UDDI Registry database, ensure that the UDDI application is stopped (and hence, not accessing the Cloudscape database), and ensure that no other application is using the Cloudscape UDDI30 database, then make a copy of the UDDI30 directory using the file system that the directory resides upon.

To restore a Cloudscape database, replace the UDDI30 file structure with the back up. Note that any updates made since the back up was taken will be lost.

Non-Cloudscape

Use the appropriate import and export tools for the database being used to contain the UDDI Registry.

• Backup

  Include elements in schemas named IBMUDI30 and IBMUDS30

• Restore

  Restore the back up by deleting the schemas IBMUDI30 and IBMUDS30, recreating database structures using the original scripts (with slight modifications), and importing the previously saved data, as described in the steps below:

  1. Delete the schemas IBMUDI30 and IBMUDS30 this will result in any IBM UDDI structures being destroyed.

  2. Create database structures (for DB2 see Creating a DB2 database, for Oracle see Creating an Oracle database or for Cloudscape, see Creating a Cloudscape database for details) as for the original creation except that the final step (xxxxxx_70xxxx.*) must not be run. This will result in a database containing the basic data required by the UDDI Registry, into which your backed-up data may be imported.

  3. Delete all the rows in the table IBMUDS30.UDDIDBSCHEMAVER, to avoid a clash between a row inserted by the scripts and the row that was backed-up. To do this, use the following command

     delete from IBMUDS30.UDDIDBSCHEMAVER
     

  4. Restore the previously backed-up data in schemas IBMUDI30 and IBMUDS30

---

 

---