Upgrading on a Cluster

Before you get started with your upgrade, you might want to read the clustering and caching overview topics. Clustering and caching interoperate closely on a clustered installation.

In addition, be sure to confirm that the plugins you're using are compatible with the version you're upgrading to. In some cases, you might need to make changes to plugins to ensure they work on the later version of the application.

You must upgrade from version 4.0.0 or later.
  1. Make sure you have read Before You Upgrade and performed the relevant steps listed there.
  2. Remove all plugins from your existing instance. (You'll need to re-install them via the Admin Console after you've successfully upgraded). For a list of supported Jive plugins, see this list in the Jive Community.
  3. Stop all application server nodes in the cluster.
  4. Install the application package (such as the RPM on Linux) on the cache server(s). Note the cache server address(es). You'll need them later when you set up the application servers.
  5. Make sure the cache server(s) is running. It must be running while you set up the application server nodes.
  6. On each node in the cluster, upgrade the application instance using the package, but don't run the setup tool yet.

    For more information about upgrading with the package, see Upgrading a Linux Package.

  7. Start the Activity Engine, Search, and Document Conversion services.
  8. Start one web app node (and only one web app node) and navigate to its instance with a web browser. Work through the upgrade tool, allowing it to run the upgrade tasks it lists.
  9. Restart the application server you've upgraded and navigate to it with a web browser again. In the setup screen provided, enter the address of the cache server(s), then complete the setup tool.
  10. After you've finished with the setup tool, restart the application server.
  11. Start the application server on each of the other nodes. Because it's connecting to the same database used by the server on the node you've already set up, the server on each subsequent node will detect that clustering is enabled. Each will also pick up the configuration you set on the first node.
  12. After setting up all of the application server nodes and running them once, restart all servers in the cluster to ensure that the address of each node in the cluster is known to all the other nodes. The entire cluster must be bounced after all the nodes are set up.
  13. You can now reapply any plugins you installed. See Post-Upgrading Tasks for your next steps.