Are there any clustered applications-specific steps to be performed to complete the migration to SR1 release?
An ELM 7.0.2 iFix014 or earlier was migrated to ELM 7.0.2 SR1 (iFix015) or 7.0.1 iFix017 or earlier was migrated to 7.0.1 SR1 (iFix018) to mitigate vulnerabilities with log4j 2.16 and earlier. The migration was performed by using the side-by-side installation, migration instructions per https://www.ibm.com/support/pages/node/6588059
1. Stop all Nodes of EWM and ETM application clusters and stop DCM
2. Migrate one Node of each application cluster to SR1 by following the instructions from the technote
3. Replicate the Nodes as instructed in the Interactive Installation Guide
IV. Replicate Change and Configuration Management to all nodes
You can replicate the CCM application on all nodes in two ways. You can install the CCM application on all other nodes and copy only the teamserver.properties and server.startup files from the first node to the other nodes. Alternatively, you can copy the entire installation directory from the first node to the other nodes. Do not forget to change the node IDs in the server.startup file on all nodes so that they all have unique IDs.
4. Replicate node-specific identifiers and keystore from previous nodes:
On each application Node machine
i. Node identifier is mentioned as value to the JAVA OPTION -Dcom.ibm.team.repository.cluster.nodeId in server.startup file. Copy the option and its value from server.startup of the older version node installation to its newer SR1 replica.
ii. Copy the keystore from older version installation for the node to its newer SR1 replica
5. Migrate Distributed Cache Microservice (DCM):
i. Copy from C:\IBM\ELM702\server\clustering\cache to C:\IBM\ELM702_SR1\server\clustering\cache
1) distributedCache.cfg
2) distributedCache.start.bat
3) distributedCache.stop.bat
4) client_keystore.jks (if you have a custom keystore, copy that over.
Refer to the section "[REST-SslContextFactory]" in distributedCache.cfg for the keystore in use.
ii. Copy from C:\IBM\ELM702\server\clustering\ to C:\IBM\ELM702_SR1\server\clustering\
1) addNodeReg.bat
2) addNodeReg.ps1
3) JASConfig.params
If DCM runs outside of JTS(default location), copy the latest DCM from JTS SR1 installation (<SR1 Installation>\server\clustering directory) to the nondefault location you want it to run from and perform the steps in this document.
6. Start DCM and then Start the Nodes, verify whether cluster works fine.
Note: Make sure to stop all old nodes, old registered services and register and use newer services and nodes.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUC3U","label":"IBM Engineering Workflow Management"},"ARM Category":[{"code":"a8m3p000000Go6kAAC","label":"Clustering"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUVV6","label":"IBM Engineering Test Management"},"ARM Category":[{"code":"a8m3p000000Go6kAAC","label":"Clustering"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]