Prepare to uninstall a cluster on IBM i

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

To prepare for uninstallation:

You must issue the removeNode command to unfederate a node prior to uninstalling because WebSphere Portal cannot uninstall a federated node.

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

    The following information is not backed up and will be 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. To remove a node from the cell:

      Remove a WebSphere Portal node from the cell does not affect the cluster definition you originally created for 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 dmgr. The enterprise applications remain and continue to be associated with the cluster definition.

      1. Log in to the Deployment Manager administrative console.

      2. Click Servers -> Clusters -> cluster_name -> Cluster members, where cluster_name is the name of cluster, click the server you want to stop, and then click Stop.

      3. If you have a dynamic cluster:

        1. Navigate 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. Click 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.

        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 dmgr 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.

  3. Click Save to save the changes made to the cell's configuration.

  4. Repeat the above steps for each node in the cluster and cell that needs to be uninstalled.

  5. Optional. If you plan to convert the stand-alone server to a working portal:

    1. Edit 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/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 changes.

  • Decide whether to keep database as is to preserve WebSphere Portal information or perform the following steps to remove the information from the database:

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

      1. Run the stopServer WebSphere_Portal -username admin_userid -password foo from the WP_PROFILE/bin directory.

      2. Choose one of the following options to delete the database information:

        Options to delete the database information.

        If database is a... Then perform the following steps:
        Local IBM DB2 for i 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=foofrom the WP_PROFILE/ConfigEngine to remove all database tables.
        Remote IBM DB2 for i

        1. Use a 5250 PC session to log on to the system where the remote database exists.

        2. Type wrklib prefix* on the command line to display a list of all libraries created for the remote database, where prefix is the prefix for database name.

        3. Type 4 in the Opt field beside each library name that you want to delete and then press Enter.


    Parent

    Uninstall from a cluster on IBM i


    Next topic

    Uninstall a cluster on IBM i


    Related tasks

    removeNode command

      Updated step 2gii. Defect PM50102.


    +

    Search Tips   |   Advanced Search