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. The following steps assume that if you are installing into a cluster, all members of the cluster use a single database.
[AIX HP-UX Linux Solaris Windows] Note: To connect to a remote DB2 database on the z/OS operating system, you must have a DB2 Connect license installed. 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 UDDI registry uses the data source to access the UDDI database.

Procedure

  1. Optional: For network Cloudscape, create a Java 2 Connector (J2C) authentication data entry. This step is not required for embedded 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. Complete the following details:
      Alias
      A suitable short name, for example, UDDIAlias.
      Userid

      [AIX HP-UX Linux Solaris Windows] The database user ID, for example, db2admin for DB2, or SYSTEM for Oracle, which is used to read and write to the UDDI registry database. For network Cloudscape, the user ID can be any value.

      [AIX HP-UX Linux Solaris Windows] For a remote DB2 database on the z/OS operating system, the user ID must be one that is valid on the remote system.

      [z/OS] The database user ID, for example db2admin for DB2, which is used to read and write to the UDDI registry database. For network Cloudscape, the user ID can be any value.

      Password
      The password that is associated with the user ID specified previously. For network Cloudscape, the password can be any value.
      Description
      A description for the chosen user ID.

      Click Apply, 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:
    Table 1. Provider types and implementation types
    Database Provider type Implementation type
    DB2

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

    Connection pool data source
    DB2 DB2 Universal JDBC Driver Provider 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

    For a UDDI node in a cluster, select cluster as the scope of the JDBC provider.

    For details about 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:
    1. Click Resources and JDBC Providers.
    2. Select the scope of the JDBC provider that you selected or created earlier, that is, the level at which the JDBC provider is defined. For example, for a JDBC provider that is defined at the level of server1, select the following:
      Node=Node01, Server=server1 
      All the JDBC providers that are defined at the selected scope are displayed.
    3. Select the JDBC provider that you created earlier.
    4. Under Additional Properties, select Data sources. Do not select the Data sources (Version 4) option.
    5. Click New to create a new data source.
    6. Complete the following details for the data source:
      Name
      A suitable name, for example UDDI Datasource.
      JNDI name
      Enter datasources/uddids. This is a mandatory field.

      You must not have any other data sources that use this Java Naming and Directory Interface (JNDI) name. If another data source uses this JNDI name, you must either remove it or change its JNDI name. For example, if you created a default UDDI node previously using an Apache Derby database, before you continue, use the uddiRemove.jacl script with the default option to remove the data source and the UDDI application instance.

      Use this Data Source in container-managed persistence (CMP)
      Ensure that the check box is cleared.
      Description
      A description of the data source.
      Category
      Enter uddi.
      Data store helper class name
      This value is provided automatically:
      Table 2. Data store helper class names
      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
      DB2 com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
      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. It is prefixed by the node name, for example MyNode/UDDIAlias.
      • For embedded Cloudscape, select (none).
      Container-managed authentication alias
      elect (none).
      Mapping-configuration alias
      Select DefaultPrincipalMapping.
      Database-specific data source properties
      • For DB2:
        Database name [AIX HP-UX Linux Solaris Windows]
        The name of the database, for example UDDI30.

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

        For 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. This value is case sensitive.

        Database name [z/OS]
        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. This value is case sensitive.

        For a remote database, the database name is the alias that you created to reference the database. See Creating a DB2 distributed database.

        Driver type [AIX HP-UX Linux Solaris Windows]
        This value is required only for a remote DB2 database on the z/OS operating system. Set this value to 4.
        Driver type [z/OS]
        Set this value to 4.
        Server name [AIX HP-UX Linux Solaris Windows]
        This value is required only for a remote DB2 database on the z/OS operating system. Set this value to the IP address of the remote machine that hosts the database. To find this value, enter the -DIS DDF operator command at the console, or ask your DB2 administrator for the information.
        Server name [z/OS]
        Set this value to the IP address of the machine that hosts the database. To find this value, enter the -DIS DDF operator command at the console, or ask your DB2 administrator for the information.
        Port number [AIX HP-UX Linux Solaris Windows]
        This value is required only for a remote DB2 database on the z/OS operating system. Set this value to the port that the DB2 database listens on. To find this value, enter the -DIS DDF operator command at the console, or ask your DB2 administrator for the information.
        Port number [z/OS]
        Set this value to the port that the DB2 database listens on. To find this value, enter the -DIS DDF operator command at the console, or ask your DB2 administrator for the information.
      • [AIX HP-UX Linux Solaris Windows] For Oracle:
        URL
        The Uniform Resource Locator (URL) of the database from which the datasource obtains connections, for example jdbc:oracle:oci8:@Oracle_database_name.

        [AIX HP-UX Linux Solaris Windows] [z/OS] This example applies to local and remote Oracle databases.

      • For embedded or network Cloudscape:
        Database name [AIX HP-UX Linux Solaris Windows] [z/OS]
        The name of the database, for example:
        app_server_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30.

        For network <ph otherprops="was60only">Cloudscape</ph><ph otherprops="was610a+">Cloudscape, ensure that the Server name and Port number values match the network server.

        Leave all other fields unchanged.

    7. [AIX HP-UX Linux Solaris Windows] [z/OS] 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. A message similar to Test Connection for datasource UDDI Datasource on server server1 at node MyNode was successful is displayed. If a different message is displayed, use the information in that message to investigate and resolve the problem.

What to do next

Continue with setting up and deploying your UDDI registry 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: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=twsu_dsource
File name: twsu_dsource.html