Before you begin
You must have already created the database for the UDDI Registry.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
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 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 |
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.
Click Apply and save the changes to the master configuration.
What to do next
Continue with setting up and deploying your UDDI Registry node.