ODBC Configuration Dialog Help
The Network tab of the ODBC Configuration dialog has the following components:
TCP/IP If you want to use ECC_TLS (formerly Certicom) or RSA_TLS strong encryption for network packets, you must select the TCP/IP protocol to access the network database server. In the adjacent field, you may enter communication parameters that establish and tune the connection from your client application to a database.
For example, to look on the machine server1 on port 4436 for a database server, you would enter HOST=server1;PORT=4436.
Contact your network administrator if you are unsure which protocol to use.
SPX You can select the SPX protocol to connect to databases on Novell NetWare networks. NetWare also supports the TCP/IP protocol. In the adjacent field, you may type communication parameters that establish and tune the connection from your client application to a database.
For example, you could enter the following communication parameters for an SPX connection HOST=0:0:0:0:0:1/4:236:121:215;PORT=2369.
Contact your network administrator if you are unsure which protocol to use.
Named pipes The Named Pipes protocol is used for client/server communication on the same machine. If you want to run under a certified security environment, you can use the named pipes protocol. It is only provided on Windows NT.
Contact your network administrator if you are unsure which protocol to use.
Shared memory The shared memory protocol is used for communication between a client and server running under the same operating system on the same machine.
Contact your network administrator if you are unsure which protocol to use.
For more information, see CommLinks connection parameter [LINKS], and Network protocol options.
Liveness timeout
A liveness packet is sent across a client/server to confirm that a connection is intact. If the client runs for the liveness timeout period without detecting a liveness packet, the communication is severed. This parameter only works with network server and TCP/IP or IPX communication protocols.
The default liveness timeout is 120 seconds.
For more information, see LivenessTimeout connection parameter [LTO].
Idle timeout
Set the amount of client idle time before the connection is terminated. If a client runs for the idle timeout period without submitting a request, the connection is severed.
The default client idle time is 240 minutes.
For more information, see Idle connection parameter [IDLE].
Buffer size
Set the maximum size of communication packets, in bytes. You should set the buffer size to be smaller than that allowed by your network because the network software may add information to each buffer before sending it over the network.
The default buffer size is 1460 bytes.
For more information, see CommBufferSize connection parameter [CBSIZE].
Compress network packets Select this option to turn on compression for the connection. Using compression for a connection can significantly improve Adaptive Server Anywhere performance under some circumstances.
For more information, see Compress connection parameter [COMP].
Select the method for encryption of network packets
Allows the encryption of packets transmitted from the client machine over the network.
Separately licensable option requiredTransport-layer security requires that you obtain the separately-licensable SQL Anywhere Studio security option and is subject to export regulations.To order this component, see Separately-licensable components. |
None Communication packets transmitted from the client are not encrypted. This is the default setting.
Simple Communication packets transmitted from the client are encrypted with Simple encryption. Simple encryption is supported on all platforms, as well as on previous versions of Adaptive Server Anywhere. Simple encryption is not as strong as ECC_TLS or RSA_TLS encryption.
ECC_TLS Select this option to enable ECC_TLS (formerly Certicom) encryption. ECC_TLS encryption protects the confidentiality and integrity of network packets as they pass between the client and the server. It is only available over the TCP/IP protocol.
In the adjacent field you must supply a trusted certificate value. You can also click Edit to supply this value.
RSA_TLS Select this option to enable RSA_TLS encryption. RSA_TLS encryption protects the confidentiality and integrity of network packets as they pass between the client and the server. It is only available over the TCP/IP protocol.
In the adjacent field you must supply a trusted certificate value. You can also click Edit to supply this value.
RSA_TLS_FIPS Select this option to enable RSA_TLS_FIPS encryption. When this option is selected, the database server accepts communication packets encrypted using FIPS-approved RSA encryption technology. RSA_TLS_FIPS uses a separate approved library than RSA_TLS, but is compatible with clients specifying RSA_TLS with Adaptive Server Anywhere 9.0.2 or later. To use this type of encryption, both the client and the server must be operating on a supported 32-bit Windows operating system, and the connection must be over the TCP/IP port.
In the adjacent field you must supply a trusted certificate value. You can also click Edit to supply this value.
Edit Click Edit to supply encryption values for trusted certificates, certificate company, certificate unit, and certificate name in the Certicom Encryption Options dialog.
For more information, see Encryption connection parameter [ENC] and FIPS 140-2 certification.
SQL Anywhere Studio 9.0.2
Copyright © 1989–2004 Sybase, Inc. Portions copyright © 2001–2004 iAnywhere Solutions, Inc. All rights reserved.