Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
guide:execute:start [2018/11/05 12:21]
127.0.0.1 external edit
guide:execute:start [2019/02/07 17:12] (current)
adminizor [Jobs Menu] Updated Screencaptures of Web Admin Menu & missing Search & Delete Icons
Line 375: Line 375:
 ##  Jobs Menu ##  Jobs Menu
  
-![image](./​image178.png)+{{:​guide:​execute:​ztmainwebadminmenu.jpg|}}
  
-![image](./​image179.png)+{{:​guide:​execute:​ztjobslocalagent.jpg?​direct|}}
  
 All load test programs which are started from the Project Navigator are always executed as "batch jobs" by an (external) **Exec Agent** process or by an **Exec Agent Cluster**. This means, that it is not required to wait for the completion of a load test program on the “Execute Load Test” window: you can close the "​Execute Load Test" window at any time and you can check later the result, or the actual effort, of all load test jobs by using this menu. All load test programs which are started from the Project Navigator are always executed as "batch jobs" by an (external) **Exec Agent** process or by an **Exec Agent Cluster**. This means, that it is not required to wait for the completion of a load test program on the “Execute Load Test” window: you can close the "​Execute Load Test" window at any time and you can check later the result, or the actual effort, of all load test jobs by using this menu.
Line 396: Line 396:
 ^ Item ^ Description ^ ^ Item ^ Description ^
 | Job | Each job has its unique ID which was automatically assigned when the job was defined. However the ID is only unique per Exec Agent. Cluster jobs have an own, separate ID (own enumeration counter). | | Job | Each job has its unique ID which was automatically assigned when the job was defined. However the ID is only unique per Exec Agent. Cluster jobs have an own, separate ID (own enumeration counter). |
-| {{/icon/search.png}} | Allows to acquire the statistic result file (`.prxres`) of an already completed load test job - or reconnects to the temporary statistic of the load test job if the job is still running – or allows to cancel the schedule of the job. |  +| {{search.gif}} | Allows to acquire the statistic result file (`.prxres`) of an already completed load test job - or reconnects to the temporary statistic of the load test job if the job is still running – or allows to cancel the schedule of the job. |  
-| {{/icon/delete.png}} | Deletes all data (-files) of a completed load test job. Take into consideration that you must first acquire the statistic result file (`*.prxres`) of the job before you delete all files of a job - otherwise the result data of the job are lost. | +| {{delete.gif}} | Deletes all data (-files) of a completed load test job. Take into consideration that you must first acquire the statistic result file (`*.prxres`) of the job before you delete all files of a job - otherwise the result data of the job are lost. | 
 | Date | Displays the date and time when the job has been defined or when the job has been completed, or - for scheduled jobs - the planned point in time when the job will be started. |  | Date | Displays the date and time when the job has been defined or when the job has been completed, or - for scheduled jobs - the planned point in time when the job will be started. | 
 | State | Displays the current job state: configured (ready to run), scheduled, running or completed. The state "???"​ means that the job data are corrupted - you should delete all jobs which have the state "???"​ because they delay the display of all jobs in this list. |  | State | Displays the current job state: configured (ready to run), scheduled, running or completed. The state "???"​ means that the job data are corrupted - you should delete all jobs which have the state "???"​ because they delay the display of all jobs in this list. |