WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Setting up a default UDDI node with a default datasource

Why and when to perform this task

Use this task to create a UDDI node with predetermined property values and an embedded Cloudscape database. You will not be able to change the mandatory node properties, such as node ID, either during the creation of the node or afterwards. Such a node is suitable for initial evaluation of the UDDI Registry and for development and test purposes. If you want to choose the mandatory node properties yourself, set up a customized node as detailed in Setting up a customized UDDI node.

The UDDI database and datasource are automatically created by running a single script, which also deploys the UDDI Registry application. If you want to have more control over the datasource, refer to Setting up a default UDDI node.

Steps for this task

  1. Create the UDDI node by running the wsadmin script uddiDeploy.jacl, as shown, from the install_root/bin directory.
    The syntax of the command is as follows (this is a Windows operating system example; for Unix or Linux operating systems, add the .sh suffix to the wsadmin command):
    wsadmin [-conntype none] -wsadmin_classpath install_root/cloudscape/lib 
                   -f uddiDeploy.jacl 
                   node_name 
                   server_name
                   default
    where
    • '-conntype none' is optional, and is only needed if the application server is not running.
    • install_root is the directory name of the WebSphere Application Server install location.
    • node_name is the name of the WebSphere node on which the target server runs. Note that the node name is case sensitive.
    • server_name is the name of the target server on which you wish to deploy the UDDI Registry, such as server1. Note the server name entered is case sensitive.
    • 'default' causes the command to create a UDDI node, with default policies, within a Cloudscape database and datasource. This is a special case only for Cloudscape and creates everything required to run a UDDI node.

      [Version 6.0.2]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, as part of the creation of the node. If you choose not to recreate the database, the UDDI node will be created using your existing database.

    For example, to create a UDDI node called 'MyNode' on server 'server1' on a Windows system, you might enter the following (this assumes server1 is started):
    wsadmin -wsadmin_classpath C:\Progra~1\IBM\WebSphere\AppServer\cloudscape\lib -f uddiDeploy.jacl MyNode server1 default
    If the server is not started the command is:
    wsadmin -conntype none -wsadmin_classpath C:\Progra~1\IBM\WebSphere\AppServer\cloudscape\lib -f uddiDeploy.jacl MyNode server1 default

    (Note that these should be entered as one command on a single line)

  2. [Linux][UNIX]If you are using DB2, stop the server if it is running. Edit the user profile for the DB2 user that will start the server. Modify the user profile to run the db2profile script which is located in the root directory of the DB2 userid (for example /home/db2inst1/sqllib/db2profile). Alternatively you can run the db2profile script manually by entering the following command, however you will need to do this every time you restart the server :
    . /home/db2inst1/sqllib/db2profile
    Note: In the above example, notice that the '.' is followed by a single space character.
  3. Click Applications > Enterprise Applications to display the installed applications. Start the UDDI Registry application by selecting the check box next to it and clicking Start. Alternatively start the application server if it is not already running; this will automatically start the UDDI Registry application. The UDDI node is now active.
    Note: Restarting the UDDI application, or the application server, will always result in the reactivation of the UDDI node, even if the node was previously deactivated.

What to do next

Follow the instructions in Using the UDDI Registry Installation Verification Program (IVP) to verify that you have successfully set up the UDDI node.



Related tasks
Setting up a default UDDI node
Setting up a customized UDDI node
Using the UDDI Registry Installation Verification Program (IVP)
Setting up and deploying a new UDDI Registry

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/twsu_default_install1.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)