DC RUM 2017 Console
RUM Console can’t connect to AMD after upgrade
We updated the AMD but it appears that RUM Console can’t connect to it. We noticed this error message in the rtmgate.log on AMD:
W HTTP 18-07-19 19:30:30.096 An attempt was made to authenticate the locked user "compuware"
On a newly installed 2017 AMD, the credentials for the RUM Console to connect have changed to adlex/vantage and the compuware/vantage credentials are deprecated.
After upgrading to 2017 the CSS service is still running. Is it safe to uninstall CSS?
User management is now integrated with RUM Console in 2017 release. During upgrade to 2017 release users are migrated from CSS component to RUM Console. If this process was successful it is safe to uninstall the CSS component now. We recommend first to disable the service, make sure users can log in to CAS and RUM console and then uninstall the old CSS service.
DC RUM 2017 CAS
Compatibility issue between SP3 and pre-SP3 versions for intra-CAS-Cluster communication
2017 May, SP1, SP2 and SP3
There is compatibility issue between SP3 and pre-SP3 versions of internal library (hazelcast) used for intra-CAS-Cluster communication. In order to avoid any issues when applying SP3 (on any < SP3 version) please take one of the two recommendations.
- apply SP3 at athe same time to all your CASes and ADSes, including Failovers, or
- if you cannot do then above, apply the hazelcast-all-3.1.9.jar patch on less then SP3 version PRIOR starting applying SP3 anywhere.
If you do not apply any of above two recommendations you will find your CASes not starting with the following entries in the server.log:
E FARM 18-01-12 13:34:55.635 com.hazelcast.nio.serialization. HazelcastSerializationException: Problem while reading DataSerializable, namespace: 0, id: 0, class: com.hazelcast.partition.CheckReplicaVersion
New version of hazelcast library
2017 May SP3 (and newer) release comes with a new version of hazelcast library. This library is used by cluster node servers (CAS and ADS) to communicate with each other. The new hazelcast libary is of version 3.1.9 in SP5 which is incompatible with hazelcast 3.1.4 included in SP2 and earlier versions of 2017 release.
Therefore, it is required to install SP5 on all cluster node servers (master + slave servers) during the same maintenance window (all or none) as if some nodes stay on SP2 (or earlier versions of 2017) they will not be able to communicate with other nodes that are already on SP5 in the same cluster.