The playback process can approximately the same time as the recording phase. However, this time can be reduced dependent upon the amount of bots you have available as well as the size of the target system(s) you are playing back into. The transaction volume from the recording also has an impact upon the playback time.
Dependent upon transactional volumes recording in learn phase, size of target system(s) compared to recorded system(s) and the number of bots available for the playback.
Audience / Users
Test team, Basis Administrators
All of the steps in the “Preparing Playback” section have been completed.
The process of running the execution queue involves the following:
(1) Run Check Steps – Prior to starting the execution queue playback, you must run the “check steps”. Select the queue, and then select the toolbar item “Shows steps” for the button “Check steps”. This will popup a window showing all of the check steps available. You can then manually select each row and execute it by choosing “Execute” -> “Run selected step only”.
The check step should run relatively quickly. If any errors are reported, you will see that in the “Status” column. You can then double click the check step then double click the lower left hand date/time/user entry in order to see the log messages.
If a fundamental issue is detected, you cannot start the execution queue. More help is available upon each check step by selecting the “Information” icon in the grid.
(2) Remote desktop onto bots – Before the execution queue starts, you should remote desktop onto all of the bots you have running. This step is only essential if you require “screenshots” to be generated for each step (in particular steps that fail). This would be the norm, so if you are running the bots upon Windows server, then you need to have a “graphics” context associated with them otherwise the screen-shots are “empty”. To achieve this, you should remote desktop onto all bot machines and then leave the remote desktops visible so that some part of the screen can be seen. The user session should not time out, otherwise from that point on, screenshots will be lost.
(3) Start the execution queue – Once the check steps are done, and everything looks ok to proceed, you can now begin the execution itself. First select the queue and then select “Start Execution Queue” in the toolbar. In this step, a job will be triggered asynchronously in the central system that co-ordinates the entire process of the execution queue playback. You can see immediately the number of steps that need to be executed in the top level information. You can drill down further to see the individual steps in the queue and filter/navigate through them.
When the “Start Execution Queue” button is selected, the check steps will be “checked” to ensure that all have passed ok. If not, you will be prompted as to whether you want to proceed. The first step of the job is to run the “preparation steps”. You do not need to run these manually as the execution queue will automatically do this. If any issues arise as a result of this, you will need to investigate the preparation step logs in order to determine if you would still like to proceed or not.
Once the status of the execution changes to “In Process”, this means that the queue is running. If you have visibility of the bot machines, you should start to see the bots performing the playback steps. This might be via the SAP GUI, but equally the console will show you if it is running other steps such as RFC’s and batch jobs.
(4) Queue monitoring – Within the “Execution Queue” menu, there is a “Monitoring” tab available for the purposes of checking the execution queue progress. You are able to see the counts at the top of the screen, however, the monitoring area provides more details. You should see all of the active bots in the top right of this screen. On the left are the queue of steps to be run and in the lower right, are the most recently executed steps.
Each of these screens provides a refresh button to re-display what is currently happening. The bulk of time spent in the monitoring process for the execution queue is pressing “refresh” within these windows to check on the progress of the playback.