Upgrading process

If one SLM server is running in your SLM Cluster environment, updating to SLM 7.5 or later requires downtime for your licensed applications.

You can upgrade an individual SLM Server in an SLM Cluster while the SLM Cluster continues to function. Sequentially update all the SLM Servers within the cluster as described in the "Upgrade procedure sequence".

Note: 

With SLM 7.0 the environment variable to locate the SLM software has become SLMHOME.

Older Infor applications build against older SLM versions require the BAANHOME environment variable. In those cases - ensure the BAANHOME environment variable is pointing to the same directory as the SLMHOME environment variable.

Upgrading a stand-alone SLM server

To upgrade a stand-alone SLM server, you must stop your running SLM server. Note that this impacts the availability of the licenses applications. Start the SLM installer, and upgrade the SLM server and the SLM MMC snap-in.

Upgrading an SLM Cluster

The concept of upgrading an SLM Cluster is to upgrade one-by-one each SLM server in the group. Do not make changes to the SLM configuration of the group during this operation; all SLM servers must operate on the same SLM version before configuration can take place (again). The complete upgrade of the SLM server group must take place within the time of the grace period. If the upgrade takes longer, the total number of licenses decreases.

See "Fail over" in SLM Cluster

During the upgrade, you can be forced to stop an SLM server that has allocated licenses to particular applications. The other SLM servers, which are still running, redistribution the licenses automatically.

See "Fail over", in SLM Cluster.

Upgrade procedure sequence

  • First upgrade the SLM Server with the ‘master’ role.
  • Upgrade the SLM Servers with the ‘slave’ role.
  • Ensure an SLM Server is up and running. To check this, run SLMClientTest.