Creating 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. You need only perform this task 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 you need to 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 install will be install_root/UDDIReg/databasescripts

arg2

is the path to the location where you want to install the Cloudscape database, for example install_root/profiles/profile_name/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.

1. Run the following java -jar command from the install_root/lib directory, to create a UDDI Cloudscape database using UDDICloudscapeCreate.jar.

   1. On Solaris and HP-UX platforms:

      java -Djava.ext.dirs=install_root/cloudscape/lib:install_root/java/lib/ext -jar 
                 UDDICloudscapeCreate.jar arg1 arg2 arg3 arg4

   2. On all other platforms:

      java -cp install_root/cloudscape/lib/db2j.jar -jar UDDICloudscapeCreate.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.

2. If you are using a remote database (which requires network Cloudscape), or you want to use network Cloudscape for other reasons, configure the Cloudscape Network Server framework as described in Configuring Cloudscape Version 5.1.60x.

   Note: Embedded Cloudscape is not supported for this configuration.

What to do next

Continue with setting up and deploying your UDDI Registry node.

Related tasks
Creating a DB2 database for the UDDI Registry
Creating an Oracle database for the UDDI Registry