PDI keeping databases configuration in two places .ktr and .kdb files
Juan Sierra Pons
This email is related to this thread Problems upgrading MSSQL's JDBC to 11.2 and how to set properly encrypt=false in the JDBC URL
I want to upgrade MSSQL JDBC to the latest version 11.2 but since 10.2 there is a breaking change:
Release notes - JDBC Driver for SQL Server
| Default encrypt to true | BREAKING CHANGE TLS encryption is enabled by default. |
So I cannot just replace the old JDBC with the latest one as the connection are going to fail for old servers that do not support encryption.
This can be solved by adding "encrypt=false" to the connection Options. The problem I see here is that PDI keeps the info in two places: in the .kdb files and in the .ktr files.
When the .kdb is updated the following is added in the .kdb file
<attributes>
<attribute><code>EXTRA_OPTION_MSSQLNATIVE.encrypt</code><attribute>false</attribute></attribute>
[...]
</attributes>
And if I open the database related step in the .ktr it updates it automatically by adding this:
<attributes>
<attribute>
<code>EXTRA_OPTION_MSSQLNATIVE.encrypt</code>
<attribute>false</attribute>
</attribute>
<attribute>
Changing the .kdb is easy, the problem I see here is that in order to update the .ktr files I have to open all of them, open the related step and saving it ( a very time consuming, prone to error task). There is a XML replace option but it can be dangerous.
Has anyone faced a similar challenge?
Is it enough to just update the .kdb files? I mean .kdb will be default value and the options in the .ktr will be like specific values for it.
Thanks for your time
Best regards
----------------------------------
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
--------------------------------------------------------------------------------------