A source system is a system that you want to record activities on. In the early stages of the installation on sandbox or development systems you might be operating with the source and target as the same system, however, it is best practice to complete the setup as below as if the source and target were separate systems.
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 Technologies into your source system, this is the system that you want to record Note that the transports can cause short dumps for users if they are using the system at the time of the import. It is therefore important that the transports are imported when there is little or no activity taking place on the system. |
| 2 | Regenerate delivered roles | Goto transaction PFCG, find the /BTI/* roles and ensure the profiles are generate. If they are not then generate them manually |
| 3 | Install Listener License Keys | Install the Testimony Listener Agent license keys provided by Basis Technologies into your source system. Separate keys for the Listener Agent will need to be installed into specific systems according to the instructions here. |
| 4 | Create Source RFC User | Create a system user with the role /BTI/AUT_SOURCE_RFC (ensure profile is generated). This user is for the RFC destination defined in the central system. Checking the RFC setup with the user at this point is best practice. |
| 5 | Enhancement Activation Program | After transports are deployed to the system the program /BTI/AUT_ENH_MANAGEMENT must be run before enhancements can be activated for recording or playback. The program should be run as per the standard selection screen with test mode not selected. Note this is a one off activity after the first installation. |
The following parameters should have been completed in the prerequisites, however, these should be double checked to ensure installation is correct.
| # | Profile Parameter | Details |
| 1 | rsdb/esm/buffersize_kb | This value should be at least ‘250000’ (250Mb) (the parameter is in kb). |
| 2 | rsdb/esm/large_object_size | This value should be at least ‘1000000’ bytes (1Mb). |
| 3 | rsdb/esm/max_objects | This value should be at least 100000 |
Post your comment on this topic.