Upgrading MCS in a Clustered Environment

You can upgrade MCS and management components only in a Windows environment. (In UNIX environments, you must uninstall any existing version before installing the current version.) If you work in a clustered environment, upgrading MCS includes several manual steps.

Warning Before you begin, back up the MCS directory and all its subdirectories on every server in the cluster.

To avoid unwanted replication during the upgrade process, stop the application server on every server in the cluster.
To upgrade MCS from version 2.1 on a server cluster
  1. Stop the application server on all secondary servers in the cluster.

  2. On the primary server, install the new version of MCS, and then stop the application server.

  3. Under ../mcs/WEB-INF/data/servermgt/settings, in the file ServerMgt.properties modify the values for the following to the value of your highest numbered XML file under ../mcs/WEB-INF/data/servermgt/servers (the value for the last secondary server in the cluster):

    • lastidserver

    • lastidcluster

  4. On all secondary servers, repeat steps 2 and 3, and then in the file ServerMgtLocal.properties under ../mcs/WEB-INF/data/servermgt/localsettings, verify the following values:

    • LocalServerID=ID for the local machine

    • PrimaryServerID=10001

    The ID for the local machine can be found in the file nnnnn.xml, in which the name attribute matches the name of hte server, under ../mcs/WEB-INF/data/servermgt/server/.

  5. Restart the application server on the primary server, and make sure that MCS is running.

  6. After you are sure that MCS is running on the primary server, restart the application servers on all secondary servers, one at a time.
Related Topics
Bullet Upgrading
Bullet Managing MCS Servers and Clusters
Bullet Installing in Windows
  Attachmate