AIX: Preparing to uninstall

We must prepare the system before you uninstall the IBM WebSphere Portal environment. For example, add passwords to the properties files. We must also decide to keep or discard the database information.

cluster note: We must issue the removeNode command to unfederate a node before uninstalling because WebSphere Portal cannot uninstall a federated node.

1. Optional: Make a backup of the WebSphere Portal configuration. Use the XML Configuration Interface.

   If we delete the database, the following information is not backed up and is deleted:

   • User attributes stored in the database and not in the user registry

   • Credential data stored in the default vault implementation

2. To remove a node from the cell in a clustered environment:

   Remove a WebSphere Portal node from the cell does not affect the cluster definition that you originally created for the cluster. The cluster definition remains intact even after you remove 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 dmgr console.

   2. Go to...
      Servers | WebSphere application server clusters | cluster_name | Cluster members | server | Stop

   3. Complete the following steps on the 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 to remove from the cell, and then click Remove Node to remove the node from the cell.

      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. The Delete option completely deletes the node, which removes the existence of the server from the deployment manager. 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 to the cell's configuration.

   6. Repeat the previous steps for each node in the cluster and cell to uninstall.

   7. Optional: Complete the following steps if you plan to convert the stand-alone server to a working portal:

      1. Edit wkplc.properties file.

      2. Set the value of the CellName property so that it matches the cell name of the node itself.

         • 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/config/cells/cell directory on the node, where cell indicates the cell to which the node belongs.

      3. Set the value of the ServerName property to the original WebSphere Portal server name.

      4. Verify the value of the PrimaryNode property is set to true.

      5. Save the changes.

3. Add passwords to the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files in WP_PROFILE/ConfigEngine/properties. We can also specify passwords on the command line.

4. Decide whether to keep the database to preserve WebSphere Portal information.

   • If we keep the database, no further steps are required.

     If we choose to keep the database information, we cannot use it with subsequent installations although we can still access the information through the database software. Also, if you keep the information, we can always delete the WebSphere Portal databases and database tables later with the database software.

   • To remove the information from the database:

     1. Stop all the servers.

     2. Open a command prompt and change to the WP_PROFILE/ConfigEngine.

     3. Run the ./ConfigEngine.sh remove-schema -DWasPassword=foo -Drelease.DbPassword=foo -Dcustomization.DbPassword=foo -Dcommunity.DbPassword=foo -Djcr.DbPassword=foo -Dfeedback.DbPassword=foo -Dlikeminds.DbPassword=foo task.

     Some tables remain in the IBM Java Content Repository database. Removing the database removes these tables.

Parent AIX: Uninstalling WebSphere Portal