Databases and production use of the UDDI registry

The UDDI registry fully supports a number of databases and can be used for development and test purposes. However, there are factors to consider when you decide which database is appropriate for the anticipated UDDI registry production use.

It is important to consult the information supplied by your chosen database vendor, but you must also consider the likely size and volume of requests, and whether the general performance and scalability of the UDDI registry is important.

For example, the Apache Derby database supports the full function of the UDDI registry, but it is not an enterprise level database and it does not have the same characteristics, for example, scaling or performance, as enterprise databases such as DB2 .

Supported configurations: WebSphere Application Server supports direct customer use of the Apache Derby database in test environments only. The product does not support direct customer use of Apache Derby database in production environments. The product supports the use of Apache Derby only by internal application server componentsf in production environments.

If we need multiple connections to the UDDI registry database (for example to use the UDDI registry in a cluster configuration) and Apache Derby is the preferred database, use the network option for Apache Derby. This is because embedded Apache Derby has a limitation that allows only one JVM to access or load a database instance at any one time. That is, two application servers cannot access the same Apache Derby database instance at the same time.

The UDDI registry can support multiple users, even if a single database connection exists.

Related concepts

Overview of the Version 3 UDDI registry

About Apache Derby

Data source minimum required settings for Apache Derby