Create a Cloudscape database for the UDDI registry

 

Perform this task if you want to use Cloudscape (embedded or network) as the database store (either local or remote) for your UDDI registry.

 

Overview

We need to perform this task only once for each UDDI registry, as part of setting up and deploying a UDDI registry.

If you are creating a remote database, use the database product documentation to familiarize yourself with the relevant capabilities of the product before proceeding with this task.

Before you begin The commands below use a number of arguments for which enter appropriate values. You should decide the values that you will use before you start. The arguments used, and suggested values, are:

arg1

is the path of the SQL files, which on a standard installation will be app_server_root/UDDIReg/databasescripts

arg2

is the path to the location where you want to install the Cloudscape database.

For example, app_server_root/profiles/profile/databases/com.ibm.uddi

arg3

is the name of the Cloudscape database. A recommended value is UDDI30, and this name is assumed throughout the UDDI documentation. If you use another name, you should substitute that name whenever you see 'UDDI30' in other sections of the UDDI documentation.

arg4

is an optional argument, and must either be omitted or be the string 'DEFAULT'. DEFAULT should only be specified if you want your database to be used as a default UDDI node. Note that this argument is case sensitive.

 

Procedure

Run the following Java -jar command from the app_server_root/UDDIReg/databaseScripts directory, to create a UDDI Cloudscape database using UDDIDerbyCreate.jar.



java -Djava.ext.dirs=app_server_root/derby/lib;app_server_root/java/lib/ext -jar UDDIDerbyCreate.jar 
arg1 arg2 arg3 arg4





java -Djava.ext.dirs=app_server_root/derby/lib:app_server_root/java/lib/ext -jar UDDIDerbyCreate.jar 
arg1 arg2 arg3 arg4

If the Cloudscape database already exists, you will be asked if you want to recreate it. If you choose to recreate the database, your existing database will be deleted and a new one created in its place. If you choose not to recreate the database, the command will exit and a new database will not be created.

If the appserver already accessed the existing Cloudscape database, the uddiDeploy.jacl script cannot recreate the database. Use the uddiRemove.jacl script to remove the database, as described in Removing a UDDI registry node, restart the server and run the uddiDeploy.jacl script again.

1. If you are using a remote database (which requires network Cloudscape), or you want to use network Cloudscape for other reasons, for example if you want to use Cloudscape with a cluster, configure the Cloudscape Network Server framework as described in the managing derby network server section of the Cloudscape information center.

 

What to do next

Continue with setting up and deploying your UDDI registry node.

---

 

Related tasks

Setting up a default UDDI node
Setting up a customized UDDI node