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.
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, you must have installed a DB2 Connect license (See the DB2 documentation for more information).
About 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.
Procedure
- 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 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 |
Note: If you are setting up a UDDI node in a cluster, select 'cluster' as the scope of the JDBC provider.
For details on how to create a JDBC provider, see Creating and configuring a JDBC provider using the administrative console.
- Create the data source for the UDDI registry by following these steps:
- Click 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 data source.
-
Fill in the details for the data source 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 data sources using this JNDI name. If you have another
data source using this JNDI name, then you must 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 data source 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 |
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 |
- Component-managed authentication alias
- 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 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
-
- 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 data source 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.