If you want to use SQL Anywhere as an Open Server, you must ensure that you start it using the TCP/IP protocol. By default, the server starts all available communications protocols, but you can limit the protocols started by listing them explicitly in the command. For example, the following commands are both valid:
dbsrv10 -x tcpip,spx c:\mydata.db dbsrv10 -x tcpip -n myserver c:\mydata.db
The first command uses both TCP/IP and SPX protocols, of which TCP/IP is available for use by Open Client applications. The second line uses only TCP/IP.
You can use the personal database server as an Open Server for communications on the same computer because it supports the TCP/IP protocol.
The server can serve other applications through the TCP/IP protocol or other protocols using the SQL Anywhere-specific application protocol at the same time as serving Open Client applications over TDS.
Every application using TCP/IP on a computer uses a distinct TCP/IP port so that network packets end up at the right application. The default port for SQL Anywhere is port 2638. It is recommended that you use the default port number as SQL Anywhere has been granted that port number by the Internet Assigned Numbers Authority (IANA). If you want to use a different port number, you can specify which one using the ServerPort (PORT) protocol option:
dbsrv10 -x tcpip(ServerPort=2629) -n myserver c:\mydata.db
You may also need to supply an EngineName if more than one local database server is running, or if you want to connect to a network server.
To connect to this server, the interfaces file at the client computer must contain an entry specifying the computer name on which the database server is running, and the TCP/IP port it uses.
For information about setting up the client computer, see Configuring Open Servers.