Configure global UDDI properties

 

To modify any of the global UDDI properties, you will need to edit the file called uddi.properties . More than one version of this file exists and the version you need to edit depends on

  • whether you are in the installation phase or are updating the properties as a post installation step

  • whether you are configured for a Deployment Manager or Base Application Server environment

The location of the file edit will be one of the following:

Deployment Manager Configurations

  1. If you are in the process of installing the UDDI Registry application for the first time into a Deployment Manager cell and wish to make some generic changes before deploying it in the cell, the uddi.properties file will be located in the <DeploymentManager-install-dir>/properties directory. If you are reinstalling the UDDI Registry application into a Deployment Manager cell, then edit the file in the location described under 2 below.

    Note: Please note that in a Deployment Manager configuration some properties (such as persister and getServletURLprefix) are dynamically set up in the uddi.properties file, during subsequent installation processing.

  2. If the UDDI Registry is already configured into an appserver within a Deployment Manager cell (i.e. you are undertaking post installation configuration changes), then the uddi.properties file edit will be located in the configuration repository, under the Deployment Manager filing system; that is in <DeploymentManager-install-dir>config/cells/<cellname>/nodes/<nodename>/servers/<servername>, where <cellname> is the name of the Deployment Manager cell, <nodename> is the name of the node in which the appserver is installed, and <servername> is the name of the appserver in which you have installed the UDDI Registry.

Application Server Configurations

  1. If you are in the process of installing the UDDI Registry application into an Application Server only environment you will be advised during the installation process when to make changes to the uddi.properties file.

    Note: Please note that in contrast with the Deployment Manager configuration, UDDI properties are not dynamically set during installation processing.

  2. If the UDDI Registry is already configured into a single appserver which is not part of a Deployment Manager cell (i.e. you are undertaking post installation configuration changes), then the uddi.properties file will be located in the properties subdirectory of the WebSphere Application Server in which you have installed the UDDI Registry application, that is <ApplicationServer-install-dir>/properties directory.

The properties that can be changed within uddi.properties are as follows:

  • The dbMaxResultCount, which is the limit on the number of rows of information that should be returned on Find requests, and will apply if the request does not specify a maxRows limit itself (or if it specifies a limit which exceeds this value). The initial value for this in uddi.properties is 100.

  • The persister, which indicates what database is to be used as the persistence store for the UDDI Registry database. If you have installed the UDDI Registry into an appserver within a Deployment Manager cell, then the persister property will have been set to the correct value for you. If you change this value, then also ensure that you have a UDDI Registry database created using the chosen database product (for more details about the UDDI Registry database, please refer to the section on "Installing the UDDI Registry"). You should also be aware that any data published to the UDDI Registry with one setting of the persister property will not be accessible when running the UDDI Registry application with a different setting for the persister property. The valid values for the persister property are:

    • persister=DB2

      indicating that DB2 is to be used as the persistence store

    • persister=Cloudscape

      indicating that Cloudscape is to be used as the persistence store

    The initial value for this in uddi.properties is Cloudscape.

    Note: This property is dynamically set by the setupuddi.jacl script when installing into a Deployment Manager cell so in this case not need to modify it.

  • The default language to be used on a publish request as the xml:lang when one is not specified. The initial value for this in uddi.properties is en-US. This property must contain one of the valid xml:lang values.

  • The UDDI site operator name. This is a string which is stored in every registry object, to indicate the operator of the UDDI Registry. The initial value for this in uddi.properties is www.mycompany.com/uddi . This property does not have any particular functional use, so its value can be set to any string that you feel is suitable.

  • The maximum number of search keys that can be used on find API requests. The initial value for this in uddi.properties is 5.

  • The getServletURLprefix and getServletname name, used to build up the discovery URL. The initial values for these are http://localhost:9080/uddisoap / and get . If you have installed the UDDI Registry into an application server within a Deployment Manager cell, then the getServletURLPrefix property will have been set for you using the value you specified as a parameter to the setup script. You are recommended to set suitable values for these properties before you first use the UDDI Registry.

    Note: This property is dynamically set by the setupuddi.jacl script when installing into a Deployment Manager cell so in this case not need to modify it.

Applying these changes to your system

In order for your changes to take effect, do one of the following:

  • If you are in the process of installing the UDDI Registry application for the first time, return to the original topic and complete the installation steps. Any changes you have made will be picked up during this subsequent processing.

  • If you have made post installation changes in a base Application Server only environment, stop and restart the UDDI Registry application using the WebSphere Administrative Console.

  • If you have made post installation changes in a Deployment Manager environment :

    1. Execute a Full Resynchronization for the node where the UDDI Registry executes. This can be done from the WebSphere Network Deployment Administrative Console under section Systems Administration ==> Nodes. Select your node, and then click the button for 'Full Resynchronization'.

      It is important that you do a 'Full Resynchronization' and not just a 'Synchronize'.

    2. Stop and restart the UDDI Registry application using the WebSphere Administrative Console

Configure the UDDI Registry

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.