Installation of the software into the source and target system should have been completed as per the installation section here.
The following parameters need to be checked and changed in the systems specified where required.
| # | Profile Parameter | System | Details |
| 1 | rsdb/esm/buffersize_kb | Source & Central | This value should be about ‘100000’ (100Mb) (the parameter is in kb). Note that this won’t be required for a very small recording |
| 2 | rsdb/esm/large_object_size | Source & Central | This value should be at least ‘1000000’ bytes (1Mb). Note that this won’t be required for a very small recording |
| 3 | rsdb/esm/max_objects | Source | This value should be set as default as at least 20000 |
| 4 | gw/acl_mode | Central | This value needs to be 0 which allows the drones/bots to register themselves on the gateway (playback preparation) |
| 5 | rsdb/esm/max_objects | Central | This value should be set as default as at least 2000 |
| 6 | sapgui/user_scripting | Target | This value needs to be TRUE which allows the bots to perform the playback properly. Only in playback system. |
| 7 | 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. |
| 8 | 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. |
| 9 | 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. |
Testimony requires a userid for the bot to access the central system as well as two RFC destinations: one from the central system to the source and one from the central system to the target. As the target system is a copy of the source it may be necessary to create the target system RFC after the copy is complete.
Testimony also requires a logical filepath and OS Command to move and hold files during recording and playback.
| # | Activity | Details |
| 1 | Bot User | Use SU01 to create a BOT_USER user (suggested name) in the central system. This user requires the following role /BTI/AUT_BOT_RFC (ensure profile role is generated) The user needs to be of type System User |
| 2 | Source RFC User | Use SU01 to create a SOURCE_USER user (suggested name) in the source system. This user requires the following role /BTI/AUT_SOURCE_RFC (ensure profile role is generated) The user needs to be of type System User |
| 3 | Create Source RFC | In your central system, use SM59 to create an ABAP RFC connection to your source system. Specify the SOURCE_USER id and password and test the connection using Utilities —> Test —> Authorization Test |
| 4 | Target RFC User | Use SU01 to create a TARGET_USER user (suggested name) this user needs to be available in the target after a copy back. This can mean that creating this user in the source before copy back can reduce the setup required This user requires the following role /BTI/AUT_TARGET_RFC (ensure profile role is generated) The user needs to be of type System User |
| 5 | Create Target RFC | In your central system, use SM59 to create an ABAP RFC connection to your. target system. Specify the TARGET_USER id and password and test the connection using Utilities —> Test —> Authorization Test |
| 6 | Create OS Command | In each system (central source and target) setup a new OS command called YAUT_COPY_FILE in transaction SM49 (For WINDOWS NT Operating system command is xcopy, for LINUX is cp ) |
| 7 | Logical Filepath | In each system (central source and target) setup a folder for the logical path /BTI/AUT_APPSERVER_FILESt using transaction FILE |
Post your comment on this topic.