Always install and upgrade to the latest version of the Passive Capture Application (PCA) that is compatible with the Acoustic™ Experience Analytics (Tealeaf) components that you have installed. Because the PCA runs on Linux servers, you upgrade it independently from the rest of your Experience Analytics components, which operate on Windows servers.
If your Experience Analytics environment contains multiple PCA instances, repeat the upgrade process on each server. Do not upgrade the PCA and Windows-based Experience Analytics components at the same time. Upgrade the PCA after you have upgraded the Experience Analytics components that run on Windows servers.
For use with version 10.0: Acoustic Experience Analytics (Tealeaf) Version 10.0 is compatible with PCA builds 3682-24 and 3732-24. If you have already installed these PCA builds, there is no need to upgrade your PCA instance to work with Experience Analytics Version 10.0.
For use with Version 10.0.1: To take advantage of the fixes and features provided by the release of Experience Analytics Version 10.0.1, including support for the W3C Beacon API, you must upgrade to PCA Build 3741.
Preparing to upgrade the PCA
Before you upgrade the PCA, make sure that your Acoustic Experience Analytics (Tealeaf) environment is ready for the upgrade. A few checks now will help avoid problems later.
Confirm that your Linux environment meets the PCA upgrade requirements. The requirements for upgrading the PCA are the same as those for installing the PCA.
If your PCA is configured to decrypt SSL traffic, verify that your existing SSL keys are compatible with the version of PCA that you are upgrading to.
Schedule the upgrade for off-peak hours. Unless your PCA is configured to fail over to another server, the PCA does not capture hits while the upgrade installer is running. Typically, the upgrade process lasts between 5-10 minutes.
Verify that you saved a copy of the .rpm file that was used install your current version of the PCA. If the PCA upgrade fails and you are unable to rectify the problem, you can revert to the old version of the .rpm file.