We have connection profiles for DB2/OS that have "Additional Connection Properties" set.
We have seen that a couple days after creation when it is used the text on this field is changing case on the profile.
Value when connection profile created: securityMechanism=7;encryptionAlgorithm=2
Days later when the Connection profile is used the value is now: securitymechanism=7;encryptionalgorithm=2
Because the value has changed, the connection profile will fail when used in a Publish.
So when we do a Publish with that Connection Profile, when it fails, we have to manually edit the "Additional Connection Properties" and re-publish as a workaround.
And also noticed, that even though the Schema Name is defined in the connection profile, when used in a generator, why do we have to select the Schema again? Should it not pick up the Schema define in the Connection Profile? Why do we have to select it again?
Release : 4.9.1
Component : TDM Web Portal
Open a support case and refer to defect DE532655.