Regardless of your SAP system scope and architecture, some general installation steps will need to be performed on your SAP systems to prepare them for Testimony.
|3.1.1||Import Testimony software||As described in the previous “Installation” section.|
|3.1.2||Check main transaction||In the central system, execute the main Testimony transaction /BTI/AUT.|
|3.1.3||Create RFC users|| Use SU01 to create a user in all clients of all SAP source systems (systems to be recorded). This RFC user needs the appropriately authorized role assignment.
For all remote systems the RFC user needs to be of type System User or Service User.
|3.1.4||Create RFC destinations (in central system)|| Use SM59 (Create Connection) to create RFC destinations in your Testimony central system that connect to both the recording system(s) and the target playback system(s).
After set up, test the connection via Utilities -> Test -> Authorization Test
|3.1.5||Check system parameters (in both recording and playback systems)|| These must be set appropriately so that both recording and playback can operate correctly. Access control for the central system gateway should be set up to allow the drone to connect to the central system. Please refer SAP help link for further details: SAP Help
This will require a system restart.
|3.1.6||Check object size parameter||Ensure the system parameter rsdb/obj/buffersize is set to an appropriate level (100Mb+)|
|3.1.7||Check system parameters (in all target systems)||Check that the system parameter sapgui/user_scripting is set to a value of “TRUE”. This may require a system restart.|
|3.1.8||Install the SAP Playback agent (in external machines)||Download and install the Drone executable file from the Testimony central system (Utilities drawer -> Software).|
Thanks for your feedback.