Preparing to uninstall a cluster on Linux

Before uninstalling your cluster, you must prepare your system; for example, adding passwords to the properties files and keeping or discarding database information.

1. Optional: Make a backup of the WebSphere Portal configuration using the XML Configuration Interface.
   Important: The following information is not backed up and is deleted if you delete the database:

   • User attributes that are stored in the database and not in the user registry
   • Credential data that is stored in the default vault implementation
2. Complete the following steps to remove a node from the cell:
   Note: Removing a WebSphere Portal node from the cell does not affect the cluster definition you originally created for your cluster. The cluster definition remains intact even after removing all WebSphere Portal nodes from the cell. In addition, removing a WebSphere Portal node from the cell does not remove the product's enterprise applications from the deployment manager. The enterprise applications remain and continue to be associated with the cluster definition.
   1. Log on to the Deployment Manager WebSphere Integrated Solutions Console.
   2. Go Servers > WebSphere application server clusters > cluster_name > Cluster members, where cluster_name is the name of your cluster, click the server you want to stop, and then click Stop.
   3. Complete the following steps if you have a dynamic cluster:
      1. Go to System Administration > Node groups > node group name > Nodes > Node group members.
      2. Select the box for the node to be uninstalled and then click Remove.
      3. Save the changes to the master configuration repository.
      4. Synchronize the node to be uninstalled.
   4. Go to System Administration > Nodes, select the node containing the server you want to remove from the cell, and then click Remove Node to remove the node from the cell.
      Important: Make sure that you choose the Remove Node option to remove the node from cell and not the Delete option on the Cluster members view. Using the Delete option completely deletes the node, which removes the existence of the server from the deployment manager and does not leave a means for restoring the WebSphere Portal node to a stand-alone system. Using the Delete option can prevent the WebSphere Portal server from working after it is deleted from the cluster. If Remove Node does not successfully remove the node, click Force Delete to remove the node.
   5. Click Save to save the changes made to the cell's configuration.
   6. Repeat the previous steps for each node in the cluster and cell that needs to be uninstalled.
   7. Optional: Complete the following steps if you plan to convert the stand-alone server to a working portal:
      1. Use a text editor to open the wkplc.properties file.
      2. Change the value of the CellName property so that it matches the cell name of the node itself.
         • When you remove the node from the cell, the cell name for the node reverts to the cell name that was used before you federated the node.
         • The cell name can be identified by the wp_profile_root/config/cells/cell_name directory on the node, where cell_name indicates the cell to which the node belongs.
      3. Change the value of the ServerName property to the original WebSphere Portal server name.
      4. Ensure that the value of the PrimaryNode property is set to true.
      5. Save your changes.
3. Add passwords to the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files, located in the wp_profile_root/ConfigEngine/properties directory, or specify passwords on the command line.
4. Decide whether to keep your database as is to preserve WebSphere Portal information or complete the following steps to remove the information from the database:
   Note: If you choose to keep the database information, you cannot use it with subsequent installations although you can still access the information through your database software. Also, if you keep the information, you can always delete the WebSphere Portal databases and database tables later using your database software.
   1. Run the ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password from the wp_profile_root/bin directory.
   2. Run the ./stopServer.sh server1 -profileName cw_profile -username admin_userid -password admin_password from the AppServer_root/bin directory.
   3. Run the ./ConfigEngine.sh remove-schema -DWasPassword=password -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password task from the wp_profile_root/ConfigEngine directory to remove all database tables.
      Note: Some tables may remain in the IBM® Java Content Repository database. Removing the database will remove these tables.