Upgrading the monitoring solution version
Scenario: Suppose you have PATROL Agent and the Linux Knowledge Module (KM) deployed on 500 computers. You already have an existing infrastructure policy, named "Linux Monitoring" for monitoring the Linux computers.
Now, a new version of the Linux KM or in other words the Linux monitoring solution is available. You want to upgrade the KM to the new version.
To upgrade the monitoring solution version, you need to perform the following steps. Use the steps as an example to understand the upgrade process.
Step 1: Identify the current version of the deployed monitoring solution
Identify the current version of the Linux monitoring solution deployed. It is possible that you have different versions deployed across the 500 computers. You need to ensure that the deployed versions are supported for upgrading to the available new version.
To understand the deployed versions, on the Configuration > Managed Devices page, from the main action menu, select Export Solutions by Agents. For more information, see Managing Infrastructure Management devices from the TrueSight console.
In the following image, notice the solution version is 1.2.00.
Step 2: Import the new monitoring solution
On the Administration > Repository page, import the new monitoring solution as a single solution. For more information, see Importing the Infrastructure Management repository.
In the following image, notice the Linux installation component versions 1.2.00 (old version) and 1.2.00.04 (higher version).
Step 3: Create a deployable package to upgrade the solution versions
After importing the single solution, on the Administration > Repository page, create a deployable package to deploy the new Linux monitoring solution (with the higher version) across all the required target hosts in your environment. For more information about creating a deployable package, see Creating deployable packages.
In the following image, notice the higher version deployable package created.
Step 4: Verify the deployed monitoring solution
Verify if the same version of the new monitoring solution is deployed across all the target hosts in your environment.
To do this, on the Configuration > Managed Devices page, from the main action menu, select Export Solutions by Agents. For more information, see Managing Infrastructure Management devices from the TrueSight console.
In the following image, notice the solution version is 1.2.00.04.
Step 5: Update the monitoring solution version in the infrastructure policy
On the Configuration > Infrastructure Policies page, locate the policy created for monitoring Linux computers.
Then, edit the policy and update the monitoring solution version to the higher version.
In the following image, you can see the lower and the higher versions for the Linux monitoring solution.
With a new monitoring solution, you can get new configuration features. Therefore, it is possible that you might have to add additional details or update additional fields in the existing configuration to get the new features. If the new fields are mandatory, this is indicated when you save the policy.
In this particular case, if you edit the RHEV Manager Details configuration, you can see that a new field, JVM Arguments is added, as indicated in the following image. However, this field is not mandatory.
After you update the monitoring solution version to the latest version in the policy, you cannot restore it to the earlier version. Therefore, when you save the policy, you are prompted to backup the policy to preserve the earlier version. When you backup the policy, a copy of the policy is created as indicated in the following image. By default, the policy copy is disabled.
This is the last step in the process of upgrading the monitoring solution version.