You create a data source so that the UDDI registry can use it to access the UDDI database.
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 Cloudscape,
the user ID can be any value.
If you are using a remote
DB2 database on the z/OS operating system, the user ID must be one that is
valid on the remote system.
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.
Click Apply, then save the changes to the master configuration.
Database | Provider type | Implementation type |
---|---|---|
DB2 | DB2 Universal JDBC Driver Provider |
Connection Pool data source |
DB2 | DB2 UDB for iSeries (Native) | Connection Pool data source |
DB2 | DB2 Universal JDBC Driver Provider | Connection Pool data source |
Oracle | Oracle JDBC Driver | Connection Pool data source |
Embedded Cloudscape | Derby JDBC Driver | Connection Pool data source |
Network Cloudscape | Derby Network Server JDBC Driver provider | Connection Pool data source |
Microsoft SQL Server | DataDirect Connect JDBC Driver | Connection Pool data source |
Node=Node01, Server=server1All the JDBC providers that are defined at the selected scope are displayed.
You must not have any other data sources that use this JNDI name. If you have another data source that 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 a Cloudscape database, before you continue, use the uddiRemove.jacl script with the default option to remove the data source and the UDDI application instance.
UDDI30
*LOCAL
-DIS DDFThis 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.
jdbc:oracle:oci8:@<Oracle database name>
This example applies to local and remote Oracle databases.
app_server_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30
For network Cloudscape, also make sure that the Server name and Port
number values match the network server.Leave all other fields unchanged.
profile_root/databases/com.ibm.uddi/UDDI30
For network Cloudscape, also make sure that the Server name and Port
number values match the network server.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.DB2AS400DataStoreHelper |
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.DerbyDataStoreHelper |
Network Cloudscape | com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper |
Microsoft SQL Server | com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper |
In this information ...Related tasks
Setting up a customized UDDI node | IBM Redbooks, demos, education, and moreUse IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. ![]() Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |