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 from.
Testimony Central System minimum specifications
| Software | SAP NW 7.01+ ABAP stack |
| Disk | 400GB (350 GB for SAP install plus free space, 50GB available for growth with Testimony utilization) |
| System Memory | 8GB (16 GB+ recommended) |
| CPU | Multi-core 64-bit processor (4 cores recommended) |
| Processes | 20 BTC, 20 DIA, 1 ENQ, 1 SPO, 1 UPD, 1 UP2 (assumes up to 15 Bot machines defined) |
| Notes | Must have network connectivity to Source, Target, and BOT systems |
In addition to the central system there will also be “source” SAP systems where recordings take place and “target” SAP systems into which recordings are played back. At the start of the installation Basis Technologies recommends that a sandbox system is used and it is likely that the same system will be used for both recording and playback. To playback you will also require a windows machine to host the Bot. Details on this are here. Once you start recording larger systems note that the target will need to be sized sufficiently to allow for all of the source system activities being run on it.
At this stage it is important to determine which systems will be acting as “central”, “source” and “target” systems as each requires different setup. The Basis Technologies consultant will also want the detail of these systems entered into the Testimony Gameplan to assist with planning and documenting the installation.
2. Determine Administrators
Installing and maintaining Testimony requires a basic working knowledge of SAP plus an understanding of your organisation’s testing processes.
Basis Technologies recommend 1-2 resources be assigned as Testimony Administrators. These will typically be the senior testing managers and/or basis administrators.
The proposed Testimony administrators should be determined before the installation is started.
3. Profile Parameters
The following profile parameters should be set as per the list below, note that as some of these require a system restart planning should be taken around the production system taking note of maintenance windows. These parameters will be reviewed and may be adjusted depending on your installation.
| # | Profile Parameter | System | Details |
| 1 | rsdb/esm/buffersize_kb | Source & Central | This value needs to be at least ‘100000’ (100Mb) (the parameter is in kb). |
| 2 | rsdb/esm/large_object_size | Source & Central | This value needs be to at least ‘1000000’ bytes (1Mb). |
| 3 | rsdb/esm/max_objects | Source | This value needs to be at least 20000 |
| 4 | rsdb/esm/max_objects | Central | This value needs to be at least 2000 |
| 5 | sapgui/user_scripting | Target | This value needs to be TRUE which allows the bots to perform the playback properly. Only in playback system. |
| 6 | sapgui/user_scripting_per_user | Target | This value needs to be FALSE which allows the bots to perform the playback properly. Only in playback system. |
| 7 | sapgui/user_scripting_set_read_only | Target | This value needs to be FALSE which allows the bots to perform the playback properly. Only in playback system. |
| 8 | login/disable_password_logon | Target | This value needs to be 0 which allows the bots to login to the playback system. Only in playback system. |
| 9 | login/disable_multi_gui_login | Target | This value needs to be 0 this allows multiple logons. Only in playback system. |
| 10 | rdisp/tm_max_no | Target | As Testimony will be logging on with the user load from production this should be the production setting +50% Only in playback system. |
| 11 | rdisp/gui_auto_logout | Target | This value needs to be 0. This ensures that the bots and their logged on users cannot be automatically logged off by the user due to time-limits (for example, if the playback is paused or other issues arise) |
| 12 | rdisp/max_wprun_time | Target | Ensure this value is at least the value set in the production system |
| 13 | abap/buffersize | Target | Ensure this value is at least the value set in the production system |
| 14 | ztta/parameter_area | Target | This value needs to be at least 64000. The value checked can be adjusted by changing PLAYBACK_PARAM_AREA in the General Parameters. Only in playback system. |
| 15 | snc/enable | Target | This value needs to be 0 this is required where TimeShiftX is being operated. Only in playback system. |
4. File Configuration
To enable Testimony to record and playback files then the following setup needs to be completed in each system that Testimony is intended to operate in central, source and target.
| # | Activity | Details |
| 1 | Create OS Command | In each system (central, source and target) set up a new OS command called YAUT_COPY_FILE in transaction SM49 (For WINDOWS NT Operating system command is xcopy, for LINUX is cp ) |
| 2 | Logical File Path | In each system (central, source and target) set up a folder for the logical path /BTI/AUT_APPSERVER_FILES using transaction FILE |
5. Operating Systems
Enter into the Game Plan the operating systems for the application and database servers for the SAP systems where Testimony is to be installed. This is required for the installation of TimeShiftX which is required to keep the date and time of the target system aligned with the date and time of the recording when playing back, more details in the TimeShiftX section.
Post your comment on this topic.