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)
4)
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).
Once the Nodes selection has been made, the function where it is will be accessed You can add management nodes.
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.
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.
Let's also add a second node
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
Saving requires you to enter the reason for the change for find a possible restore
After saving the dashboard will highlight that there are no others changes to save
Returning to the initial dashboard the summary panels will include all registered nodes
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
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
Define the general context of activation such as activation at a specific time or others general features to all tracks of the player
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
Choice of the track to be performed
Upload and subsequent choice of any replacement list
The result will be the following
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.
Once you have completed the step with the additional information it is possible save it and then start the player
Execute the save confirming all the options proposed
After saving, go back to the setting panel of the tracks to be performed
From the control panel of the module you can start the player through the Actions button
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
Internal memory partitioning
Detailed log of the steps in progress
Services within the module
Desktop interfaces and connectivity
Details of the form
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)
We will then go to upload the second track
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
Let's save with the new parameters
Saving the parameters
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
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
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
Following the link you will see a summary of the modules they have errors reported.
Following see details
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
We 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 of the log.
Second method to reach the log reading point
From the actions menu select View logs
Select the log
Search for ERROR \ | and the cursor will highlight the first error message of the log.
Brief description of the cells of a trace
Item | Description |
---|---|
description | Free description of the step contextualized to this desktop |
fileName | Name of the trace file chosen from the list of trace files on the remote desktop |
trackID | Free identifier of the trace, this value will be reported in all the logs if it exists for information retrieval of any anomalies found |
maxTimeTrack | If > 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 |
evalScreenSize | If 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 |
enable | By 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 details | View / allow you to edit the trace in xml format (not recommended) |
Add new item | Allows you to add new play tracks in sequence |
Remove item | Allows you to remove tracks from the playlist |