Hi Julie,
in case you haven't see the update on your idea CONDIRECT-I-317.
You can enable the secure connection to the database through ODBC itself.
- Open the ODBC Data Source Administrator
- Go to the System DSN tab and locate the Connect:Direct v6.3.0 Messages and Connect:Direct v6.3.0 TcqStats entries.
- Open each entry and configure the desired settings.
Note: These settings will not be carried over during an upgrade of Connect:Direct, or when you manually run the CD Database Wizard (DBWiz). In these cases, repeat the above steps again.
------------------------------
Volker Friedrich
------------------------------
Original Message:
Sent: Mon July 22, 2024 07:53 PM
From: Julie Miller
Subject: Connect:Direct for Windows 6.1: Using TLS to connect to MS-SQL DB
Fantasic, thanks John. Idea raised https://watsonsupplychain.ideas.ibm.com/ideas/CONDIRECT-I-317
------------------------------
Julie Miller
Original Message:
Sent: Mon July 22, 2024 08:22 AM
From: JOHN MASON
Subject: Connect:Direct for Windows 6.1: Using TLS to connect to MS-SQL DB
Hi Julie,
The Sterling Support agent was endeavouring to state that we do not provide technical support for the Microsoft ODBC driver and SQL Server, not that CD Windows doesn't support SQL Server (which it clearly does). Apologies for any misunderstanding here.
Unfortunately the DB Wizard database configuration tool doesn't provide the option to add any optional ODBC connection strings such as those required to encrypt the database connection. If you would like to see this feature added to a future release of the software, please open an enhancement request here. Your request will be reviewed by IBM Product Management will will respond to your via the website in due course.
Regards
------------------------------
JOHN MASON
Original Message:
Sent: Thu July 18, 2024 09:37 PM
From: Julie Miller
Subject: Connect:Direct for Windows 6.1: Using TLS to connect to MS-SQL DB
Hi All,
Our database team are expecting all database connections to be made using secure methods instead of TCP.
They've advised these involves connecting to a FQDN eg database.db.com and including the following parms:
encrypt=true;TrustServerCertificate=false;
Enforcing server side security isn't an option at this point because there are other application databases on the server.
IBM support have told me they don't support MS-SQL and what we want can't be done. Which seems odd to me because the doco is very plain in that we can use Postgres SQL DB or bring our own MS-SQL DB.
Just wondering if anyone out there knows how we might be able to configure the Connect:Direct connection to our MS-SQL please?
As it is, when I search for config files, I can't even find mention of the existing DB connection so I am completely befuddled by this product.
Cheers!
------------------------------
Julie Miller
------------------------------