As part of TLS 1.2 set-up, (https://www.ibm.com/support/pages/connection-sql-server-fails-when-server-configured-use-tls-12-or-connecting-sql-server-2016), JVM arguments need to be added. Post these changes, the Cognos Configuration tool should be started using the cogconfig.bat file, and not using the cogconfigw.exe file. When users launch the Cognos Configuration UI, it throws a database exception error, which in reality is not an error. When the bat file is run, Cognos Configuration launches just fine. However, this is confusing to the admins and may result in support tickets as the exception error is misleading.
So, it would be better if the JVM argument changes are to the Config tool itself.
Why is it useful?
|Who would benefit from this IDEA?||Customers who would upgrade to TLS 1.2 in Analytics servers|
How should it work?
|Priority Justification||Reason for ranking this as a medium priority is because a lot of customers will upgrade to TLS 1.2 protocol, and the subsequent launch of Cognos Config tool with the error could be misleading otherwise.|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions