Taking a backup and restoring data in the UDDI Registry Server

There are two methods of taking a backup of your data that are explained as follows:

• The first method is to take a backup of the database files. This method is simple and it preserves the unique ID values of the entries when restoring data.
• The second method is to export the contents of the Universal Description Discovery and Integration (UDDI) Registry Server to an XML file. This method does not preserve the unique ID values of the entries when restoring data.

Both the methods of taking backup and of restoring data are explained in the following sections.

To take a back up of the database

1. Stop the Tomcat server that hosts UDDI Registry Server.
2. Navigate to the <ATRIUMCORE_HOME>/shared/wsc/data/bmcuddi/derby-db directory.
3. Add the entire contents of derby-db/ to a zip file.
   This file is a snapshot of your data.
4. Rename the file to include the date and time of the backup and store it in a reliable location.
5. Start the Tomcat server.

To restore the database

This procedure assumes that you have a zip file with a saved backup.

1. Stop the Tomcat server that hosts UDDI Registry Server.
2. Navigate to the <ATRIUMCORE_HOME>/shared/wsc/data/bmcuddi/ directory.
3. If the derby-db/ directory exists, move it to another directory outside the <ATRIUMCORE_HOME> location, or rename it, such as derby-db.bak.
4. Extract the contents of the backup zip file.
   The expanded directory should be derby-db.
5. Start the Tomcat server.

To take a back up of the UDDI server

1. Do not stop the Tomcat server. If the server is not running, start the server.
   It must remain running while performing this procedure.
2. In the <ATRIUMCORE_HOME>/wsc/wsregistryapi/registryserver.properties file, verify the correct endpoints.
   • If the endpoints are incorrect, edit the file and correct them.

   • To test the validity of the endpoints, open a browser and enter the endpoint as listed but with an added ?wsdl to the end of it. If the WSDL for each endpoint appears correctly, then the endpoints are likely correct.
     In the following example, the hostname is mozart.yourcompany.com and the port is 8080:

     bmc.uddi.registryserver.url.security=
     http://mozart.yourcompany.com:8080/uddi/services/security
     bmc.uddi.registryserver.url.inquiry=
     http://mozart.yourcompany.com:8080/uddi/services/inquiry
     bmc.uddi.registryserver.url.publishing=
     http://mozart.yourcompany.com:8080/uddi/services/publication
     bmc.uddi.registryserver.url.subscription=
     http://mozart.yourcompany.com:8080/uddi/services/subscription

3. In a command-line interface, go to the <ATRIUMCORE_HOME>/wsc/wsregistryapi/migration/scripts/ directory.
4. At the command prompt, enter the following command:
   • Windows: test_export.cmd
   • UNIX/Linux: ./test_export.cmd
5. When the script prompts for a username and password, enter the root publisher's username and password.
   If the script executes successfully, it creates a migration_list.xml file in the directory. This file is a snapshot of all of the businesses, applications, and services that are published into the registry at the point that the script was executed.
6. Rename the migration_list.xml file to include the date and time of the backup and store it in a reliable location.

To restore the UDDI server

When restoring data to the UDDI server by importing from an exported data file, you must start with a clean database. To ensure that the database is clean and empty, complete the following steps:

1. Stop the Tomcat server that hosts UDDI Registry Server.
2. Navigate to the <ATRIUMCORE_HOME>/shared/wsc/data/bmcuddi/ directory.
3. If the derby-db/ directory exists, move it to another directory outside the <ATRIUMCORE_HOME> location, or rename it, such as derby-db.bak.
4. Start the Tomcat server.
   Because the database directory is no longer present, it creates a new, empty database instance on startup.
5. Do not stop the Tomcat server. If the server is not running, start the server.
   It must remain running while performing this procedure.
6. In the <ATRIUMCORE_HOME>/wsc/wsregistryapi/registryserver.properties file, verify the correct endpoints.
   • If the endpoints are incorrect, edit the file and correct them.

   • To test the validity of the endpoints, open a browser and enter the endpoint as listed but with an added ?wsdl to the end of it. If the WSDL for each endpoint appears correctly, then the endpoints are likely correct.
     In the following example, the hostname is mozart.yourcompany.com and the port is 8080:

     bmc.uddi.registryserver.url.security=
     http://mozart.yourcompany.com:8080/uddi/services/security
     bmc.uddi.registryserver.url.inquiry=
     http://mozart.yourcompany.com:8080/uddi/services/inquiry
     bmc.uddi.registryserver.url.publishing=
     http://mozart.yourcompany.com:8080/uddi/services/publication
     bmc.uddi.registryserver.url.subscription=
     http://mozart.yourcompany.com:8080/uddi/services/subscription

7. In a command-line interface, go to the <ATRIUMCORE_HOME>/wsc/wsregistryapi/migration/scripts/ directory.
8. Copy the export data file created in the previous previous into the directory, and rename it to migration_list.xml.
9. At the command prompt, enter the following command:
   • Windows: test_import.cmd
   • UNIX/Linux: ./test_import.cmd
10. When the script prompts for a username and password, enter the root publisher's username and password.
11. If the script executes successfully, all of the entries in the data file are entered into the UDDI registry.