+

Search Tips   |   Advanced Search

Create an Apache Derby database for the UDDI registry


Perform this task to use an Apache Derby database as the database store for the UDDI registry. Use an embedded or network Apache Derby database, and the database store can be local or remote.

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, the path is APP_ROOT/UDDIReg/databasescripts.

arg2

The path to the location where you want to install the Apache Derby database.

For example, APP_ROOT/profiles/profile_name/databases/com.ibm.uddi.

arg3

The name of the Apache Derby database. A recommended value is UDDI30, and this name is assumed throughout the UDDI information. If we 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.

To create a remote database, refer first to the database product documentation about the relevant capabilities of WAS ND.

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

 

  1. Create a UDDI Apache Derby database using UDDIDerbyCreate.jar.

    Run the following Java-jar command from the APP_ROOT/UDDIReg/databaseScripts directory.

    (Windows) 

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

    [AIX] [Linux] [HP-UX] [Solaris]

    (UNIX) 

    java -Djava.ext.dirs=APP_ROOT/derby/lib:APP_ROOT/java/jre/lib/ext -jar UDDIDerbyCreate.jar  arg1 arg2 arg3 arg4
    If the Apache Derby database already exists, we are asked to re-create it. If we choose to re-create the database, the existing database is deleted and a new one is created in its place. If we choose not to re-create the database, the command exits and a new database is not created.

    If the appserver has already accessed the existing Apache Derby database, the uddiDeploy.jacl script cannot re-create the database. Use the uddiRemove.jacl script to remove the database, restart the server, and run the uddiDeploy.jacl script again.

  2. For a remote database, which requires network Apache Derby, or to use network Apache Derby for other reasons, for example, to use Apache Derby with a cluster, configure the Apache Derby Network Server framework.

 

Next steps

Continue with setting up and deploying the UDDI registry node.

 

Related tasks


Set up a default UDDI node
Set up a customized UDDI node