Loading...

XML

Word

Printable

Story Points:
2
Affects:

Release Notes
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Text:

Hide
Cause: ODBC transport was not properly configured in the standalone-openshift.xml
Consequence: It was not possible to securely connect to the ODBC transport
Fix: Both odbc and secure-odbc transports are now configured in standalone-openshift.xml when the ssl keystore is provided
Result: It is now possible to connect to the JDV container with secured ODBC protocol

Show
Cause: ODBC transport was not properly configured in the standalone-openshift.xml Consequence: It was not possible to securely connect to the ODBC transport Fix: Both odbc and secure-odbc transports are now configured in standalone-openshift.xml when the ssl keystore is provided Result: It is now possible to connect to the JDV container with secured ODBC protocol
Target Release:

JDV63 1.3.0.GA
Git Pull Request:
https://github.com/jboss-openshift/cct_module/pull/20, https://github.com/jboss-openshift/application-templates/pull/319

Need ODBC secure socket binding setting injected into the datavirt openshift templates.

relates to

CLOUD-2152 [tracker] Sprint 12 release