Setting up a default UDDI node with a default data source

You can create a UDDI node with predetermined property values and an embedded Cloudscape database. You can do this to set up a UDDI registry quickly for test or development purposes.

About this task

When you set up a default UDDI node with a default data source, the mandatory node properties, such as node ID, are set automatically and you cannot change them. You run a single script to create the UDDI database and data source, and to deploy the UDDI registry application. This type of node is suitable for initial evaluation of the UDDI registry and for development and test purposes.

If you want to create a default UDDI node with an embedded Apache Derby database but a different data source, or with a different database, see Setting up a default UDDI node.

If you want to set up a UDDI node with your own properties, including the mandatory node properties, you must set up a customized node. See Setting up a customized UDDI node.

Procedure

  1. Create the UDDI node by running the wsadmin script uddiDeploy.jacl from the app_server_root/bin directory. The syntax of the command is shown below.

    For the UNIX® or Linux® operating systems, add the .sh suffix to the wsadmin command.

    Use the following syntax:

    wsadmin [-conntype none] [-profileName profile_name] 
                   -wsadmin_classpath app_server_root/cloudscape/lib 
                   -f uddiDeploy.jacl 
                   node_name 
                   server_name
                   default
    where:
    • -profileName profile_name is optional, and is the name of the profile in which the UDDI application is deployed. If you do not specify a profile, the default profile is used.
    • -conntype none is optional, and is needed only if the application server is not running.
    • app_server_root is the directory name of the WebSphere® Application Server installation 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 that deploys the UDDI registry, for example, server1. The server name is case sensitive.
    • '-profileName profile_name' is optional, and is the name of the profile in which the UDDI application is deployed. If you do not specify a profile, the default profile will be used.
    • '-conntype none' is optional, and is only needed if the application server is not running.
    • app_server_root is the directory name of the WebSphere Application Server installation location.
    • node_name is the name of the WebSphere node on which the target server runs. 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. The server name entered is case sensitive.
    • default creates a UDDI node with default policies in a Cloudscape database and data source. This option is specific to the Cloudscape database only and creates everything required to run a UDDI node.
      If the UDDI Cloudscape (Derby) database already exists, you are asked if you want to re-create it. If you choose to re-create the database, the existing database is deleted and a new one is created in its place. If you choose not to re-create the database, the command exits and a new database is not created.
      Note: If the application server has already accessed the existing UDDI Cloudscape (Derby) database, the uddiDeploy.jacl script cannot re-create 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.
    For example, to create a UDDI node named MyNode on a server named server1 when server1 is started, you might enter the following command. Enter the command on a single line.
    wsadmin -wsadmin_classpath C:\Progra~1\IBM\WebSphere\AppServer\cloudscape\lib 
    -f uddiDeploy.jacl MyNode server1 default
    To create a UDDI node named MyNode on a server named server1 when server1 is not started, you might enter the following command. Enter the command on a single line.
    wsadmin -conntype none -wsadmin_classpath 
    C:\Progra~1\IBM\WebSphere\AppServer\cloudscape\lib -f uddiDeploy.jacl 
    MyNode server1 default
  2. [AIX] [HP-UX] [Linux] [Solaris] For a DB2® database, stop the server if it is running. Edit the user profile for the DB2 user that starts the server. Modify the user profile to run the db2profile script, which is located in the root directory of the DB2 user ID (for example, /home/db2inst1/sqllib/db2profile). Alternatively, you can run the db2profile script manually, but you must do this every time that you restart the server. Enter the following command (there is a single space character after the period in this command):
    . /home/db2inst1/sqllib/db2profile
  3. Click Applications > Enterprise Applications to display the installed applications. Start the UDDI registry application by selecting the check box next to the application name and clicking Start. Alternatively, if the application server is not already running, start the application server. This action automatically starts the UDDI registry application. The UDDI node is now active.

    If you restart the UDDI application or the application server, the UDDI node always reactivates, even if the node was previously deactivated.

What to do next

Follow the instructions in Using the UDDI registry installation verification test (IVT) to verify that you have successfully set up the UDDI node.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

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

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=twsu_default_install1
File name: twsu_default_install1.html