-x server option

Specifies server side network communications protocols.

Syntax 1 
dbsrv11 -x { all | none | srv-protocols } ...

srv-protocols:
    { tcpip parmlist },...
parmlist:
    ( parm=value;...)
Syntax 2 
dbeng11 -x { all | none | eng-protocols } ...

eng-protocols:
    { tcpip [ parmlist ] },...
parmlist:
   ( parm=value;...)
Applies to

All operating systems and database servers.

Remarks

Use the -x option to specify which communications protocols, in addition to shared memory, you want to use to listen for client connection broadcasts.

If you do not specify the -x option, the server attempts to listen for client connection broadcasts using all protocols supported by the database server running on your operating system, including shared memory.

If you specify the -x option with one or more protocols, the server attempts to listen for client connection broadcasts using the specified protocol(s) and also using a shared memory protocol.

For information about securing shared memory connections on Unix, see Security tips.

Note

If you are running Windows Mobile and specify the -x option, the server only attempts to listen for client connection broadcasts using the TCP/IP protocol unless you explicitly request otherwise.

Regardless of which settings you choose for the -x option, the server always listens for connection broadcasts using the shared memory protocol. In addition to the shared memory protocol, you can also specify the following:

  • ALL   Listen for connection attempts by the client using all communications protocols that are supported by the server on this platform, including shared memory. This is the default.

  • NONE   Listen for connection attempts by the client using only the shared memory protocol.

  • TCPIP (TCP)   Listen for connection attempts by the client using the TCP/IP protocol. The TCP/IP protocol is supported by the network server on all operating systems, and by the personal database server for same-computer communications.By default, the database server listens for broadcasts on port 2638, and redirects them to the appropriate port. This ensures a connection in most cases.

    You can override this default and cause the server not to listen on port 2638 by setting the option -sb 0, or by turning off the BroadcastListener option (BroadcastListener=0). Additionally, if the client and server are communicating through a firewall, the client must send the packet to the exact port the server is listening on by specifying DoBroadcast=None and Host=.

See ServerPort protocol option [PORT].

For some protocols, additional parameters may be provided, in the format

-x tcpip(PARM1=value1;PARM2=value2;...)

For more information about available parameters, see Network protocol options.

For Unix, quotation marks are required if more than one parameter is supplied:

-x "tcpip(PARM1=value1;PARM2=value2;...)"
See also
Example

Allow only shared memory and TCP/IP communications:

-x tcpip
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1