After running the upgrade on all of the components in your Acoustic™ Experience Analytics (Tealeaf) environment, finish the upgrade by completing the following post-upgrade cleanup tasks.
Before you begin to use Experience Analytics, clear your browser's cache. Some files in your cache might have changed on the server during the upgrade. For more information about clearing the cache, see your browser's documentation.
If you want to see information in your dashboard reports immediately after you perform the upgrade, you will need to restart the data collector and data service. If you don’t want to restart, you will need to wait for the nightly aggregation cycle to see your data.
If you have questions about the process or the steps that are required to upgrade your Experience Analytics solution, contact our support team. You can reach them via email at Help.AcousticID@acoustic.com or at the following phone numbers:
United States: +1 866-820-5136
United Kingdom +44 808 169 2385.
Updating the Application Pool settings
Complete the steps listed here to update the Experience Analytics Application Pool settings in Microsoft™ Internet Information Services (IIS).
- On the server that supports the Experience Analytics Portal, log in to the Windows™ server and open IIS Manager.
- Locate the Portal server node. Click Application Pools.
- Change the setting for .NET Framework Version to a support version.
- Restart the IIS service before you log in to the Portal.
Review the logs
Confirm that the upgrade completed without error. Review the following logs for error messages.
- Errors that are related to the conversion of events and installation of new event definitions are located in <install_directory>\Logs\TLEventManager-yyyyMMdd.log.
- Messages that are related to the database upgrade and data migration processes are located in <install_directory>\Logs\TeaLeafDatabaseManagerYYYYMMDD_*.log .
- Application errors are located in the Event Viewer. Open the Event Viewer and open the Application node. Review the entries for the Experience Analytics warning and error messages.
Set the recovery model to Simple
Set the Recovery Model for all Experience Analytics databases to
Re-apply custom configurations on the Portal
You can modify certain files that enable you to customize the Portal web application in your Acoustic Experience Analytics (Tealeaf) environment. However, because the upgrade does not preserve those customizations, you must apply the customizations again after the upgrade.
- Review the following files and apply the pre-upgrade changes to the default files installed during the upgrade process.
These files enable you to specify configurations specific to your instance of the Portal web application. During the upgrade process, these files are automatically backed up in the same directory where they are located.
- Open the
Web.configfile and add the following code to the root node of the file.
Note: This modification is in addition to any custom modifications that you might need to re-apply.
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Syncfusion.Pdf.Base" publicKeyToken="3d67ed1f87d44c89" /> <codeBase version="4.402.0.51" href="bin\syncfusion.pdf.Base.dll" /> <codeBase version="14.2450.0.32" href="bin\Syncfusion14\Syncfusion.Pdf.Base.dll" /> </dependentAssembly> </assemblyBinding> </runtime>
Configure HBR for 64-bit pipeline (optional)
By default, the Experience Analytics upgrader configures the Health-based routing (HBR) server to support a 32-bit pipeline. However, you can configure the HBR to support a 64-bit pipeline for better performance in high load conditions.
The HBR server supports a limited number of 64-bit session agents that can process global and non-global data. After you complete the Experience Analytics installation or upgrade, you can change the HBR server configuration to use the approved 64-bit session agents.
Canister servers and the Experience Analytics PCA process 32-bit data only. When you connect the PCA and canister servers to a HBR server that uses a 64-bit pipeline, you must configure the HBR server to handle 32-bit data on entry and exit.
Note: The session agents in the HBR pipeline must all be either 32-bit or 64-bit agents. You cannot combine 32-bit and 64-bit session agents in the same pipeline.
Post-upgrade cleanup on the Replay server
After the upgrade finishes, you must perform several post-upgrade cleanup tasks on the Acoustic Experience Analytics (Tealeaf) Replay server.
- Disable Interactive Services Detection: For the WebKit/Chrome renderer to function properly, the Interactive Services Detection service on the server that hosts Replay Server must be disabled.
- Give the Replay server access to the Origin server: The Replay server requires access to the server that hosts the web application for effective replay.
- Update POST data matching configuration to recognize new content types: If you upgraded to the current release and use the DWR library, you must update the Replay server profile and each RTV replay profile to recognize the DWR requests and to apply the appropriate POST data matching plug-in to locate the corresponding response.
Individual users of RTV must apply this change to their local replay profiles.
Replay server must run as Local System user
The Replay server must be run as the Local System user.
Before you begin replaying sessions through browser-based replay (BBR), complete the following steps for each Replay server in your environment.
- Log in to the server that hosts the Replay server.
- From the Start menu, open the Services control panel.
- From the list of services, select Tealeaf Replay Server.
- Right-click the service and select Properties.
- Click the Logon tab.
- Click the
Local System accountradio button.
- Select the
Allow service to interact with desktopoption.
- Click OK.
- Right-click the service and select Restart.
- Repeat the steps for every other Replay server in your Experience Analytics environment.
Start all Experience Analytics services
If you did no do so already, start all Experience Analytics services on all upgraded servers.
If you modified the
ADMIN group, you must update menu permissions manually for that group. For all other users and groups, you must configure the appropriate permissions.
If your upgrade includes any newly licensed Acoustic Experience Analytics (Tealeaf) products, automatic access to product features is granted to the
ADMIN group if you did not modify your
ADMIN group permissions since original installation.
Back up the event model
Before you begin making modifications to your event definitions, perform an event model backup, which can be used to restore event definitions to a previous state.
Archive your backups
Transfer all backups that you made before the upgrade to a safe and permanent location.