Important hotfix for Insight 1.0.1.1 and CLM 3.0.1.x
If you are using CLM 3.0.1.x with Rational Insight 1.0.1.1 then you must
install this hotfix. In fact, without it your ETLs will stop functioning with the upcoming CLM 3.0.1.2 and Tomcat due to a protocol change. It also fixes two other import issues: (1) Without the hotfix, errors that happen during REST calls are not propagated from the XDC driver to the Data Manager. You miss that something went wrong and your Data Manager logs only show a success message. In the past you had to review the entire ri_jdbc.log file for errors. With the hotfix errors are no properly reported in the DM log files. (2) There was a big confusion about the XDC Editor reporting a warning when using the Test Connection button. The connection would indeed succeed with the xdc files downloaded from the CLM servers, but many people would interpret the warning telling the user that a resource was not found as an error and started changing the authentication settings, which would break the ETLs completely. This hotfix revised the warning messages and provides an additional field for a resource path to properly test the connection. For example, add /testcase for the rqm xdc file or /rpt/repository/workitem for the workitem xdc to run the test now checking an actual resource. Get the hotfix here: ftp://ftp.software.ibm.com/software/rational/private/RAT5-1lDLVRNkbxY5/ If you are using RRDI, no action is needed. Hope this helps, Peter Haumer. |
One answer
Hello.
There is now also an official support page available for this hotfix: http://www-01.ibm.com/support/docview.wss?uid=swg24031827 On 1/10/2012 10:38 AM, jmw2 wrote: Was this hotfix reported or documented anywhere that we could have |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Was this hotfix reported or documented anywhere that we could have proactively applied it rather than having to find it after the fact when we already ran into these issues/errors? Is there any place to subscribe to notifications to be included on updates like this?