In with the new! We periodically introduce improvements to Tealeaf. Here’s how you can update your existing installation with our latest ideas.
Just like a first time installation, plan things out. Know the upgrade path. You must be on Tealeaf version 9.0.2 FP7 or 9.0.2A FP7 to upgrade to Tealeaf version 10.x.
Understand the upgrade requirements, compare the hardware, software, and database requirements to what you have, and make changes before you try to upgrade.
Before you begin, complete all backups. If possible, create a mirror or each server.
Stop traffic. Pick the best time.
Download the upgrade software and run the upgrade tool in the proper order on every server and database in your environment. For details, review the process in the Upgrading section.
Upgrade from non-global versions of Tealeaf
This part of documentation is applicable only to customers who are using non-global Tealeaf version 9.0.2 (or earlier non-global versions like 8.7, 8.8, 9.0.1 and upgrades to 10.x.x via 9.0.2A) and upgrades to 10.x.x which is a global version. If you are using the global Tealeaf version 9.0.2A (or the earlier global version 9.0.1A and upgrades to 10.0.0 via 9.0.2A), this information is not applicable.
After upgrading Tealeaf from 9.0.2 to 10.0.0 with the PCA in a non-global state, you will need to add a parameter in your pipeline configuration.
- If PCA is sending hits directly to canisters, add the parameter in the Globals sections of the
TealeafCaptureSocket.cfgfile for each canister.
- If PCA is sending hits to an HBR server, then the parameter needs to be added in the Globals section of the
TealeafCaptureSocket.cfgfile on the HBR server.
To determine the encoding value to be set for the
DEFAULT_REQ_BUFFER_ENCODING parameter in
TealeafCaptureSocket.cfg, go to the Pipeline tab of the PCA Web Console. Note the value set for Default response encoding and Default request encoding fields and check the encoding set for these fields.
Then, in the Globals section of
TealeafCaptureSocket.cfg, add the
DEFAULT_REQ_BUFFER_ENCODING parameter by assigning the same encoding value to it. For example in the Pipeline tab, on the PCA side, if UTF-8 encoding is set, then the Globals section in TealeafCaptureSocket.cfg will look like this:
Before upgrading canisters or HBR servers from a non-global to a global version, make sure that there are no hits spooled on that respective server before performing the upgrade.
In the Pipeline tab of the PCA Web Console, for the Default response encoding and Default request encoding fields, if value is set to
None, then set the value of the
DEFAULT_REQ_BUFFER_ENCODING parameter to