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

Creating a datasource for the UDDI Registry

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.

Why and when to perform this task

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

Steps for this task

  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.
      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 Connection Pool datasource
    Oracle Oracle JDBC Driver Connection Pool datasource
    Embedded Cloudscape Cloudscape JDBC Driver Connection Pool datasource
    Network Cloudscape Cloudscape Network Server Using Universal JDBC Driver Connection Pool datasource
    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 datasource for the UDDI Registry by following these steps:
    1. Expand 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 datasource.
    6. Fill in the details for the datasource 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 datasources using this JNDI name. If you have another datasource 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 datasource 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
      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
        Note: If you are using a remote database, the database name is the alias that you created to reference the database. See Creating a DB2 database.
      • 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:
        install_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.

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



Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_dsource.html

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