Customers sometimes encounter issues while using APM. This is resolved sometimes through the creation of a hotfix by Sustaining Engineering. This workaround is used then by customers until incorporated into a release.
This knowledge article provides some guidance on hotfix usage and next steps should issues occur.
I just installed an APM Hotfix and encountering problems . What should I do?
Hotfixes could be created for any APM actively supported release. However, the issues described below are mainly for APM 10.2 on the EM.
After deploying a hotfix installation on a 10.2 EM, customers report sometimes a wide range of issues. These include cryptography-related errors, APM Team Center not working, various error messages due to mismatched jar files, and various other unexpected conditions.
Typically, this is caused by installing the Hotfix incorrectly. Sometimes this is due to unclear directions.
Note the following:
1) All APM HFs are cumulative. So HF #4 would include all the fixes from the previous hotfixes plus a new fix. (i.e. HF #1- #3.)
2) APM 10.2 HF #16 introduced dependencies on multiple jars.
3) Defect 177630 is reused in multiple HFs (10.2 HF#16, #19, and 10.3 HF#5). So, to apply any 10.2 EM/Webview HF after HF#16 correctly, the full set of jars touched by HF#16 needs to be applied also, not just the jars touched by that particular HF.
Note, this is also true for 10.3 HFs after HF#3, for the same reason.
Another important thing is to clear EM/Webview cache after applying the HF.