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,
have installed a DB2 Connect license (See the DB2 documentation for more information).
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.
Create a J2C Authentication Data Entry (not required for embedded Cloudscape, but required for network Cloudscape):
Expand Security , Global Security and JAAS
Configuration (on the right), then click J2C Authentication Data .
Click New to create a new J2C authentication data entry
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.
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 datasource
DB2 UDB for iSeries
DB2 and then DB2 UDB for iSeries (Native)
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
Create the datasource for the UDDI Registry by following these steps:
Expand Resources and JDBC
Providers .
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.
Select the JDBC provider created earlier.
Under Additional Properties , select Data Sources (not the Data Sources Version 4 option).
Click New to create a new datasource.
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 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
or com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper if you are using a remote DB2 database on the z/OS operating system.
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 DB2 UDB for iSeries , 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 database.
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
this applies only if you are using a remote DB2 database on the z/OS operating system. Set this value to 4.
Server name
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
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 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.
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.