-xs server option

Specifies server-side web services communications protocols.

Syntax 
{ dbeng11 | dbsrv11 } -xs { protocol,... } ...
protocol : { 
   NONE
 | HTTP [ ( option=value;...) ]
 | HTTPS [ ( option=value;...) ]
HTTPS-only options:
FIPS={ Y | N }
IDENTITY=server-identity-filename
IDENTITY_PASSWORD=password
Applies to

All operating systems and database servers.

Remarks

Use the -xs option to specify which web protocols you want to use to listen for requests.

If you do not specify the -xs option, the database server doesn't attempt to listen for web requests.

If you specify the -xs option with one or more protocols, the server attempts to listen for web requests using the specified protocol(s).

Note

If you want to start multiple web servers at the same time, then you must change the port for one of them since they both have the same default port.

You can use the HTTPS or the FIPS-approved HTTPS protocols for transport-layer security. See Encrypting SQL Anywhere web services.

Separately licensed component required

ECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations.

See Separately licensed components.

Regardless of which settings you specify with the -xs option, the server always listens for connection attempts using the shared memory protocol. You can specify any of the following:

  • option   For a list of supported option values for each protocol, see Network protocol options.

  • HTTP   Listen for web requests by the client using the HTTP protocol. The default port on which to listen is 80.

  • HTTPS   Listen for web requests by the client using the HTTPS protocol. The default port on which to listen is 443. You must specify the server's certificate and password to use HTTPS. The password must be an RSA certificate because HTTPS uses RSA encryption.

    The SQL Anywhere HTTP server supports HTTPS connections using SSL version 3.0 and TLS version 1.0.

    You can specify HTTPS, or HTTPS with FIPS=Y for FIPS-approved RSA encryption. FIPS-approved HTTPS uses a separate approved library, but is compatible with HTTPS.

    Note

    The Mozilla Firefox browser can connect when FIPS-approved HTTPS is used. However, the cipher suite used by FIPS-approved HTTPS is not supported by most versions of the Internet Explorer, Opera, or Safari browsers—if you are using FIPS-approved HTTPS, these browsers may not be able to connect.

    For information about enforcing the FIPS-approved algorithm, see -fips server option.

    • server-identity-filename   The path and file name of the server identity. For HTTPS, you must use an RSA certificate.

    • password   The password for the server private key. You specify this password when you create the server certificate.

  • NONE   Do not listen for web requests. This is the default.

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

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

-xs "HTTP(OPTION1=value1;OPTION2=value2;...)"
See also
Example

Listen for HTTP web requests on port 80:

dbeng11 web.db -xs HTTP(PORT=80)

Listen for web requests using HTTPS:

dbeng11 web.db -xs HTTPS(FIPS=N;PORT=82;IDENTITY=eccserver.id;IDENTITY_PASSWORD=test)
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1