The Central system is where Testimony is operated from (details on operating Testimony are found in the Administrators Guide) once setup is complete there should be relatively few times that changes are required in the source or target systems.
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 system. This would typically be your SAP Solution Manager system. |
| 2 | Regenerate delivered roles | In each system into which transports have been deployed, go to transaction PFCG, find the /BTI/* roles and regenerate |
| 3 | Testimony administrator access | Assign the role /BTI/AUT_CENTRAL_ADMINISTRATOR to the Testimony Administrators in the Testimony central system |
| 4 | Check main transaction | In the central system, execute the main Testimony transaction /N/BTI/AUT. If this transaction does not exist then check the transports have been imported correctly |
| 5 | Install License Keys | Install the Testimony license keys provided by Basis Technologies into your central system only as per the central license section here. |
| 6 | Install Listener License Keys | Install the Testimony Listener Agent license keys provided by Basis Technologies into your central system. Seperate keys for the Listener Agent will need to be installed into specific systems according to the instructions here. |
| 7 | Filter Set Number range | Use SAP standard transaction SNRO for Object /BTI/AUT33 to setup three number ranges as follows 01 from 0000000001 to 0999999999 08 from 8000000000 to 8999999999 09 from 9000000000 to 9999999999 |
| 8 | Assign Administrators | The first person to start Testimony using the transaction /N/BTI/AUT will be assigned as a Testimony administrator. You should assign the other Administrators to this role at this point, |
Once this is complete you can move onto the next part of the installation:
| # | Activity | Details |
| 1 | Bot User | Use SU01 to create a BOT_USER user (suggested name) in the central system. This user requires the role /BTI/AUT_BOT_RFC (ensure profile role is generated) The user needs to be of type System User |
| 2 | Create Source RFC | In the central system, use SM59 to create an ABAP RFC connection to the source system. This requires the user created in the source system as per the details here then test the connection using Utilities —> Test —> Authorization Test |
| 3 | Create Target RFC | In the central system, use SM59 to create an ABAP RFC connection to the target system.This requires the user created in the target system as per the details here then test the connection using Utilities —> Test —> Authorization Test |
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 about ‘250000’ (250Mb) (the parameter is in kb). |
| 2 | rsdb/esm/large_object_size | This value should be at least ‘51200000’ bytes (50Mb). |
| 3 | rsdb/esm/max_objects | This value should be at least ‘2000’ |
Post your comment on this topic.