Resolving a UDDI Registry Database Port Conflict

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

Modify the port used by the database hosting the UDDI registry schema by editing the Start script for the database and synchronizing the JUDDIServerCache connection cache configuration to use the same port.

Open <installation directory>\SC\bin\startUO51uddidb_asa.cmd (Windows) or <installation directory>/SC/bin/startUO51uddidb_asa.cmd (UNIX).
Note: If you do not see the startUO51uddidb_asa.cmd file in this directory, you should perform the preparatory tasks to set up the UDDI server. For current information, see the Data Integration Suite Release Bulletin.

Edit the following line:

START "Start UDDI db" "%ASA_HOME%\dbsrv9.exe" -n %DB_NAME% "%DB_LOC%\%DB_DATA%"

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)

Open the EAServer Manager by selecting Start > Programs > Sybase > Sybase Central.
Right-click the JUDDIServeCache node in the Connection Caches Properties dialog.
In the General tab, edit the Server Name and XA Server Name fields so the port number matches the port number in the startup script.
For example:
```
jdbc:sybase:Tds:localhost:543
```

For current information on setting up and using the UDDI server, see the Data Integration Suite Release Bulletin.