Changing Database Ports for SQLAnywhere Databases

By default, ports are configured when you install the data tier. You can change values for any SQLAnywhere database deployed as part of the data tier.

During installation you are prompted to enter a port number for each of the SQLAnywhere databases used by the runtime: the cache database (CDB), the cluster database, the log and monitor database (which share the same port).

Depending on whether or not you have deployed SAP Mobile Platform as a single node (as in the case of Online Data Proxy environments), or as a cluster, the process varies slightly. This is because:

In single node deployment, a single database server named CacheDB supports all installed databases.
In a cluster deployment, two servers are used: the monitor and domain log databases use a server called LogDataDB, the default database used for the cache data uses the CacheDB server, and the cluster database uses the ClusterDB server.

Stop all instances of SAP Mobile Server, as well as all database services.
For a list of database services, search for SAP Mobile Platform Windows Services in System Administration.
If you are updating ports in a cluster deployment, then for each database that requires a port change, open the corresponding initialization file and modify the tcpip(PORT=newPort) entry. These files are installed to SMP_HOME\Servers\SQLAnywhere16\binxx:
- For the cache database, open cdboptions.ini.
- For the cluster database, open cldboptions.ini.
- For the log database, open monitoroptions.ini.
For all deployments, run the update properties utility to propagate changes to all runtime servers:
```
updateProps.bat -u user -p pwd -d dsn -nv "serverport_property1=newport#serverport_property2=newport
```
Supported server port property names include:
- cdb.serverport
- cldb.serverport
- monitoringdb.serverport
- domainlogdb.serverport
For details on the update properties utility, see Update Properties (updateprops.bat) Utility in the System Administration guide.
Restart the cluster database.
Restart all SAP Mobile Servers.