Resolving a UDDI Registry Database Port Conflict

Resolve a UDDI registry database port conflict by changing the port used by the database hosting the UDDI registry schema.

Prerequisites 

Stop the UDDI server.

Edit the Start script for the database and synchronizing the JUDDIServerCache connection cache configuration to use the same port.

  1. Open the command script:
    Table 1. Command scripts
    Platform Script
    Windows <installation directory>\DevRuntimes\SC\templates\startUO51uddidb_asa.cmd
    UNIX <installation directory>/DevRuntimes/SC/templates/startUO51uddidb_asa.sh
  2. Edit the following line: 
    START "Start UDDI db" "%ASA_HOME%\dbsrv9.exe" -n %DB_NAME% "%DB_LOC%\%DB_DATA%"
  3. Specify the desired port: 
    START "Start UDDI db" "%ASA_HOME%\dbsrv9.exe" 
-n %DB_NAME% "%DB_LOC%\%DB_DATA%" 
-x tcpip(ServerPort=5432;doBroadcast=no)
  4. Open EAServer Manager. Select Start > Programs > Sybase > Sybase Central.
  5. Right-click the JUDDIServeCache node in the Connection Caches Properties dialog.
  6. Select the General tab, and edit the Server Name and XA Server Name fields so the port number matches the one in the startup script. For example: jdbc:sybase:Tds:localhost:5432
The port number conflict for the UDDI Registry Database is resolved.
Next 

Start the UDDI server.

Related concepts
UDDI Registries
UDDI Server
UDDI Server Security Roles
Related tasks
Setting up the UDDI Server
Creating a UDDI Registry Connection Profile
Pinging a Server
Connecting to a Server
Refreshing a Server Connection
Disconnecting From a Server
Mapping UDDI Server Security Roles
Starting and Stopping the UDDI Server

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.