Communication Link

Using the -x [comlink1,comlink2] parameter, you can configure the communication link for the protocol that the server should use to communicate with the clients. Instead of the [comlink1,comlink2] above you enter ALL, DDE, NamedPipes, IPX, NetBIOS, or TCPIP, or a combination of these separated with comma signs. The standard is ALL (that is, all protocols) unless a specific communication link has been entered. The choice of network protocol affects the performance of your system.

When the "monwin" database server service has been installed by the MONITOR installation program, it will be configured with -x ShMem,TCPIP.

In certain cases you might want or need another database server service on the database server (the computer), for example to divide the management of many company databases. You can then enter that service manually and name its database server "monwin2" or another suitable name (this is done using the -n monwin2 parameter). In that case you also need to specify a specific port in the communication link in the new service. The standard TCP/IP port used by Sybase SQL Anywhere is port 2638, unless another port has been specified. To enter a unique port you should enter -x ShMem,TCPIP(PORT=[port]). For example, if port 49152 should be used you should enter -x ShMem,TCPIP(port=49152).

The Communication Link in Monitor.ini

In the Monitor.ini file it says CommLinks=ShMem,TCPIP{HOST=[SERVERNAME]} on the Connectstring row under the [Database] section. Instead of [SERVERNAME] you will see the computer name of the database server.

If you want to use another port it should say CommLinks=ShMem,TCPIP{HOST=[SERVERNAME];PORT=[port]} instead.

Here you can also initiate additional communication links separated with commas, such as CommLinks=ShMem,IPX,TCPIP. The communication links entered here will then collectively be initiated for all company databases that there are rows for under the section [Company].

It is also possible to enter a communication link for a separate company database under the section [Company]. The parameter CommLinks=[comlink1,comlink2] should then be added on the row for that company database.

Read more about communication links in Monitor.ini in the section Configuration Files in MONITOR.

However, you should avoid initiating additional communication links in Sybase Central or Monitor.ini, if you are using more than one protocol in your network. This will only make the system slower during connection, since there are several communication links that must be initiated between the database server and client each time.

Communication Link in Client

A separate client can use another communication link or other parameters in the communication link by adding an own communication link. It will then override the one entered in the Monitor.ini. The communication link is added in the register in Windows on the client computer it concerns.

1. You start the Registry Editor on that computer by searching for regedit.exe on the Start menu.
2. In the Registry Editor you then go to HKEY_LOCAL_MACHINE\SOFTWARE\Monitor Industriutveckling AB\Monitor (in a 32-bit Windows) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Monitor Industriutveckling AB\Monitor (in a 64-bit Windows).
3. There you should enter the string value Connectstring with the CommLinks=[comlink] value. For example, if IPX should be used you should enter CommLinks=IPX. In this string value you can enter the corresponding parameters in the same way as they are entered in Monitor.ini.

In the example the computer is using the IPX protocol in the communication link. This will then apply for the connection to all company databases in MONITOR from that client computer. You cannot enter specific communication links for individual company databases here.

of