The key steps to perform an upgrade of Testimony are summarised below:
| Step | Activity | Other Information |
|---|---|---|
| 01 | Provision of Testimony Software | To request the latest version of Testimony, please email your Basis Technologies Account Manager |
| 02 | Verify if existing MDR/Diffuser Customer | If you are an existing MDR/Diffuser customer, please ensure you inform Basis Technologies – as upgrading to the latest version of Testimony can have detrimental impact on the existing MDR/Diffuser installation if not carefully planned. |
| 03 | Read the ReadMe | Carefully read the ReadMe file provided with the transports when upgrading. |
| 04 | Plan the impact on your current recordings | As Testimony is NOT backwards compatible older recordings may not be able to be successfully played back on the newer versions. You will need to check on compatibility between versions by contacting Basis Technologies Support. The best advice is always to record and playback on the same version of Testimony. Anything already executed and with results will still be stored for future reference. |
| 05 | Plan upgrade timing over a short period of time | Testimony is NOT backwards compatible because of the nature of some of the new functionality. This means you should plan to apply the new Transports in the systems and upgrade the Bot machines in a relatively short period of time as you may not be able to record or playback with incompatible versions |
| 06 | Plan the deployment of transports | The enhancement transports can cause short dumps while being deployed to a Source or Target systems therefore choose a time of ideally no activity or very low activity to deploy the transports. |
| 07 | Deactivate Enhancements in Source and Target systems | Deactivate Testimony enhancements before deploying transports by running the program /BTI/AUT_DEACT_ENH to deactivate enhancements directly on the Source and Target systems. |
| 08 | Deploy transport to Central system | Apply upgrade transports one by one in the order specified to Central System(s) |
| 09 | Check Central system setup | Check the Central system setup section for the version of Testimony being deployed as this may have been updated. |
| 10 | Deploy transport to Source system | Apply upgrade transports one by one in the order specified to Source Systems |
| 11 | Check Source system setup | Check the Source system setup section for the version of Testimony being deployed as this may have been updated. |
| 12 | Deploy transport to Target system | Apply upgrade transports one by one in the order specified to Target Systems |
| 13 | Check Target system setup | Check the Target system setup section for the version of Testimony being deployed as this may have been updated. |
| 14 | Deploy new Bot software | Deploy new bot software as per the ReadMe with any other steps actioned while deploying. |
| 15 | Check bot machine setup | Check the bot setup is complete as per the Bot Setup section for the version of Testimony being deployed as this may have been updated. |
| 16 | Check security roles | Check Testimony supplied roles are in place for the correct users, the upgrade may have provided extra authorisations in roles provided. These roles should be re copied if the standard Testimony roles supplied were copied into the local naming conventions |
| 17 | Consider team training | If functionality has changed or there is a change of process intended as a part ot the upgrade |
| 18 | Testimony Central System | Validate the Central system is setup as expected and check if any of the current General Parameter’s should be updated with the new default settings provided. |
| 19 | Testimony Testing | Ensure test recordings and playbacks are run, this will ensure any steps missed in upgrading systems are picked up by running recording and playback tests |
| 20 | Review System Refresh Steps | Check the system refresh steps section for the version of Testimony being deployed as this may have been updated. |
| 21 | Carefully deploy Testimony to Production Environments | 1. Find a time with no or very low activity on the system 2. Deactivate Testimony enhancements by running the program /BTI/AUT_DEACT_ENH 3. Apply upgrade transports one by one in the order specified |
| 22 | Communicate Testimony Upgrade Complete | Ensure you update your team on the new version of Testimony and any differences in process. |
Post your comment on this topic.