Note that non-admin users will still require access to the transaction /N/BTI/AUT with specific access to activities then maintained in Testimony, users investiagting defects in playback systems will require the correct authorisations to investigate the issues found.
Authorization/Role Notes
| User | Role/Authorizations | Notes |
|---|---|---|
| Testimony Administrator | /BTI/AUT_CENTRAL_ADMINISTRATOR, /BTR/DIF:EXPERT, /BTI/AUT_SOURCE_RFC | The Testimony Administrator(s) will be the technical solution leads for Testimony. Typically this is the Basis admins that will be starting, stopping, and monitoring the recordings. |
| BOT user in Central | /BTI/AUT_BOT_RFC | The BOT user is used for the BOT machines to establish an RFC connection to the Central system in order to receive script instructions for playback. It is typically named BTI_BOT |
| RFC user in Source | /BTI/AUT_SOURCE_RFC | The RFC source user is defined in the Source system and entered into an RFC connection defined in the Central system to connect to the Source for recordings. It is typically named BTI_SOURCE_SID |
| Batch User | ||
| RFC user in Target | /BTI/AUT_TARGET_RFC /BTI/AUT_BOT_SIMULATION |
The RFC target user is defined in the Target system and entered into an RFC connection defined in the Central system to connect to the Target for playback. It is typically named BTI_TARGET_SID. The user defined in the Target system requiring auths for creating Users, assigning Roles to Users and Deleting Users, which is required during the BOT Simulation |
| RFC Metadata User | /BTI/AUT_NCO_METADATA_ACCESS | |
| Transactions Needed to Monitor Source | ST22, ST02, SM66 as a minimum | These transactions are used to monitor the Source system during recordings, which is typically performed by a Basis team member |
| Transactions Needed to Monitor Target | ST22, ST02, SM66, SM51, SM50, SE16 as a minimum | These transactions are used to monitor the Target system during playback activities, which is typically performed by a Basis team member |
Authorization/Transaction Code Details
| Role | Transaction Codes | Notes |
|---|---|---|
| /BTI/AUT_CENTRAL_ADMINISTRATOR | /BTI/AUT | Testimony Primary Transaction Code |
| /BTR/MDR, /BTR/MDRH, /BTR/MINICUBE | BTI Diffuser tool transaction codes | |
| AL08, SM04, SM50, SM51, SM66 | Used to monitor active users and processes | |
| RZ10, RZ11 | Used to view/update profile parameters | |
| SE01, SE09 | Used for transport management, only necessary when bringing in new transports | |
| SE11, SE16 | Used for config table maintenance | |
| SE24, SE37, SE38, SE80, ST22 | Used for development, troubleshooting, and code corrections | |
| SM59 | Used for setting up RFC connections | |
| SMGW | Used to monitor gateway connections, primarily for BOTs | |
| ST02 | Used to monitor memory/buffer statistics | |
| ST03 | Used for system utilization analysis | |
| SU01D | Used to display user details and role assignments | |
| /BTI/AUT_BOT_RFC | RFC Objects that can be executed using this role: /BTI/*, RFC1, RFC_METADATA, SYST | These are for connecting to the Central system for the purpose of obtaining work to playback via the BOTs into the Target system. |
| /BTI/AUT_SOURCE_RFC | RFC Objects that can be executed using this role: /BTI/*, SBUF, SCSM, SCSM_COLLECTOR, SDTX, STUB, SUNI, SU_USER, SYST, THFB | These are for activating and deactivating the enhancements, starting and stopping the recordings, and collecting usage data in the Source system |
| /BTI/AUT_TARGET_RFC | RFC Objects that can be executed using this role: /BTI/*, SDTX, STUB, SUNI, SU_USER, SYST | These are for activating and deactivating the enhancements to facilitate the playback of activities in the Target system |
| /BTR/DIF:EXPERT | /BTR/DIFFUSER, /BTR/LICENSE, /BTR/MDR, /BTR/MDRH, /BTR/MDRH_OLD, /BTR/MINICUBE | BTI Diffuser tool transaction codes |
Post your comment on this topic.