WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

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.

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. On a standard installation, this is app_server_root/UDDIReg/databaseScripts.
arg2
The path to the location where you want to install the Cloudscape database.

[AIX HP-UX Linux Solaris Windows] [z/OS] For example, app_server_root/profiles/profile_name/databases/com.ibm.uddi.

[i5/OS] For example, profile_root/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 information center.
arg4
An optional argument, which must either be the string 'DEFAULT', or be omitted. Specify DEFAULT if you want the database to be used 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 need to perform this task only once for each UDDI registry, as part of setting up and deploying a UDDI registry.

Procedure

  1. [i5/OS] Start a Qshell session by entering the STRQSH command from the i5/OS command line.
  2. Run the following Java -jar command from the app_server_root/UDDIReg/databaseScripts directory, to create a UDDI Cloudscape database using UDDIDerbyCreate.jar. [Windows]
    java -Djava.ext.dirs=app_server_root/derby/lib;app_server_root/java/lib/ext -jar UDDIDerbyCreate.jar 
    arg1 arg2 arg3 arg4
    [AIX] [Linux] [HP-UX] [Solaris] [AIX HP-UX Solaris] [z/OS] [i5/OS]
    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 are asked if you want to recreate it. If you choose to recreate the database, your 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.
    Note: If the application server has 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.
  3. [z/OS] Ensure that the database has the correct permissions to allow WebSphere Application Server to access it, by running the following command: chmod -R 777 arg2/arg3

    where arg2 and arg3 are the path and name of the Cloudscape database, as described earlier in this topic.

  4. 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.




In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twsu_create_derby.html