Connectivity protocols
The connectivity protocols that you can use to connect client products to the database server depend on the operating system.
The following table uses these abbreviations for protocol names:
- BSTP - Berkeley sockets using TCP/IP
- IPSP - IPC using stream pipe
- IPSM - IPC using shared memory
- IPNM - IPC using a named pipe
- MAXC - MaxConnect
- SSL - Secure Sockets Layer
- TLTP - TLI using TCP/IP
- TLIX - TLI using IPX/SPX
| Platform/OS | BSTP | IPSP | IPSM | IPNM | TLTP | MAXC | SSL |
|---|---|---|---|---|---|---|---|
| AIX | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| HP Itanium 64 | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| HPUX | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux 32-bit | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux AMD 64 | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux POWER (Big Endian) | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux POWER (Little Endian) | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux IBM System z | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Linux ARM | onsoctcp drsoctcp |
onipcstr | onipcshm | drsocssl
onsocssl |
|||
| Mac OS X | onsoctcp drsoctcp |
onipcstr | onipcshm | onsocimc | drsocssl
onsocssl |
||
| Solaris | onsoctcp drsoctcp |
onipcstr | onipcshm | ontlitcp | ontliimc | drsocssl
onsocssl |
|
| Windows | onsoctcp drsoctcp |
onipcnmp | drsocssl
onsocssl |
Notes:
- If you are using 64-bit servers: Remote 32-bit applications/tools (example: ESQL/C) can only connect to HCL Informix® using the TCP/IP protocol. Local 32-bit applications/tools can connect to the 64-bit server using either TCP/IP protocols or IPC stream pipe protocols. Local 32-bit applications/tools cannot connect to the 64-bit server using IPC shared memory protocol.
- If you are using a NUMA system and have several IP addresses configured on the same physical interface: The HCL Informix TCP listener thread binds to a particular IP address/port. It listens for incoming calls addressed to only one IP address. If there are multiple IP addresses configured on the system, a TLI client is not able to connect to the server. (If DNS is configured to resolve the host name on a rotary of the four IP addresses, you do not know which of those addresses has been selected by the HCL Informix TCP listener). The solution is that in the $INFORMIXDIR/etc/sqlhosts file, use "*hostname" instead of "hostname". It will make the HCL Informix TCP listener bind to INADDR_ANY instead of a particular address.
- For additional information, see the Informix machine notes.