WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Creating a data source for the UDDI registry

You create a data source so that the UDDI registry can use it to access the UDDI database.

Before you begin

You must have already created the database for the UDDI registry. These instructions assume that, if you are installing into a cluster, a single database will be used by all members of the cluster.
Note: If you are connecting to a remote DB2 database on the z/OS operating system, you must have installed a DB2 Connect license (See the DB2 documentation for more information).

About this task

Perform this task as part of setting up and deploying a new UDDI registry. The data source is used by the UDDI registry to access the UDDI database.

Procedure

  1. Create a J2C Authentication Data Entry (not required for embedded Cloudscape, but required for network Cloudscape):
    1. Expand Security, Global Security and JAAS Configuration (on the right), then click J2C Authentication Data.
    2. Click New to create a new J2C authentication data entry
    3. Fill in the details as follows:
      Alias
      a suitable (short) name, such as "UDDIAlias"
      Userid

      the database userid (such as db2admin for DB2 or SYSTEM for Oracle), which is used to read and write to the UDDI registry database. For network Cloudscape the userid can be any value.

      If you are using a remote DB2 database on the z/OS operating system, the userid must be one that is valid on the remote system.

      Password
      the password associated with the userid specified above. For network Cloudscape the password can be any value.
      Description
      a suitable description to describe the chosen userid.

      Click Apply and then Save the changes to the master configuration.

  2. Create a JDBC Provider (if a suitable one does not already exist), using the following table to determine the provider type and implementation type for your chosen database:
    Database Provider type Implementation type
    DB2

    DB2 Legacy CLI-based Type 2 JDBC Driver , or DB2 Universal JDBC Driver Provider if you are using a remote DB2 database on the z/OS operating system.

    Connection Pool data source
    Oracle Oracle JDBC Driver Connection Pool data source
    Embedded Cloudscape Cloudscape JDBC Driver Connection Pool data source
    Network Cloudscape Cloudscape Network Server Using Universal JDBC Driver Connection Pool data source
    Note: If you are setting up a UDDI node in a cluster, select 'cluster' as the scope of the JDBC provider.
    For details on how to create a JDBC provider, see Creating and configuring a JDBC provider using the administrative console.
  3. Create the data source for the UDDI registry by following these steps:
    1. Click Resources and JDBC Providers.
    2. Select the desired 'scope' of the JDBC provider you selected or created earlier. For example, select:
      Server: yourservername

      to show the JDBC providers at the server level.

    3. Select the JDBC provider created earlier.
    4. Under Additional Properties, select Data sources (not the Data sources (Version 4) option).
    5. Click New to create a new data source.
    6. Fill in the details for the data source as follows:
      Name
      a suitable name, such as UDDI Datasource
      JNDI name
      set to datasources/uddids - this value is obligatory.
      Note: You must not have any other data sources using this JNDI name. If you have another data source using this JNDI name, then you must either remove it or change its JNDI name. For example, if you have previously created a default UDDI node using Cloudscape, you should use the uddiRemove.jacl script with the default option to remove the data source and the UDDI application instance, before continuing.
      Use this Data Source in container-managed persistence (CMP)
      ensure the check box is unchecked.
      Description
      a suitable description
      Category
      set to uddi
      Data store helper class name
      filled in for you as:
      Database Data store helper class name
      DB2 com.ibm.websphere.rsadapter.DB2DataStoreHelper, or com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper if you are using a remote DB2 database on the z/OS operating system
      Oracle 9i com.ibm.websphere.rsadapter.OracleDataStoreHelper
      Oracle 10g com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
      Embedded Cloudscape com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper
      Network Cloudscape com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper
      Component-managed authentication alias
      • for DB2, Oracle or network Cloudscape, select the alias that you created in step 2 from the pulldown. It will have the node name appended in front of it, for example MyNode/UDDIAlias.
      • for embedded Cloudscape leave this set to (none).
      Container-managed authentication alias
      set to (none)
      Mapping-configuration alias
      set to DefaultPrincipalMapping
      Relational Database Management System data source properties
      • for DB2:
        Database name
        for example:
        UDDI30
        Notes:
        • If you are using a remote database on a distributed system, the database name is the alias that you created to reference the database. See Creating a DB2 distributed database.
        • [Version 6.0.2] If you are using a remote DB2 database on the z/OS operating system, the database name is the local LOCATION value. To find this value, enter the operator command -DIS DDF at the console (or ask your DB2 administrator for the information). Note that this value is case sensitive.
        Driver type [Version 6.0.2]
        this applies only if you are using a remote DB2 database on the z/OS operating system. Set this value to 4.
        Server name [Version 6.0.2]
        this applies only if you are using a remote DB2 database on the z/OS operating system. Set this value to the IP address of the remote machine that is hosting the database. Use the -DIS DDF operator command to find this information (or ask your DB2 administrator for the information).
        Port number [Version 6.0.2]
        this applies only if you are using a remote DB2 database on the z/OS operating system. Set this value to the port that the DB2 database is listening on. Use the -DIS DDF operator command to find this information (or ask your DB2 administrator for the information).
      • for Oracle - URL - for example:
         jdbc:oracle:oci8:@<Oracle database name>

        This applies to local and remote Oracle databases.

      • for Cloudscape (embedded or network) - Database name - for example:
        app_server_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30
        For network Cloudscape, also make sure that the Server name and Port number match the network server.

        Leave all other fields unchanged.

    7. Click Apply and save the changes to the master configuration.
  4. Test the connection to your UDDI database by selecting the check box next to the data source and clicking Test connection. You will see a message similar to "Test Connection for datasource UDDI Datasource on server server1 at node MyNode was successful". If you do not see this message investigate the problem with the help of the error message.

What to do next

Continue with setting up and deploying your UDDI registry node.



Related tasks
Setting up a customized UDDI node
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_dsource.html

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