+

Search Tips   |   Advanced Search

 

Database considerations for 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 your anticipated UDDI registry production use.

It is important to consult the information that is supplied by your chosen database vendor, but you also need to consider the likely size and volume of requests, and whether the general performance and scalability of the UDDI registry is important. For example, the Cloudscape 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.

Cloudscape is not supported for production use.

If we need multiple connections to the UDDI registry database (for example to use the UDDI registry in a cluster configuration) and Cloudscape is your preferred database, use the network Cloudscape option. This is because embedded Cloudscape has a limitation that allows only one Java virtual machine to access or load a database instance at any one time. That is, two appservers cannot access the same Cloudscape 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 V3 UDDI registry

 

Related tasks


Setting up and deploying a new UDDI registry

 

Related Reference


About Cloudscape v10.1.x