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 data source is used by the UDDI registry to access the UDDI database.Steps for this task
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.
Click Apply and then Save the changes to the master configuration.
Database | Provider type | Implementation type |
---|---|---|
DB2 | DB2 Legacy CLI-based Type 2 JDBC Driver ![]() |
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 |
Server: yourservername
to show the JDBC providers at the server level.
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 |
UDDI30
jdbc:oracle:oci8:@<Oracle database name>
This applies to local and remote Oracle databases.
install_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30For network Cloudscape, also make sure that the Server name and Port number match the network server.
Leave all other fields unchanged.
What to do next
Continue with setting up and deploying your UDDI registry node.