Remove a node from an existing cluster

Products

• CA Process Automation Base

Issue/Introduction

The following instructions describe how to remove an existing node from a PAM cluster. 

Removal is a manual process, which requires access to the backend PAM database.  As this procedure is highly involved, it is recommended to take full backups and snapshots of the given environment as well as test on a non-production instance.

Environment

ITPAM 4.3.x and 4.4

Resolution

1. Stop all the running nodes of the ITPAM cluster

2. Connect to the runtime database and delete the entries of the unwanted node from the properties table

   delete from dbo.properties

3. Connect to the repository database and delete the entries related of the unwanted node from the ServerCnfgProperties table.

   select * from dbo.ServerCnfgProperties

4. Copy the value of "nodeID" column for the node that needs to be removed.

   Execute below query:

   delete from ServerCnfgProperties where nodeID="[paste the copied value from the above query]"

   This removes the entry in PAM UI in the "Configuration Properties" section under "Configuration" tab

5.  Connect to the repository database and update the ClusterNodeProperties column in dbo.Orchestrator table   

   Execute the query in Repository database:

   select * from dbo.Orchestrator

   Copy the content from ClusterNodeProperties Column

    

6. Copy the xml content and remove the entry of unwanted node under  <ClusterNodeProperties> </ClusterNodeProperties> tag and update the column value by running the below query.

   update dbo.Orchestrator set ClusterNodeProperties='[Updated_XML_Value_After_removing_unwanted_node_under_ClusterNodeProperties_tag]'

7. Delete unwanted node details from Domain.xml file located in the <Install_Location>/wildfly/standalone/.config/Domain.xml file

   Remove the entry of unwanted node under <ClusterNodeProperties> </ClusterNodeProperties> tag and save the Domain.xml file

8.  Repeat step #6 for all nodes of the cluster.

9. Restart all the nodes of the cluster.

Additional Information

If there are plans to perform this procedure in a production instance, it is strongly advised to create a support case to go over the procedure thoroughly, even if you have practised in a non-production instance of PAM