protocolThe protocol to use. It can be https or tls. The tls protocol is TCP/IP with TLS.

cipherThe cipher to use. It can be rsa or ecc for RSA and ECC encryption, respectively. The cipher must match the encryption used to create your identity.

fips Indicates whether to use FIPS. FIPS can only be used with RSA encryption. RSA FIPS uses separate FIPS 140-2 certified software
from Certicom. Servers using FIPS are compatible with clients not using FIPS and vice versa. RSA FIPS can be used for SQL
Anywhere clients on any supported 32-bit Windows platform or Solaris, or for UltraLite clients on Unix or any supported 32-bit
Windows platform including Windows Mobile.

identity-fileThe path and file name of the identity file, which contains the server's private key, the server's certificate, and, optionally,
the certificates signed by the Certificate Authority.

For information about creating the server certificate, which can be self-signed, or signed by a Certificate Authority or enterprise
root certificate, see Creating digital certificates.

passwordThe password for the server private key. You specify this password when you create the server identity.