Perform this task to use a Cloudscape database as the database
store for your UDDI registry. You can use an embedded or network Cloudscape
database, and the database store can be local or remote.
Before you begin
The following steps use a number of variables. Before you
start, decide appropriate values to use for these variables. The variables,
and suggested values, are:
- arg1
- The path of the SQL files. For a standard installation, this is app_server_root/UDDIReg/databaseScripts.
- arg2
- The path to the location where you want to install the Cloudscape
database, for example app_server_root/profiles/profile_name/databases/com.ibm.uddi.
- arg3
- The name of the Cloudscape database. A recommended value is UDDI30,
and this name is assumed throughout the UDDI information. If you use
another name, substitute that name when UDDI30 is used in the UDDI
information.
- arg4
- An optional argument. Either use the value DEFAULT, or omit this
argument. Specify DEFAULT to use the database as a default UDDI node.
This argument is case sensitive.
If you want to create a
remote database, refer first to the database product documentation
about the relevant capabilities of the product.
About this task
You perform this task only once
for each UDDI registry, as part of setting up and deploying a UDDI
registry.
Procedure
- create a UDDI Cloudscape database using UDDICloudscapeCreate.jar.
Run the following java -jar command from the app_server_root/lib
directory.
java -cp app_server_root/cloudscape/lib/db2j.jar -jar UDDICloudscapeCreate.jar arg1 arg2 arg3 arg4
java -Djava.ext.dirs=app_server_root/cloudscape/lib:app_server_root/java/lib/ext -jar
UDDICloudscapeCreate.jar arg1 arg2 arg3 arg4
java -cp app_server_root/cloudscape/lib/db2j.jar -jar UDDICloudscapeCreate.jar arg1 arg2 arg3 arg4
If the Cloudscape database already exists, you
are asked if you want to recreate it. If you choose to recreate the
database, the existing database is deleted and a new one is created
in its place. If you choose not to recreate the database, the command
exits and a new database is not created.
Ensure that the database has the correct
permissions to allow WebSphere Application Server to access it. Run
the following command: chmod -R 777 arg2/arg3
where arg2 and arg3 are
the path and name of the Cloudscape database, as described previously.
- If you are using a remote database, which requires network
Cloudscape, or if 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 that embedded Cloudscape
is not supported for this configuration.
What to do next
Continue
with setting up and deploying your UDDI registry node.