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 Solaris HP-UX Linux 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

Complete 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 Apache Derby, create a Java™ 2 Connector (J2C) authentication data entry. This step is not required for embedded Apache Derby.
    1. Click Security > Global security > [Authentication] Java Authentication and Authorization Service > J2C authentication data.
    2. Click New to create a new J2C authentication data entry.
    3. Enter the following details:
      Alias
      A suitable short name, for example UDDIAlias.
      Userid

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

      [AIX Solaris HP-UX Linux 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 Apache Derby, the user ID can be any value.

      Password
      The password that is associated with the user ID specified previously. For network Apache Derby, the password can be any value.
      Description
      A description of the 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, by using the following table to determine the provider type and implementation type for your chosen database.
    Table 1. Provider types and implementation types. The table lists the correct provider type and implementation type for each database.
    Database Provider type Implementation type
    [AIX Solaris HP-UX Linux Windows]DB2 [AIX Solaris HP-UX Linux Windows]DB2 Universal JDBC Driver Provider [AIX Solaris HP-UX Linux Windows]Connection pool data source
    [IBM i]DB2 [IBM i]DB2 UDB for iSeries (Native) [IBM i]Connection pool data source
    [z/OS]DB2 [z/OS]DB2 Universal JDBC Driver Provider [z/OS]Connection pool data source
    [AIX Solaris HP-UX Linux Windows][IBM i]Oracle [AIX Solaris HP-UX Linux Windows][IBM i]Oracle JDBC Driver [AIX Solaris HP-UX Linux Windows][IBM i]Connection pool data source
    Embedded Apache Derby Derby JDBC Driver Connection pool data source
    Network Apache Derby Derby Network Server JDBC Driver provider Connection pool data source
    Microsoft SQL Server DataDirect Connect JDBC Driver

    Microsoft SQL Server 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 the topic about configuring a JDBC provider by using the administrative console.
  3. Create the data source for the UDDI registry:
    1. Click Resources > JDBC > 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 (WebSphere Application Server V4) option.
    5. Click New to create a new data source.
    6. In the Create a data source wizard, enter the following data:
      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 that uses 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.

      Component-managed authentication alias
      • For DB2[AIX Solaris HP-UX Linux Windows][IBM i], Oracle, or network Apache Derby, select the alias that you created in step 2. The alias is prefixed by the node name, for example MyNode/UDDIAlias.
      • For embedded Apache Derby, select (none).
    7. Click Next.
    8. On the database-specific properties page of the wizard, enter the following data:
      • For DB2:
        [AIX Solaris HP-UX Linux Windows]Database name
        [AIX Solaris HP-UX Linux 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.

        [IBM i]Database name
        [IBM i]The name of the database, for example *LOCAL.
        [z/OS]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.

        [AIX Solaris HP-UX Linux Windows]Driver type
        [AIX Solaris HP-UX Linux Windows]This value is required only for a remote DB2 database on the z/OS operating system. Set this value to 4.
        [z/OS]Driver type
        [z/OS]Set this value to 4.
        [AIX Solaris HP-UX Linux Windows]Server name
        [AIX Solaris HP-UX Linux 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.
        [z/OS]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.
        [AIX Solaris HP-UX Linux Windows]Port number
        [AIX Solaris HP-UX Linux 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.
        [z/OS]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 Solaris HP-UX Linux Windows][IBM i]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 Solaris HP-UX Linux Windows][z/OS]This example applies to local and remote Oracle databases.

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

        For network Apache Derby, ensure that the Server name and Port number values match the network server.

        Leave all other fields unchanged.

      Use this Data Source in container-managed persistence (CMP)
      Ensure that the check box is cleared.
    9. Click Next, then check the summary and click Finish.
    10. Click the data source to display its properties, and add the following information:
      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
      [AIX Solaris HP-UX Linux Windows]DB2 [AIX Solaris HP-UX Linux Windows]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
      [IBM i]DB2 [IBM i]com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
      [z/OS]DB2 [z/OS]com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
      [AIX Solaris HP-UX Linux Windows][IBM i]Oracle 11g [AIX Solaris HP-UX Linux Windows][IBM i]com.ibm.websphere.rsadapter.Oracle11gDataStoreHelper
      Embedded Apache Derby com.ibm.websphere.rsadapter.DerbyDataStoreHelper
      Network Apache Derby com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper
      [AIX Solaris HP-UX Linux Windows]Microsoft SQL Server [AIX Solaris HP-UX Linux Windows]com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

      com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper

      Mapping-configuration alias
      Select DefaultPrincipalMapping.
    11. [AIX Solaris HP-UX Linux Windows][z/OS]Click Apply and save the changes to the master configuration.
    12. [IBM i]Click Apply.
    13. [IBM i]Select Additional Properties > Custom Properties > libraries.
    14. [IBM i]Enter IBMUDI30,IBMUDS30 in the Value field and click OK.
    15. [IBM i]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 Node01 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.

指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:18
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twsu_dsource
檔名:twsu_dsource.html