Search
Related topics are listed below.
System Refresh Steps
Technical Setup » Target System » System Refresh Steps
*Note that parameters should be changed on each app server # Description Required Notes 1 Activate recording on the source system Yes 2 Put the source database into online backup mode Yes …
Central System
Technical Setup » Central System
Follow the steps below to ensure Testimony is correctly installed on the central system. # Activity Details 1 Install Testimony into Central System Install the transports provided by Basis Technologies into your central…
Source System
Technical Setup » Source System
Follow the steps below to ensure Testimony is correctly installed on the source system. # Activity Details 1 Install Testimony into Source System Install the transports specified for the source system provided by Basis…
Target System
Technical Setup » Target System
Follow the steps below to ensure Testimony is correctly installed on the target system. # Activity Details 1 Install Testimony into Target System Install the transports specified for the target system provided by Basis…
Production Ramp-Up
Validating the Installation » Production Ramp-Up
When deploying to a production system run through the source system setup as defined in the technical setup here. Then schedule recordings which incrementally increase the recording time and complexity as below, while the SAP Basis team closely monitoring the system…
Upgrade Steps
Upgrading Testimony » Upgrade Steps
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…
Installing Testimony in new systems
Installing Testimony in new systems
When installing Testimony in new systems go back through the same steps for the type of system where Testimony is being installed as below: Central System Source System Target System Bot System *If upgrading always ensure that the enhancements are deactivated…
Technical Setup
Technical Setup
After the prerequisite processes have been completed you can now begin the Testimony implementation, including configuration of the product and preparing it for use. Basis Technologies recommends that the first recording and playback are completed on a Sandbox system…
Prerequisites
Prerequisites
There are five sets of activities that should be completed before Testimony is installed and configured. 1. Determine Systems Before installing check the Architecture section and determine the “central” SAP system where Testimony will be operated…
Background
Technical Setup » TimeShiftX » Background
The end state of a Testimony installation is to record real user transactions executed in a production SAP system and plays them back into a copy of that system. The playback system is based on a backup of the production system as it was at the start of the recording,…
Config File Maintenance
Technical Setup » Bot Setup » Config File Maintenance
When installing for the first time or changing the Central system where Testimony is operating, each bot’s main config file will need to be updated. To build the config file that allows the Bot to connect to the SAP central system where Testimony is deployed,…
Glossary
Glossary
Bot The bot is an executable which resides on a windows machine (normally a virtual machine). During playback the bot logs on as the recorded user and executes that user’s transactions. The requirements for bot setup can be found here. Central System This is the…
QA Testing
Validating the Installation » QA Testing
Basis Technologies recommends that the Testimony setup is fully tested before operating in a production system. When deploying to the system identified to act as the source system for QA testing ensure the source system setup is run through as defined in the technical…
Uninstall Transports and Configuration
Uninstallation » Uninstall Transports and Configuration
Transports Via the Add-On Manager, you can apply the deletion Transports to remove all the objects associated with Testimony. The transports will be provided by Basis Technologies upon request. It is recommended that the uninstallation of any Production system objects…
First Recording and Playback
Validating the Installation » First Recording and Playback
Having completed the Technical Setup the first recording and playback should be completed. Follow the Quick Start Guide for details on how to operate a recording and playback in Testimony, essentially it will be these steps below: 1. Test Plan and System Connections…
Architecture
Architecture
The architecture of Testimony comprises four types of systems as below: Central system (usually Solution Manager) Testimony is operated from here with recordings and playback details stored here. Source system to be recorded (e.g. ECC development, test and…
Central Licenses
License Keys » Central Licenses
Testimony is licensed by the central system and the individual source systems that are to be recorded. Within this screen users can see existing licenses that are currently installed and add/change existing ones. Before a central license is applied or once a central…
Uninstallation
Uninstallation
To remove the installation of Testimony from your system there are steps to follow to ensure it is completed safely. The tool will have been installed in Central, Source and Target systems. There are Uninstallation transports supplied for each system and they will be…
Bot Testimony Setup
Technical Setup » Bot Setup » Bot Testimony Setup
Steps to setup the Bot in Testimony 1) In the central system, execute transaction /N/BTI/AUT, navigate to the ‘Execution’ tray and select ‘Supporting Infrastructure’. Click the create button to add a new bot. 2) Fill in the details for the desktop/remote…
Bot Appears Inactive
Technical Setup » Bot Setup » Trouble Shooting » Bot Logs » Bot Appears Inactive
If the bot is active on the bot machine and the output logs look correct, however, the bot does not appear active on the Central system check if the central system has multiple app servers as the config file will need to be updated for a system using a message server…
License Keys
License Keys
License keys are required on the Central system directly through Testimony and the Diffuser licenses are required in each system Central, Source and Target as per the links below: Central Licenses Diffuser Licenses
Check installed keys
License Keys » Diffuser Licenses » Check installed keys
To check the products you have installed in your system, select the “List installed products” option as below and Execute. The keys installed are shown as below. Note that any red status icons indicate a problem with the key details being consistent…
Installing a License
License Keys » Diffuser Licenses » Installing a License
After entering the license screens through the transaction /N/BTR/LICENSE or via the button on the /N/BTR/MINICUBE as described in Maintaining Licenses. To install a license simply select the “Install key file” option as below and execute. Select the…
SAP Gateway
Technical Setup » Bot Setup » Trouble Shooting » SAP Gateway
If you are having issues with the bot the SAP Gateway Monitor can also be checked. You can launch this from Testimony or use transaction SMGW. If the SAP Gateway is causing an issue the parameter gw/acl_mode should be set to 0 on the central system and the central…
Timing & Sequence
Uninstallation » Timing & Sequence
However since software is being removed it is best practice to conduct the removal during a planned maintenance window. It should be noted that there is no specific order in which to uninstall the Testimony add-on as there are no inter-system dependencies between…
Bot Setup
Technical Setup » Bot Setup
After completing the preparation and installation activities on the Central system, the bots can now be configured. The following sections will take you through the bot setup Installing the Bot Config File Maintenance SAP GUI Configuration Bot Testimony…
Software Support
Software Support
After appropriate testing on your SAP test systems, you are now ready to use Testimony within your productive landscape. Remember that Testimony is dormant in your SAP system until activated for recording. You must ensure that Testimony recordings are deactivated after…
Windows License – TimeShiftX
Technical Setup » TimeShiftX » Windows Setup – TimeShiftX » Windows License – TimeShiftX
1. Click Start -> Program Files -> TimeShiftX -> activate 2. Type Y then press Enter 3. Type your 16-digit key then press Enter 4. If successful, you will see “Activation Successful”. Press Enter to finish. a. If behind a firewall, open port 80 and retry…
Linux License – TimeShiftX
Technical Setup » TimeShiftX » Linux Setup – TimeShiftX » Linux License – TimeShiftX
1. As a regular non-root user, run the license utility $ tsxactivate.sh 2. Type Y then press Enter 3. Paste your 16-digit key then press Enter 4. If successful, you will see “Activation Successful”. Press Enter to finish. a. If behind a firewall, open port 80…
Config File Specialisations
Technical Setup » Bot Setup » Config File Maintenance » Config File Specialisations
Config File – Specialisations SAP GUI Location The bot may be running in an environment where SAP’s SAPGui.exe files are not in the standard location. The logfile on startup will report it as: A new entry in the config.xml will allow an alternative…
Introduction
Introduction
The Testimony Installation and Setup Guide takes you through setting up Testimony for use in your SAP system landscape. It is recommended that you check the following sections so you are familiar with Testimony before starting. Glossary Architecture The following…
Upgrade Considerations
Upgrading Testimony » Upgrade Considerations
The following should be considered as part of an upgrade to latest version of Testimony: 1. Latest software transports will need to be applied in the Central system plus Source and Target Systems, the Bot executable will also require an upgrade. 3. Always be aware…