+

Search Tips   |   Advanced Search

Uninstall a deployment before migration

Uninstall a deployment of Connections before migrating to a later version.

If we are installing IBM Connections 4.5 side-by-side with the current deployment, you do not need to complete this task. However, if we are installing 4.5 on the same systems as 4.0, IBM recommends that you uninstall the 4.0 deployment. We can migrate the 4.0 data to 4.5. See Migrate to IBM Connections 4.5 topic.

Back up your current deployment. See Back up IBM Connections DBS and file systems topic.

To uninstall Connections:

  1. Start the IBM WebSphere Application Server Deployment Manager.

  2. Stop all instances of WAS, including node agents, in the deployment.

  3. To uninstall a deployment of Connections, start the Installation Manager and then click Uninstall.

  4. Select the Connections package group and click Next.

  5. Click Uninstall to begin uninstalling.

  6. When the process is complete, restart the dmgr.

  7. Restart all instances of WAS, including node agents.

  8. Synchronize the nodes.

  9. To check the details of the procedure, open the log files in the connections_root/logs directory. Each Connections application that you uninstalled has a log file that uses the following naming format: application_nameUninstall.log, where application_name is the name of a Connections application.

  10. If we plan to install Connections 4.5 on the same server as the 4.0 deployment, remove the following files:

    • Except where noted, remove these files from the system hosting the dmgr.

    • Because some of these files might be used by other programs, it is possible that we are not allowed to remove all of the following files.

    • We do not need to remove Installation Manager files. These files might be associated with other IBM applications.

    1. IBM Connections installation files: connections_root

      If we did not install Connections in the default directory, delete the directory where you installed the product.

    2. IBM Connections shared and local content stores. Before removing this data, migrate your 4.0 content stores. For more information see the Content store migration.

    3. Connections configuration files: Delete the profile_root/config/cells/cell_name/LotusConnections-config directory, where cell_name is the name of the WAS cell.

    4. If it is present, delete the registry.xml file from the profile_root/config/cells/cell_name directory.

    5. Delete all .py files from the /opt/IBM/WebSphere/AppServer/profiles/profile_name/bin directory on the deployment manager server.


Results

You uninstalled IBM Connections.

If we plan to reinstall Connections at some point, refer to Upgrading and Migrating.


Parent topic:
Upgrade Connections v4.x to Connections v5.0


Related:

Content store migration


Related:

Back up IBM Connections DBS and file systems