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.
The following
steps assume that
if you are installing into a cluster, all members of the cluster use
a single database. Note: To connect to a remote DB2® database on the z/OS® operating system, you must have a DB2 Connect license installed.
See the DB2 documentation for
more information.
About this task
Complete this task as part
of setting up and deploying a
new UDDI registry. The UDDI registry uses the data source to access
the UDDI database.
Procedure
- Optional: For
network Apache Derby, create
a Java 2 Connector (J2C) authentication
data entry. This step is not required for embedded Apache Derby.
- Click .
- Click New to create a new J2C
authentication data entry.
- Enter the
following details:
- Alias
- A suitable
short name, for example UDDIAlias.
- Userid
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 Apache Derby, the user ID can be any value.
For 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 Apache Derby, the user
ID can be any value.
- Password
- The
password that is associated with the user ID specified previously.
For network Apache Derby, the password can be any value.
- Description
- A description of the user ID.
Click Apply, then save the
changes to the master configuration.
- Create a JDBC provider, if a suitable one does not
already
exist, by using the following table to determine the provider type
and implementation type for your chosen database.
Table 1. Provider types and implementation types. The table lists the correct provider type and implementation
type for each database.
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 Apache Derby |
Derby JDBC Driver |
Connection
pool data source |
Network Apache
Derby |
Derby Network Server JDBC Driver
provider |
Connection pool data source |
Microsoft® SQL
Server |
DataDirect Connect JDBC Driver Microsoft SQL Server JDBC
Driver
|
Connection pool data source |
For
a UDDI node in a cluster, select cluster as
the scope of the JDBC provider.
For details about how to create
a JDBC provider, see the topic about configuring a JDBC provider by
using the administrative console.
- Create the
data source for the UDDI registry:
- Click .
- Select
the scope of the JDBC provider that you selected
or created earlier, that is, the level at which the JDBC provider
is defined. For example, for a JDBC provider that is defined
at the level of server1, select the following:
Node=Node01, Server=server1
All
the JDBC providers that are defined at the selected scope are displayed.
- Select the JDBC provider that you created
earlier.
- Under Additional
Properties,
select Data sources. Do not select the Data
sources (WebSphere Application Server V4) option.
- Click New to create
a new data
source.
- In the Create a data
source wizard,
enter the following data:
- Name
- A suitable name, for example UDDI Datasource.
- JNDI name
- Enter datasources/uddids. This is a mandatory
field.
You must not have any other data sources that use this Java
Naming and Directory Interface (JNDI) name. If another data source
uses this JNDI name, you must either remove it or change its JNDI
name. For example, if you created a default UDDI node previously that
uses an Apache Derby database, before you continue, use the uddiRemove.jacl script with the default
option to remove the data source and the UDDI application instance.
- Component-managed authentication alias
- For DB2, Oracle, or network Apache
Derby, select the alias that you created in step 2. The alias is prefixed
by the node name, for example MyNode/UDDIAlias.
- For embedded Apache Derby, select (none).
- Click Next.
- On the database-specific properties page of
the wizard,
enter the following data:
- For DB2:
- Database name
- The name of the database, for example UDDI30.
For
a remote database on a distributed system, the database name is the
alias that you created to reference the database. See Creating a DB2 distributed database.
For
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. This value is case sensitive.
- Database name
- The name of the database, for example *LOCAL.
- Database name
- 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. This 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.
- Driver type
- This value is required only for a remote DB2 database on the z/OS
operating system. Set this value to 4.
- Driver type
- Set this value to 4.
- Server name
- This value is required only for a remote DB2 database on the z/OS
operating system. Set this value to the IP address of the remote machine
that hosts the database. To find this value, enter the -DIS
DDF operator command at the console, or ask your DB2 administrator
for the information.
- Server name
- Set this value to the IP address of the machine that hosts the
database. To find this value, enter the -DIS DDF operator
command at the console, or ask your DB2 administrator for the information.
- Port number
- This value is required only for a remote DB2 database on the z/OS
operating system. Set this value to the port that the DB2 database
listens on. To find this value, enter the -DIS DDF operator
command at the console, or ask your DB2 administrator for the information.
- Port number
- Set this value to the port that the DB2 database listens on. To
find this value, enter the -DIS DDF operator command
at the console, or ask your DB2 administrator for the information.
- For Oracle:
- URL
- The Uniform Resource Locator (URL) of the database from which
the datasource obtains connections, for example jdbc:oracle:oci8:@Oracle_database_name.
This example applies to local and remote Oracle
databases.
- For Apache Derby (embedded or network):
- Database name
- The name of the database, for example:
app_server_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30.
- Database name
- The name of the database, for example:
profile_root/databases/com.ibm.uddi/UDDI30
For network Apache Derby, ensure that the Server
name and Port number values match
the network server.
Leave all other fields unchanged.
- Use this Data Source in container-managed persistence (CMP)
- Ensure that the check box is cleared.
- Click Next,
then check the summary
and click Finish.
- Click
the data source to display its properties, and
add the following information:
- Description
- A description of the data source.
- Category
- Enter uddi.
- Data store helper class name
- This value is provided automatically:
Table 2. Data store helper class names
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 11g |
com.ibm.websphere.rsadapter.Oracle11gDataStoreHelper |
Embedded Apache Derby |
com.ibm.websphere.rsadapter.DerbyDataStoreHelper |
Network Apache Derby |
com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper |
Microsoft SQL Server |
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper
|
- Mapping-configuration alias
- Select DefaultPrincipalMapping.
- Click Apply and
save the changes to the master configuration.
- Click Apply.
- Select .
- Enter IBMUDI30,IBMUDS30 in
the Value field and click OK.
- 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. A message similar to Test Connection
for datasource UDDI Datasource on server server1 at node Node01 was
successful is displayed. If a different message is
displayed, use the information in that message to investigate and
resolve the problem.
What to do next
Continue with setting
up and deploying your UDDI registry
node.