GUI Reliability Tools Player

Back

LBL Global Distributed Gateway GUI Reliability Tools Player (GUIRT-P hereafter) is the instrument of repetitive reproduction of desktop tasks.

Through LBL GUIRT-P, it is possible to play recordings made through LBL Global Distributed Gateway GUI Reliability Tools Recorder, associating a unique identifier, structuring more tracks and perform a log end of events with any integration for the notification of anomalies. You can also activate the player in a particular time of day or schedule at regular intervals.

Start the Player

After the installation of the portable-app (see Installation Manual), to perform the start of player you must perform the following tasks:

  1. Navigate to the directory C:\TCOProject\bin\LBL\LBLLoadBalancer or, if already activated automatic start at startup of the desktop, go to step 4.
  2. Run command goPlayer.bat.

  3. The player will be activated as per installation done (see Installation Manual) and will provide a service in an https connection to the address indicated on port 4444 es.:

  4. Once logged in you will access the dashboard from which it is possible to add other nodes player for centralized management of the nodes player.

Add player nodes

The dashboard with license Catalog can add nodes to a centralized management of all installations LBL GDG you have login credentials delegated (see Manual LBL_ADC_AutonomousDelegatedAuthentication.pdf to deepen the concept of delegation and groups).

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global

Once you have made your selection nodes you will access the feature where you can add nodes to management.

Enter the characteristics of the node in the query window. It is appropriate to enter names and meaningful descriptions in order to identify the player immediately in the windows of the synthesis.

If the node inserted is turned on and discoverable will highlight a green checkmark. It is by definition should also enter oneself as a node component inventory for any management of a cluster.

We are also adding a second node

 


It will be appreciated that the node on which we are connected will have a tag location


Once you have added all the nodes in accordance with the licenses you need to confirm with the rescue operation of population of the inventory.

Save the changes made up to now, in this case will be affected only the inventory management system of the nodes, ec calls Workspace

Save prompts you to enter the reason for the change to find a possible restoration

After saving the dashboard will highlight that there are no other changes to save

Returning to the initial dashboard panels of synthesis will include all nodes counted

Selecting Reliability Tools>GUI Player we have the list of player counted for centralized management of the individual player. Also the player can be managed in the cluster or individually depending on the specific needs

Deploy & start player

To run the deployment of a track, previously created through the LBL GUIRT Recorder, it is sufficient to choose the node on which to run the deployment, in the example shown node MINNESOTA_PLAYER

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global
Define the general context activation as the activation to a specific time or other general characteristics at all traces of player

Below in tabular form the meaning of individual entries general context of implementation. These parameters are valid for all tracks. If not modified the player will cyclically perform traces halts the execution of the track to the occurrence of the error and continue with the next track.

Entry Description
StopAtEndTracksList If set to true, at the end of the execution of the traces the player stops without once again start running from the first track
ProgramErrorNotification In this parameter you can specify the name of a program or a batch of integration with the system of notification of events of the datacenter.

The program can be passed as arguments the significant values of the event through the use of metavalori that will be replaced with the values of the event :

%TrackID% = identifier of the track

%TrackFileName% = file name of the track

%TrackFilePathName% = name with the path to the file of the track

%TrackStepNumber% = number of step that caused the event

%HostName% = name of the host (desktop) that generated the event

%HostAddress% = address of the host (desktop) that generated the event

%MessageError% = error message generated by the event

%MaxTimeTrack% = maximum value set time to run the track

%TimeTrackExecuted% = execution time of the track

EnableStartAtHourMinute If true running traces will be enabled per hour and minutes specified in startAtHour startAtMinute and
StartAtHour If enableStartAtHourMinute to true is the time of execution of traces
StartAtMinute If enableStartAtHourMinute to true is the fraction in the minutes of the time of execution of traces
EnableStartEveryMinutes If true performs the traces cyclically with a range described in startEveryMinutes 
StartEveryMinutes If enableStartEveryMinutes to true is the execution interval of the traces for each cycle
StopAtError If set to true to the occurrence of an error indication in the execution of the track the player will notify you of the problem and will stop in the execution of the tracks
MaxOffTimeAsError If set to true, the exceeding of the threshold of time indicated on the player in the cell maxTimeTrack of specific track will be considered an error

Upload of the generated trace with LBL GUIRT Recorder

Choice of track to perform

Upload and subsequent selection of the possible list of replacement

The result will be the following

It is important to be able to add other information to the track. These information are typical of this player even if the trace can be used on more than one player. Take for example the maxTimeTrack. This value can be set differently depending on the position of the player. In fact from different places it is possible that Service Level Agreements (SLAS) are different to avoid SLA does not congruous with the connectivity of the place and then give indications that in that place are incorrect.

Once you have completed the step with the additional information you can save it and then start the player

Run the save confirming all the options proposed

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global

To save carried out return with back to the panel of tracks setup to run

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global


To start the player whose status is indicated by the icon to select the name of the module

From the control panel of the module it is possible to start the player through the Button Actions

The control panel of the module allows you to check the status of the major parameters including the number of errors

% Of employment of dedicated memory module

Internal partitioning of the memory

Detailed Log of step running

Services inside the module

Interfaces and desktop connectivity

Details of the module


Displays the remote desktop

Deploy second track

A player can run in sequence more tracks. To carry out the deployment of the second track is sufficient to perform an add on the panel Tracks (also hot)

Mouse, Puntatore, Freccia, Ps, Calcolatore, Www, Global

The result of the + is the total copy of the trace of departure.

We will go therefore to perform the upload of the second track

Just run the upload we can select the track has just been loaded by changing the descriptions and the trackID and possibly other typical values of the track

Save with the new parameters

Saving parameters

Arrived at this point you will notice a difference than before and that is an indication of reinit in top right that in the initial rescue had not appeared. This reinit is indicated why the player is running and then up to that we will not perform for explicit reinit hot continue execution in progress without changes.

We follow the link with the indication of the reinit

There will be proposed to perform the reinit hot module we are going to run

 

If we go back to the verification of the desktop we see that will perform two tracks

Going to check the¬†¬†general dashboard we see that there are errors that we can view by following the link to¬†view details¬†of the rectangle “Error Messages”

By following the link you will see a summary of the modules that have reported errors.

Following EEA details


Selecting the log we can check that the track MY002 generates an error in the comparison of the image which differs from that hold. In the log it is possible to investigate the reason for the difference being reported both the image comparison is the image present on the desktop in order to perform the operations of calibration of the track.

Troubleshooting

To troubleshoot  it is advisable to check the results of the operations on the database that shows in a manner normalized the contents of the log. The log is very detailed and allows to reconstruct all phases of the track up to the achievement of step that has generated the problem in the absence of configuration with logging on DB (see LBL_DBNetworkedConfiguration_lang.pdf).

For exercise, later on we will see at least two ways to reach the reading logs for convenience the interface allows to reach from multiple points the information.

The first method to reach the point of reading of the log

Select the module

From the Actions menu select View Logs

Select the log

Search for Error| and the cursor will highlight the first error message in the log.

The second method to reach the point of reading of the log

From the Actions menu select View Logs

Select the log

Search for Error| and the cursor will highlight the first error message in the log.

Brief description of the cells of a track

Entry Description
Description Description free of step contextualized in this desktop
FileName The name of the tracing file selected from the list of trace file present on the remote desktop
TrackID Free identifier of the track, this value will be reported in all logs if existing for a retrieval of the information of the anomalies
MaxTimeTrack If > zero will be controlled the total time of crossing of the track and if exceeded may generate an error or a warning in dependence of the general parameter maxOffTimeAsError 
EvalScreenSize If set to false does not check the values of desktop resolution that was used to record the track. It is useful to set it to false in cases there are traces that are not dependent on the size of the screen as for example any traces of carryover to the initial state of the desktop
Enable By setting it to false the track you can keep it in the list of tracks to run but will not be executed by the player
The EEA details Show/allows you to edit the track in xml format (not recommended)
Add new item Allows you to add new tracks to run in sequence
Remove item Allows you to remove traces from the execution list