How to Apply a Quick Fix (QPM) in Applications Manager ?

How to Apply a Quick Fix (QPM) in Applications Manager ?

Please follow the steps below to apply the QPM provided by the support team.

QPM Deployment Steps for Applications Manager version 17.98.00 and above

Professional Edition:

1.Enable Immediate Deployment (Optional)
  1. The server can be configured to deploy the QPM process immediately after the QPM file is uploaded to the server. This is done by enabling the option “Initiate QPM Deployment immediately after the file upload completes" under Settings → Global Settings.


2Uploading the QPM File
  • The QPM file can be uploaded from Settings → Upload Files / Binaries, using the option "Upload QPM to <Product_Home>/working/quickfixes/".

  • Once the QPM is uploaded, its status can be viewed under Support → Product Summary → QPM Details or The QPM Details page can also be accessed from the QPM Details link located in the upper-right corner of the Upload QPM section on the QPM Upload page.


3. Server Restart

  • If immediate-deployment option is enabled, the product restarts automatically after the QPM upload the prompt will appear stating the product will restart now to apply QPM If you wish to proceed. Once confirmed,the QPM deployment process will start in a seconds.

  • If immediate-deployment is not enabledthe QPM deployment process can be initiated by clicking the Apply QPM button on the QPM Details page for the respective QPM.


Info
Failover Server:
In a failover setup, the QPM will first be deployed on the currently active server and then on the standby server. The following log trace can be found in the standby server’s wrapper.log. After this, the QPM will be pushed from the primary server to the secondary server and applied there.

Enterprise Edition:

1.Enable Immediate Deployment (Optional)
  1. The central server can be configured to deploy QPM immediately after a QPM file is uploaded. This is done by enabling the option “Initiate QPM Deployment immediately after the file upload completes" under Settings → Global Settings on the central server.

  1. Once enabled, this option in the central server it will automatically synced to all probe servers.
  2. To restrict specific probes from immediately deploy the QPM, the option needs to be disabled on those probes.

2. Uploading the QPM File
  1. The QPM file can be uploaded from Settings → Upload Files / Binaries, using the option "Upload QPM to <Product_Home>/working/quickfixes/" on the central server.
  2. After the QPM is uploaded, its status can be viewed under Support → Enterprise Summary → QPM Details or The QPM Details page can also be accessed from the QPM Details link located in the upper-left corner of the Upload QPM section on the QPM Upload page.
  3. If the QPM is need to be applied only on the central server, the option "Apply only on central server" should be selected before uploading the QPM in the central server.


3. Server Restart
  1. If immediate-deployment option is enabled in the central server the QPM deployment process will be started in few seconds in the central server.
  2. If the immediate-deployment is not enabled on the central server. Navigate to Support → Enterprise Summary → QPM Details page and click on Apply QPM button to initiate the QPM deployment process.


  1. The probe QPM sync can also be checked from the central server and the QPM deployment of the probe can be initiated from the central server.


4. Probe Sync
  1. Once the QPM is successfully applied on the central server, it will be synced to all probe servers within a few minutes.
  2. If the immediate-deployment option is enabled on the probe servers, they restart automatically and apply the patch.
  3. If immediate-deployment is not enabled, The QPM deployment process can be initiated from the Support → Enterprise Summary → QPM Details page by Click on Apply QPM on the page.
  4. Sync details are displayed under Support → Enterprise Summary → QPM Details, where the download status is shown as COMPLETED.
  5. In some cases, the central server may not be reachable from the probe server, causing the QPM sync to fail. In such situations, please upload the failed QPM again on the probe server.
InfoFailover QPM Behaviour:
In an enterprise failover setup, once the QPM is applied on the central server, it will automatically be pushed to the standby server and applied there. Similarly, when a QPM is applied on the probe servers, it will also be automatically pushed to and applied on the probe standby servers.
The following log traces can be found in the wrapper.log of the primary server. Once the QPM is applied on the primary server, it will be pushed to the secondary server and applied there.




QPM Deployment Steps for Applications Manager version below 17.98.00

Professional Edition:

1. Auto-Restart Option (Optional)

  • For APM version 176600 or later, the server can be configured to restart automatically after a QPM is uploaded. This is done by enabling the option “Restart the product after the QPM upload” under Settings → Global Settings.

2Uploading the QPM File

  • The QPM file can be uploaded from Settings → Upload Files / Binaries, using the option "Upload QPM to <Product_Home>/working/quickfixes/".

  • Once the QPM is uploaded, its status can be viewed under Support → Product Summary → QPM Details.

3. Server Restart

  • If auto-restart is enabled, the product restarts automatically after the QPM upload, and the changes take effect upon restart.

  • If auto-restart is not enabled, a manual server restart is required after the QPM upload for the changes to be applied.


Enterprise Edition:

1. Auto-Restart Option (Optional)

  •  For APM version 17.66.00 or later, the central server can be configured to restart automatically after a QPM is uploaded. This is done by enabling the option “Restart the product after the QPM upload” under Settings → Global Settings on the central server.

  • Once enabled, this option is automatically synced to all probe servers.

  • To restrict specific probes from automatically restarting, the option needs to be disabled on those probes.

2. Uploading the QPM File

  • The QPM file can be uploaded from Settings → Upload Files / Binaries, using the option "Upload QPM to <Product_Home>/working/quickfixes/" on the central server.

  • After the QPM is uploaded, its status can be viewed under Support → Enterprise Summary → QPM Details.

  •  If the QPM is to be applied only on the central server, the option "Apply only on central server" should be enabled.

3. Server Restart

  • After the QPM is successfully applied on the central server, it is synced to all probe servers within a few minutes.

  • If auto-restart is not enabled in the central server, a manual restart of the central server is required after the QPM upload for the changes to be applied.

4. Probe Sync

  • Once the QPM is successfully applied on the central server, it will be synced to all probe servers within a few minutes.

  • If the Auto Restart option is enabled on the probe servers, they restart automatically and apply the patch.

  • If Auto Restart is not enabled, the probes must be manually restarted after the QPM sync.

  • Sync details are displayed under Support → Enterprise Summary → QPM Details, where the download status is shown as COMPLETED.

  • In some cases, the central server may not be reachable from the probe server, causing the QPM sync to fail. In such situations, please upload the failed QPM again on the probe server.

     

    NotesAuto restart option can be enabled even after the QPM is uploaded to the server. The Applications Manager instance will be restarting and Apply the QPM in few minutes.



                  New to ADSelfService Plus?

                    • Related Articles

                    • ManageEngine Applications Manager High Availability setup with dual database (MySQL).

                      Apart from the Failover setup,  which uses a single database and dual Application Server, we also support a failover with dual database and Application Server. Failover support requires you to configure Applications Manager Secondary (Standby server) ...
                    • Disable HTTP access in Applications Manager

                      Overview This article describes configuring a secure connection between Applications Manager server and the browser/client. Applications Manager can be accessed through any of the following URLs: For HTTP  -> http://[hostname/ip-address]:[http-port] ...
                    • Graphs are not displayed in Applications Manager

                      Issue: Graphs are not displayed in Applications Manager. Fix: Verify if you have given read/write permissions for AppManager\working\webclient folder. If not, kindly update the permissions, the issue will be resolved.
                    • Monitoring Capacity Entitlement in Applications Manager

                      Applications Manager is equipped to monitor processor capacity entitlement issues. To measure the average entitlement value during peak production times with a higher workload, you can use the following command: lparstat 1 20 > /tmp/apm_physc.txt && ...
                    • Applications Manager not starting after upgrade

                      If Applications Manager is not starting, it could be due to the following: 1. License would've expired. Please apply valid license using updateLicense.bat/updateLicense.sh. Refer this link to know how to apply license. 2. Take a look at the log trace ...