Informix

Pardon the n00b-ish question, but I'm [thankfully] mostly Java and JDBC illiterate. Traditionally, we've connected to JDBC data sources by using something like the following:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr

This works for 'onsoctcp' services. For 'onsocssl' services, we must do this:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr;SSLCONNECTION=true

Recently, we've started switching to using sqlhosts instead of hard-coding the host/port into the URL. That looks something like this:

jdbc:informix-sqli:/mydb:INFORMIXSERVER=my_ifxsvr;SQLH_TYPE=file;SQL_FILE=/path/to/sqlhosts

What I'm curious about is whether the SSLCONNECTION=true is necessary, since the protocol is specified in sqlhosts. If it is, that's problematic, as we still have a mix of onsoctcp and onsocssl. If so, that's problematic, because I'd ideally like to make the connections as simple as specifying the INFORMIXSERVER and database name; requiring users and apps to conditionally specify SSLCONNECTION undermines the simplicity of the approach, and forces them to once again update connection strings as we transition legacy onsoctcp listeners to onsocssl.

Thanks in advance for any insight.

Pardon the n00b-ish question, but I'm [thankfully] mostly Java and JDBC illiterate. Traditionally, we've connected to JDBC data sources by using something like the following:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr

This works for 'onsoctcp' services. For 'onsocssl' services, we must do this:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr;SSLCONNECTION=true

Recently, we've started switching to using sqlhosts instead of hard-coding the host/port into the URL. That looks something like this:

jdbc:informix-sqli:/mydb:INFORMIXSERVER=my_ifxsvr;SQLH_TYPE=file;SQL_FILE=/path/to/sqlhosts

What I'm curious about is whether the SSLCONNECTION=true is necessary, since the protocol is specified in sqlhosts. If it is, that's problematic, as we still have a mix of onsoctcp and onsocssl. If so, that's problematic, because I'd ideally like to make the connections as simple as specifying the INFORMIXSERVER and database name; requiring users and apps to conditionally specify SSLCONNECTION undermines the simplicity of the approach, and forces them to once again update connection strings as we transition legacy onsoctcp listeners to onsocssl.

Thanks in advance for any insight.

Pardon the n00b-ish question, but I'm [thankfully] mostly Java and JDBC illiterate. Traditionally, we've connected to JDBC data sources by using something like the following:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr

This works for 'onsoctcp' services. For 'onsocssl' services, we must do this:

jdbc:informix-sqli://myhost.mydomain.com:9288/mydb:INFORMIXSERVER=my_ifxsvr;SSLCONNECTION=true

Recently, we've started switching to using sqlhosts instead of hard-coding the host/port into the URL. That looks something like this:

jdbc:informix-sqli:/mydb:INFORMIXSERVER=my_ifxsvr;SQLH_TYPE=file;SQL_FILE=/path/to/sqlhosts

What I'm curious about is whether the SSLCONNECTION=true is necessary, since the protocol is specified in sqlhosts. If it is, that's problematic, as we still have a mix of onsoctcp and onsocssl. If so, that's problematic, because I'd ideally like to make the connections as simple as specifying the INFORMIXSERVER and database name; requiring users and apps to conditionally specify SSLCONNECTION undermines the simplicity of the approach, and forces them to once again update connection strings as we transition legacy onsoctcp listeners to onsocssl.

Thanks in advance for any insight.