GUIRT player

Notes before use

Oplon Global Distributed Gateway GUI Reliability Tools Player (GUIRT-P from now on) is the repetitive playback tool desktop activities.

Through Oplon GUIRT-P it is possible to play the recordings made through Oplon Global Distributed Gateway GUI Reliability Tools Recorder, associate a unique identifier, structure multiple traces and fine-log events with possible integration for the notification of anomalies found. IS also can activate the player at a particular time of day or schedule it at regular intervals.

Start of the Player

After installing the portable-app (see manual of installation), to start the player you have to do the following operations:

1) Go to the directory C:\TCOProject\bin\LBL\LBLLoadBalancer or, if already activated Autostart on desktop startup, go to step 4.

2) Run the goPlayer.bat command.

3) image1 the player will be activated as per installation done (see installation manual) and will put an https service is available at the address indicated on the port 4444 ex .:

4) image2 Once logged in yes will access the dashboard where you can add more nodes player for centralized management of player nodes.

Add player nodes

The Catalog licensed dashboard can add nodes for management centralized of all Oplon GDG installations of which you have the delegated access credentials (see manual LBL_AutonomousDelegatedAuthentication.pdf to learn more about the concept of delegation and groups).

image4

Once the Nodes selection has been made, the function where it is will be accessed You can add management nodes.

image5

Enter the characteristics of the node in the request window. IS it is advisable to include names and meaningful descriptions so as to identify the players immediately in the summary windows.

image6

If the inserted node is on and reachable, a sign of will be highlighted green tick. By definition it is also appropriate to include yourself as inventory component node for eventual management of a cluster.

image7

Let's also add a second node

image8

image9

image10 You will notice that the node we are on linked will report a position tag

image10 Once all nodes have been added according to with the licenses it is necessary to confirm the operation by saving of population of the inventory.

Let's save the changes made so far, in this case it will be only the inventory of the node management system is concerned, yes call workspace

image11

Saving requires you to enter the reason for the change for find a possible restore

image12

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

image13

Returning to the initial dashboard the summary panels will include all registered nodes

image14

Selecting Reliability Tools > GUI Player we will have the list of players registered for the centralized management of individual players. Even the players they can be managed in clusters or individually depending on the specific needs

image15

Deploy & start player

To deploy a track, previously created through the Oplon GUIRT Recorder, just choose the node on which to run the deploy, in the example the MINNESOTA_PLAYER node

image16

Define the general context of activation such as activation at a specific time or others general features to all tracks of the player

image17

The meaning of the individual general items is shown below in table form context of execution. These parameters are valid for all traces. If not modified, the player will cycle through the tracks stopping the execution of the trace when the error occurs e continuing with the next track.

Voice Description
stopAtEndTracksList If set to true, at the end of the execution of the tracks the player stops without starting the execution again from the first track
programErrorNotification

In this parameter you can indicate the name of a program or a batch of integration with the datacenter event notification system.

The program can be passed as arguments the significant values of the event through the use of meta-values which will be replaced with the event values:

% trackID% = track ID

% trackFileName% = name of the track file

% trackFilePathName% = name with path of the track file

% trackStepNumber% = number of the 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 time value set to run the trace

% timeTrackExecuted% = time to execute the trace

enableStartAtHourMinute If true the execution of the traces will be activated at the hour and minutes specified in startAtHour and startAtMinute
startAtHour If enableStartAtHourMinute is the time of execution of the tracks
startAtMinute If enableStartAtHourMinute to true is the fraction in minutes of the running time of the tracks
enableStartEveryMinutes If true, it cycles traces with an interval described in startEveryMinutes
startEveryMinutes If enableStartEveryMinutes to true is the execution interval of the traces for each cycle
stopAtError If set to true when an error message occurs in the execution of the track, the player will notify the problem and stop in the execution of the tracks
maxOffTimeAsError If set to true, when the time threshold indicated on the player in the maxTimeTrack cell of the specific track is exceeded, an error will be considered

Upload of the track generated with Oplon GUIRT Recorder

image18

Choice of the track to be performed

image19

Upload and subsequent choice of any replacement list

image20

The result will be the following

image21

It is important to be able to add other information to the track. These information is typical of this player even if the track can be used on multiple players. Let's take the maxTimeTrack for example. This value can be set differently depending on of the player's position. Indeed from different places it is possible that SLAs (Service Level Agreements) are different to avoid SLAs not congruent with the connectivity of the place and therefore give reports that in that place are wrong.

image22

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

image23

Execute the save confirming all the options proposed

image24

After saving, go back to the setting panel of the tracks to be performed

image25

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

From the control panel of the module you can start the player through the Actions button

image27

image28

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

\% of memory occupation dedicated to the module

image29

Internal memory partitioning

image30

Detailed log of the steps in progress

image31

Services within the module

image32

Desktop interfaces and connectivity

image33

Details of the form

image34

image35 Displays the remote desktop

Deploy second track

A player can play multiple tracks in sequence. To deploy of the second track it is sufficient to perform an add on the Tracks panel (even hot)

image36

image37 The result of the + is the total copy of the starting track.

We will then go to upload the second track

image38

As soon as the upload is done we can select the track just uploaded changing the descriptions and the trackID and eventually the other values typical of the track

image39

Let's save with the new parameters

image40

Saving the parameters

image41

At this point you will notice a difference compared to before and that is an indication of reinit in the upper right corner of the initial save it hadn't appeared. This reinit is indicated why the player is in execution and then until we explicitly execute the reinit a hot will continue running without the changes made.

We follow the link of the indication of the reinit

image42

We will be offered to perform the hot reinit of the module that we will go to perform

If we go back to checking the desktop we will notice that they will perform two traces

image43

Going to check the general dashboard we will notice that there are errors that we can view by following the View details link "Error messages" rectangle

image44

Following the link you will see a summary of the modules they have errors reported.

Following see details

image45

image46 By selecting log we can verify that the trace MY002 generates an error in comparing the image that differs from that expected. In the log it is possible to investigate the reason difference being shown both the comparison image and the image present on the desktop in order to perform the operations of track calibration.

Troubleshooting

To perform the troubleshooting it is recommended to verify the results of the operations on the database that reports the contents in a normalized manner of the log. The log is very detailed and allows you to reconstruct all phases of the track until reaching the step that generated the problem in the absence of the configuration with logging on DB (see LBL_DBNetworkedConfiguration_lang.pdf).

For exercise, below we will look at at least two ways to achieve the reading logs. For convenience the interface allows you to reach from more points the information.

First method to reach the log reading point

image47

We select the module

image48

From the actions menu select View logs

image49

Select the log

image50

Search for ERROR \ | and the cursor will highlight the first error message of the log.

image51

Second method to reach the log reading point

image52

From the actions menu select View logs

image49

Select the log

image50

Search for ERROR \ | and the cursor will highlight the first error message of the log.

image51

Brief description of the cells of a trace

ItemDescription
descriptionFree description of the step contextualized to this desktop
fileNameName of the trace file chosen from the list of trace files on the remote desktop
trackIDFree identifier of the trace, this value will be reported in all the logs if it exists for information retrieval of any anomalies found
maxTimeTrackIf > zero, the total crossing time of the trace will be checked and if exceeded it can generate an error or a signal depending on the general parameter maxOffTimeAsError
evalScreenSizeIf set to false it does not check the resolution values ​​of the desktop that was used to record the trace. It is useful to set it to false in cases where there are traces that are not dependent on the screen size such as any traces that carry over to the initial state of the desktop
enableBy setting the track to false it is possible to keep it in the list of tracks to be played but it will not be played by the player
See detailsView / allow you to edit the trace in xml format (not recommended)
Add new itemAllows you to add new play tracks in sequence
Remove itemAllows you to remove tracks from the playlist