Home

User Manual - centeractive

1. 4 1 2 FORMATS Within this panel you can change the way certain data gets formatted and represented in the GUI 4 1 2 1 DATE FORMATS This box lets you define date and time formats that are used throughout the Mirador program The entered patterns must conform to the specifications valid for the Java class SimpleDateFormat see http java sun com j2se 1 5 0 docs api java text SimpleDateFormat html Option Description Date Format Pattern that specifies a date without the time The default value is vyyy MM dd Date Time Format Pattern that specifies a date together with the time The default value is yyyy MM dd HH mm ss Date Time ms Format Pattern that specifies a date together with the time and should include milliseconds The default value is yyyy MM dd HH mm ss SSS 4 1 3 ALERTS This panel relates to alerts issued by the monitored Hawk agents Description Remove cleared and read This option defines after how much time in seconds cleared alerts shall alerts after be removed from the alert tables when these alerts have been read by the user An internal worker process repeatedly goes through all buffered alerts and checks whether the defined number of seconds has expired since an alert reached its read amp cleared state Each time the worker process has checked all alerts it waits a few seconds before it starts checking them again Remove cleared only alerts This option defines afte
2. 5 Read Write Method F Mirador Agent centeractive User Manual Mirador Release 2 1 Description Each agent has a set of microagents that are represented like this and placed within a group node or a branch of group nodes Microagents can also appear underneath the inbuilt Mirador pseudo agent if they are successfully loaded from the Mirador plugin directory The user can also define agent collection microagents that are based on existing microagents found on any remote agent Such KEE microagents are placed within the Agent Collection node E that appears as soon as the first agent collection microagents is defined Icon Annotations The microagent description could not be retrieved from the agent Microagent method nodes are placed directly below the owning microagent node Depending on the application options and the name of the method it may be placed inside a method group node that is created on the fly This icon stands for a read only microagent method Icon Annotation amp There is at least one subscription active on that method This icon stands for a write microagent method a method that has an impact agent s side Icon Annotation amp There is at least one subscription active on that method Read write microagent methods are represented by this icon Icon Annotation There is at least one subscription active on that method This top level node represents the internal Mirador a
3. Datagrams sec over a period of 5 minutes Datagrams sec 13 10 00 13 10 30 13 11 00 13 11 30 13 12 00 13 12 30 Time copyright centeractive ag 13 13 00 13 13 30 13 14 00 13 14 30 Page 35 of 57 centeractive User Manual Mirador Release 2 1 Result View Description When a microagent method invocation results in an error exception the error message gets shown with the stack trace This is helpful for failure tracking when debugging custom microagents or AMI enabled programs Invocation Description Arguments Key Result at 2008 05 12 14 47 13 MicroAgentException AMI application returned error Error msg Key must be specified Stack Trace COM TIBCO hawk talon MicroAgentException AMI application returned error Error msg Key must be specified at COM TIBCO hawk agent mafactories AmiTibryMicroAgent invyokeMethod Unknown Source at COM TIBCO hawk agent macollection MicroAgent inyvoke Unknown Source at COM TIBCO hawk agent macollection Collection invoke Unknown Source at COM TIBCO hawk console nest agent RemoteAccessServer invyokeRequested RemoteAccessServer java at COM TIBCO hawk console nest agent RemoteAccessServer invokeRequested RemoteAccessServer java at COM TIBCO hawk console nest agent RemoteAccessServer processRequest RemoteAccessServer java at COM TIBCO hawk console nest agent RemoteAccessServer access 200 RemoteAccessServer java at COM TIBCO hawk console nest agent Remo
4. svchost exe 1936 7 svchost exe 584 46 svchost exe 1936 svchost exe 2008 svchost exe 584 svchost exe 1220 spoolsv exe 344 stacsv exe 384 svchost exe 672 svchost exe 3216 copyright centeractive ag Page 31 of 57 centeractive User Manual Mirador Release 2 1 Result View Description pie chart 3D The behavior and configuration of this view is the same as the one of the simple pie chart described above The pie however appears in 3D mode As with the simple 2D pie you can rotate the pie and show or hide the section labels An additional slider from the result control box lets you change the depth of the 3D pie Arguments Process Name sv Result at 2009 11 03 15 00 40 Mem Usage per Process Name ID Process spoolsv exe 344 13 5 svchost exe 3216 10 svchost exe 2008 7 svchost exe 1936 svchost exe 2008 svchost exe 584 svchost exe 1220 spoolsv exe 344 stacsv exe 384 svchost exe 672 svchost exe 3216 copyright centeractive ag Page 32 of 57 Result View multiple pie chart User Manual Mirador Release 2 1 Description This view shows several pies one for each row from the result table data Every single pie proportionally shows data from different type in relation to a total of 100 One of the table columns has to be chosen as the label column The label column defines the name of individual pies and must contain
5. TIBHawkEvent TIBCO Hawk OWN DO STOPPED 1077 No attempts istri Li i il TIBHawkHMA TIBCO Hawk HMA INTERACTIVE_OW N_PROCESS STOPPED 0 The operation completed successfully O 0 O copyright centeractive ag STOP SHUT U 0 0 O 0 O 0 O View Label Column Label Column 2 Value Columns ea gt e Service e Win32 Exit Code Service Exit Code Check Point Wait Hint Page 23 of 57 centeractive User Manual Mirador Release 2 1 Both Invocation and Subscription panels have the same toolbar appearing in the top right corner The individual buttons are described in the following table Button Description Show Result in Form Shows the current and future result data within the same panel in a form This button only appears if the result is of composite data structure Show Result as HTML Table Shows the current and future result data within the same panel as an HTML formatted table This button appears only if the result data is of composite data that by default gets displayed in form Create Agent Collection Creates a collection microagent that is based on the current Microagent Method selected microagent method The collection microagent is a Mirador software component that appears as a tree node within EE the Agent Collection node EI The Agent Collection node itself becomes visible only as soon as the first collection microa
6. The microagent method nodes are represented by different icons depending on their impact Icon Impact 5 Synchronous Info Asynchronous Info d s Action Gi Action Info Description This is a synchronous read only method that only provides information without provoking any action or changing any data Icon Annotations This annotation indicates that there exist one or several active subscriptions on this method This is an asynchronous method that provides information when a certain event occurs Icon Annotations amp This annotation indicates that there exist one or several active subscriptions on this method This method type does not return any data but provokes an action on the target agent Such actions can be the execution of a script modification of some data etc Icon Annotations amp This annotation indicates that there exist one or several active subscriptions on this method This method type provokes an action on the target agent and returns some data related to that action Icon Annotations amp This annotation indicates that there exist one or several active subscriptions on this method The microagent detail view by default contains the two tabbed panels Invocation and Description Additional tabbed Subscription panels are added each time you subscribe to a method within the Invocation panel copyright centeractive ag Page 21 of 57
7. C Sun SDKxib jdic jdic jar C Sun SDKMib install tray tray jar C Sun SDK lib appserv rt jar Tray 1078 NORMAL_PRIORITY_CLASS CA40005 markus 16248 16288 17184 4964 7129 View Label Column Label Column 2 Value Columns default Cluster ID Process Parent Process ID CPU Time Mem Usage Peak Working SetSize Page File Usage Page Fault Count Start time Every method of an agent collection microagent is based on the microagent method from where the EA button was activated The name and display name of the agent collection microagent and its methods remain identical to the ones of the base microagent and methods The descriptions are the same as the ones from the base microagent plus some text that gives further information about the collection related behavior The real apparent differences are the following e The agent collection microagent most often contains only a subset of the methods found on the base microagent copyright centeractive ag Page 49 of 57 centeractive User Manual Mirador Release 2 1 Two elements are added to the method arguments The new arguments are named Cluster Names and Agent Names and they let you specify the remote agents that shall have their corresponding microagent method invoked When an agent collection microagent method is invoked the method invocation is forwarded to all remote agents if their setti
8. L core bo012 h core bo014 LJ database db007 Indude Schedules Indude Rulebases Indude Microagents Output format e HTML Output file c Users Office mirador export doc BRAYO Environment html Open file after generation copyright centeractive ag Page 57 of 57
9. a copyright centeractive ag Page 22 of 57 User Manual Mirador Release 2 1 centeractive The Invocation panel represents the main user interface to interact with the Hawk agents on remote hosts Invocation Description Arguments Result at 2009 11 17 13 42 08 Service Display Na 7 TIBHawkHMA TIBCO Hawk T T Table Row Details Service Display Name Service Type Current State Win32 Exit Code Exit Code Description Service Exit Code Controls Accepted Check Point Wait Hint OWN_PROC PROC INTERACTIV STOPPED 0 rhe operati 077 077 Trkwks Distributed L SHARE_PRO RUNNING 0 thecperati Udfs Udfs FILE_SYSTE STOPPED 1077 No attempts 0 C Adjust table to panel Service Type Current St Win32 Exi Exit Code Service Ex IDPIPE IDPIPE KERNEL_DR 5 IOPPEL Uff No attempts JU mer TDTCP_KERNELDR STOPPED 1077 Nosttempts d_ TermDD Terminal De KERNEL_DR RUNNING O Tee 0 TOP TermService Terminal er SHARE PRO RUNNING 0 Weste 0 Themes Themes SHARE PRO RUNNING 0 Weste 0 Som TIBCOAdmin TIBCO Admi OWN PROC STOPPED o Wee 0 tibemsd TIBCO EMS SHARE PRO RUNNING 0 Weste 0 STOP SHUT tibemsmed MIBCOEMS SHARE PRO STOPPED 1077 __Noattempts 0 TIBHawkAgent TIBCO Hawk DM PROC STOPPED o Weste 0 5 TIBHawkAg TIBCO Hawk OWN_PROC RUNNING 0 The operati 0 STOP SHUT 0
10. and Enterprise Message Service Communication Channel a Rendezvous Service The Rendezvous parameters are Caaan by Mirador to create a session in order to connect to a Rendezvous daemon Rendezvous Network see above Rendezvous Daemon see above Communication Channel aie Message Service server edi The user is an optional parameter if the EMS session requires authentication authentication copyright centeractive ag Page 41 of 57 centeractive User Manual Mirador Release 2 1 4 1 1 1 ADVANCED OPTIONS Advanced Hawk Environment options can be defined in a separate dialog that pops up if you press the Advanced button right to the common option fields The individual advanced options are explained in the table that follows E Advanced Options Hawk Rendezvous Options Security Class COM TIBCO hawk security trusted Trusted Character Encoding Customizing Method Invocation Customizer Class com opentrend mirador agent microagent DeFaultMethodInvocationCustomizer Alert Description File C iDatalMiradoriresourcesiHawkAlertDescription xml Description Security Class Name of the Java class that implements the Hawk Security Policy When defining a standard security class please make sure the lt HAWK HOME gt bin directory is in the variable path This is required because Hawk needs an additional DLL HawkTrustedUserID dll which is located in t
11. gt Load Subscriptions either to the same agent or to any other agent during the same Mirador session or during subsequent sessions Microagent method subscriptions can also be loaded simultaneously to multiple agents The Mirador program can load subscriptions only if the chosen target agent contains a microagent method that is identical with the one the subscription was running on when it was saved to the file When microagent method subscriptions are successfully loaded the Mirador program also tries to start them After the loading process you can easily switch to the different microagent method subscription panels by selecting the entries from the Subscriptions menu If you load the same microagent method subscriptions on an agent that already has the same subscriptions loaded these subscriptions will not be overwritten The Mirador program will always try to create new subscriptions This is not a problem for standard microagent method nodes but may not be possible when the target node does not directly represent a remote microagent i e BusinessWorks monitoring nodes Views The Mirador program lets the user save the current view by selecting the menu item View gt Save Current View When the current view is saved to a file the Mirador program collects the items listed below and writes them in XML format to a file copyright centeractive ag Page 47 of 57 centeractive User Manual Mirador Release 2 1 e All agent colle
12. Description Depending on whether the method returns individual fields or tabular data this view shows the result in a form or a table according to the following examples made with the standard microagent Process Example Method Process getInstanceCount This method expects one argument and returns two fields If a result field contains multiple line text data a mouse click on the editor icon behind the field lets you pop up a dialog where you can display the data in its full mode Arguments Process Mame java Result at 2007 07 30 09 52 40 Example Method Process getProcess This also expects one argument but returns a table where each row represents a process running on the related host The rows can be sorted by any column by clicking on the corresponding column header Selecting the check box appearing top right of the table will adjust its width to the enclosing panel copyright centeractive ag Page 25 of 57 centeractive User Manual Mirador Release 2 1 Result View Description Arguments Process Name java Result at 2007 07 30 09 56 41 Adjust table to panel Process ID Pr Pare Com vi Class User Mem Peak Page Page java exe 2924 3604 NORMA INT AUT 26152 24716 180606 In order to display the data of a single row in a well structured format on the bottom of the panel select it Double click a row to show the row data in a pop up dialog that looks similar to the o
13. O O O O O O O O O O O O O Created Suspended Swapped Queued Aborted Completed Checkpointed TotalExecution AverageExecution TotalElapsed AverageElapsed MinElapsed MaxElapsed MinExecution MaxExecution MostRecentExecutionTime MostRecentElapsedTime TimeSinceLastUpdate CountSinceReset copyright centeractive ag Page 53 of 57 centeractive User Manual Mirador Release 2 1 6 1 3 PROCESS DEFINITIONS NODE The process definitions contained within a BW engine are hierarchically structured using the process folder node L I The process definitions appear as leaf nodes with a gear icon either directly beneath the engine node or inside the corresponding folder node Process definitions that are linked to a process starter are represented by an additional green arrow pe The process definitions from the BW engine shown in the figure in the previous chapter would be structured as follows G ES BusinessWorks Engines i EE RY RPC i EEA RW RPC 1 i EEA RV RPC 2 i EB invoke_partner ERC jobRecovery g8 Processes lf onStartup process ErrorHandling i pt GenerateError process GC Fail s Ffail amp fterCheckpoint process i ForceFailures process 2 E SubPracesses eg SubPracess 2 process i BD SubProcess 1 process Each process definition has again a number of tabbed panes that let you easily retrieve and display data obtained from the underlying microagents Espe
14. The save button has to be pressed each time you change the application properties otherwise these changes will be lost when you exit the Mirador program Stops running the Mirador program Prior to closing the main window you are asked whether you want to save the current configuration If you confirm by pressing the Yes button the same function gets performed as if you had selected the menu item File gt Save View S Go To Previous Selection Moves to the previous node from the node selection history Go To Next Selection Moves to the next node from the node selection history This button is enabled only in case the Previous button was pressed before As soon as the user actively selects a new node it gets added to the selection history and the Next button gets disabled copyright centeractive ag Page 6 of 57 centeractive User Manual Mirador Release 2 1 Submenu Menu Item Description Save Current View Allows the user to save the current view to a file for later use The user can determine the location and the name of the file The program by default proposes to store the view file in the mirador export views folder located in the user home directory The default file extension is mvw When the current view is saved to a file the Mirador program collects the items listed below and writes them in XML format to the chosen file e All agent collection microagents Current active sub
15. at 2009 11 03 15 00 40 250 000 4 225 000 200 000 175 000 150 000 125 000 4 100 000 75 000 50 000 25 000 a e e POI ero si eros A si os exe sa Process Name ID Process CPU Time Mem Usage Peak Working SetSize Page File Usage Page Fault Count copyright centeractive ag Page 28 of 57 centeractive User Manual Mirador Release 2 1 Result View Description The behavior and configuration of this view is the same as the one of the simple line chart described above The lines however appear in 3D mode Arguments Result at 2007 07 30 11 06 46 97 500 25 000 22 500 20 000 17 500 15 000 12 500 10 000 7 500 5 000 2 500 O ID Frocess CPU Time Mem Usage Page File Usage The bar chart has same characteristics and restrictions as the line chart The different types of values are shown in bars with different values Between categories the data of the same type are shown in bars with the same color Arguments Result at 2007 07 30 11 06 46 27 500 25 000 22 500 20 000 17 500 15 000 12 500 10 000 7 500 5 000 2 500 E lt lt g ID Process M CPU Time E Mem Usage P Page File Usage copyright centeractive ag Page 29 of 57 centeractive User Manual Mirador Release 2 1 Result View Description bar chart 3D The behavior and configuration of this view is the same as the one of the simple bar ch
16. properties copyright centeractive ag Page 8 of 57 centeractive User Manual Mirador Release 2 1 Submenu Menu Item Description Displays the About dialog of the Mirador program 3 1 2 MAIN TOOLBAR The main toolbar contains a number of buttons that are basically shortcuts to menu items they are explained in the table below Button Shortcut to Menu Item e Views Go rari sea SSOSCS S gt View gt ge ronerseet OOOO E Lesen O C Monitoring gt Eno Dicovera Newagene O ref Toot gt inn ndependentdkiog SSS EL ras show Sytem oroperies SSS tia a copyright centeractive ag Page 9 of 57 3 2 TREE NODES centeractive User Manual Mirador Release 2 1 This section explains the different tree nodes in detail The following table gives an overview of the icons that get used in the left located navigation tree to represent single nodes Hawk Environment SEH A Agent Collection L Cluster Node This is a top level node that corresponds to the Hawk environment that s being monitored The node appears red colored E if there are non dismissed console warnings present in its detail view Icon Annotations One or several agents within the monitored Hawk environment have at least one open not cleared notification One or several agents within the monitored Hawk environment have at least one open warning There may also be open notifications One or several a
17. was monitored in a previous session Currently the status of the agent is unknown it may not yet have been detected or it may not be running at all The agent was detected during the current monitoring session but was reported as expired O Agent Node active This node represents a detected and active Hawk agent Icon Annotations One or several agents within the cluster have open non cleared notifications One or several agents within the cluster have open warnings and maybe notifications One or several agents within the cluster have open errors and maybe warnings and or notifications By Schedules Shows the schedules that can be used for determining if a rulebase or part of the rulebase should be in schedule or out of schedule at a given time E Rulebase A single rulebase is shown through this icon Icon Annotations There exist open not yet cleared notifications issued by the rulebase There exist open warnings and maybe notifications issued by the rulebase There exist open errors and maybe warnings and or notifications issued by the rulebase Li Microagent Group Microagents are placed in a group node that is named Microagents by default Depending on the application options and the name of the microagent it gets placed inside a different group node that is created on the fly copyright centeractive ag Page 11 of 57 Microagent Method Group KC Read Method di Write Method
18. 34 of 57 Result View User Manual Mirador Release 2 1 Description The time chart is very similar to a line chart except that the values on the domain axis are dates rather than numbers Through a time chart you can visualize the evolution of microagent method result data from multiple invocations over a certain period of time A time chart is fed by a method subscription that repeatedly provides the data as long as it s active The lower bound field can be used to explicitly define the lower bound of the chart s vertical value axis The value in the duration field determines the time period covered by the chart s data When new data is View Label Column Label Column 2 Value Columns Lower Bound Duration centeractive lf time chart e Datagrams sec O Datagrams Received sec O Datagrams Received Header Errors O Datagrams Received Address Errors O Datagrams Forwarded sec O Datagrams Received Unknown Protocol O Datagrams Received Discarded O Datagrams Received Delivered sec 0 Datagrams Sent sec 0 Datagrams Outbound Discarded O Datagrams Outbound No Route 7 Fragments Receivedisec Fragments Re assembled sec O Fragment Re assembly Failures C Fragmented Datagrarms sec Fragmentation Failures O Fragments Createdsec added to the chart old data that exceeds the defined number of minutes are automatically removed from the chart Arguments Result at 2007 10 14 13 14 45 IP
19. 4gentEventMonitor clean4awaitingInitiall4gentEventMonitor jaya at COM TIBCO hawk console nest console 4gentEventMonitor access 1200 4gentEventMonitor jaya at COM TIBCO hawk console nest console AgentEventMonitort 10 0nTimerl4gentEventMonitor java at Com Dbco tipry TibryTimer firelTibryTimer java pp at Com Dbco Dr Tibry Queue timedDispatch TibryQueue jawa 217 at com Dbco tibry TibryQueue dispatchiTibryQueue java 199 at COM TIBCO hawk console nest console AgenteventMonitork1 runi amp genteyventMonitor java copyright centeractive ag Page 14 of 57 centeractive User Manual Mirador Release 2 1 3 2 2 CLUSTER NODE O Cluster nodes are containers that group a series of agent nodes Every Hawk agent belongs to a cluster whose name can freely be configured please consult the Hawk documentation The default cluster name of an agent is the IP subnet address in which its host computer is located All agents with the same cluster name are shown within the same cluster node New cluster nodes get created upon agent detection if no other agent with the same cluster name was previously detected Cluster nodes disappear if their last agent node is removed by the user The detail view of the cluster node represents all contained agents in form of an icon representing a computer These icons are of different style and color depending on the status of the agent they represent If a mouse click occurs on one of these icons the correspon
20. 711453406E12 USED 0 PROCESS_NAME bwengine exe CPU_TOTAL 1813921 CPU_PERCENT 1 8483333333333334 MEM_USAGE 58660 DEPLOYMENT jobRecovery COMPONENT_INSTANCE Process Archive STATE RUNNING DATA CREDENTIAL 0 0 OUT_OF_SYNC false In a large environment with a high number of BusinessWorks KSE EIERE E SHSHEe JOU May be interested in a limited set of engines Please select the BusinessWorks engines that shall be included in the result Select All Deselect All ke RW RPC ke RY RPC 1 kw R RPC 2 C inwoke_partner only Also for some specific monitoring tasks you may want to limit the number of displayed engines especially if you want to represent their resource consumption in a chart To restrict the number of displayed engines simply click on iw jobRecowery the Define Filter button on top of the result control panel A C queueReceiver dialog will pop up see example and let you select the engines you want to have included in the result table Cancel copyright centeractive ag Page 52 of 57 User Manual Mirador Release 2 1 6 1 2 PROCESS ENGINE NODE centeractive Every deployed BusinessWorks process engine is represented as a package Di node and appears directly beneath the Business Engines folder node E Its detail view contains a series of tabbed panes each of them showing BW engine data of a certain type such as process definitions as shown in the figure below The underlin
21. 75203 30 2007 07 11 20 13 37 Internal AgentMonitor Warning Initial never received for C40001 none default 1181391275203 30 2007 07 11 20 12 07 Internal AgentMonitor Warning Initial never received for CA0001 none default 1181391275205 30 2007 07 11 20 10 37 Internal AgentMonitor Warning Initial never received for CO0001 none default 1181391275203 30 2007 07 11 20 09 07 Internal AgentMonitor Warning Initial never received for CAO001 none defaulk 1181391275203 30 2007 07 11 20 07 37 Internal AgentMonitor Warning Initial never received for CO0001 none default 1181391275203 30 2007 07 11 20 06 07 Internal AgentMonitor Warning Initial never received for CAO001 none defaulk 1181391275203 30 2007 07 11 20 04 37 Internal AgentMonitor Warning Initial never received for CAO001 none default 1181391275203 30 2007 OF eee Console Warning Details Date Time 2007 07 11 20 21 07 Warning Internal AgentMonitor Warning Initial never received for CA000L none default 1181391275203 30 Stack Trace COM TIBCO hawk console hawkeye Consolevarning Internal 4gentMonitor Warning Initial never received for CADDO none default 1181391275203 30 at COM TIBCO hawk console hawkeye AgentMonitor deliverConsoleW arningAgentMonitor java at COM TIBCO hawk console bawkeve AgentMonitor access 500 4gentMonitor java at COM TIBCO hawk console hawkeye AgentMonitor oniInternalConsoleWarningl4gentMonitor jaya at COM TIBCO hawk console nest caonsole
22. O Rulebases E Microagents Custom nu EventLog FileStat Logfile Messaging Performance B Process i _onUnsolicitedMsg E getInstanceCount i E getInstanceCountBy Command EG getProcess E getReleaseVersion E getTraceLevel E getTraceParameters vo setTraceLevel eu setTraceParameters Registry nu RuleBaseEngine GH Self Zi Services amp SysInfo TIBCO Rendezvous E ca0002 CH ca0005 amp ca0007 D vw Mirador Agent centeractive Arguments ke Cluster Names All Agent Names All Process Name jav Result at 2009 11 23 07 52 38 Cluster Agent ca office ca0001 Process N C Adjust table to panel Parent Pr Command CPU Time 4324 C Program Files Java jre6 binjjava exe H 1114 ID Process ca0002 ca0005 ca0005 ca office ca office ca office 3732 C Program Files Javaljdk1 6 0 25421 1088 C Sun SDk jdk binijavaw exe Xms2m 1078 3672 C Program Files Javajjre1 6 0_O7 binjja 1437 ca office Cat 612 C Program Files Java jre6 bin java exe 942859 Table Row Details Cluster Agent Process Name ID Process Parent Process ID Command CPU Time Class User Name Mem Usage Peak Working SetSize Page File Usage Page Fault Count Start time ca office ca0005 javaw exe 1708 1088 CiASun SDK jdk bin javaw exe Xms2m Dadmin port 4848 cp
23. Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubF 2009 10 29 16 48 30 500 Se 10 29 16 48 30515 Call Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubF Call Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes Su Call Process 1 gt Processes SubProcesses SubPracess 1 process Call SubPracess 2 gt Pracesses Su Call Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes Su be Te Tee 10 nn E Ef Te Fe ae be Te Tee AO non E Ef Te Fe MAr Fall Mw ew wn 1 Pe ww wwe we d be han mm ww wm mm em a db F n a wm d eve zm mm wm e d e ll EC ck F n ew mm em Me Mee ow wm mm oI ab n 3 copyright centeractive ag Page 56 of 57 centeractive User Manual Mirador Release 2 1 7 REPORT GENERATION You can generate useful reports from the Hawk agents found in the monitored environment Report generation is defined in the Document Agents dialog that is invoked by selecting the menu item File gt Document Agents from the main menu The same dialog is also shown if you press the button B from the main toolbar Here you can define among other things the Hawk agents you want to document the output format currently only HTML as well as the filename and path of the output file 3 Mirador Report Report properties Title Mirador Report Agents E core bo006
24. RE Transport 7474 7474 Fis Wen Lopes Moser oiire Tod Ten BOO LB sr amp hx Inevaalion Dese Gal PACO Errore ei C Plant 26 Result 278 zi 0 bersara 4 A n telaio Mare E DN s bus Vereen 232 KH La big bee 2006 1002 DI d Joie Weg A Minor T f Sackolfice 5 ipara yemi peA puleto Pink a 007 09 08 de 1344 deier en E pee Ue Bee ee d Sc gattacartyTnfa hy gerber BS Gr in ehr Ever Valus casca oe 6 Raa oH Processor BS Us Tira RS Syren Tina Tire Tile copyright centeractive ag Page 5 of 57 centeractive User Manual Mirador Release 2 1 3 1 APPLICATION CONTROLS 3 1 1 MAIN MENU The main menu is composed by sub menus and menu items as described below Submenu Menu Item Description Show Application Properties Displays the dialog with the application properties that lets the user customize the Mirador program E Document Agents Displays the Document Agents dialog that lets the user document the Hawk agents supported output formats are PDF XLS and HTML Saves the current state of the Mirador session not its view and microagent method subscriptions to the mirador hmo file located in the mirador bin folder located in the user home directory The previous version of the mirador hmo file gets copied to the mirador backup folder with a name of the format lt yyyyMMddHHmmss gt mirador hmo
25. SZ mirador Release 2 centeractive User Manual Mirador Release 2 1 1 CONTENTS MESSE MEHN 4 3 USER NCERFACE scricciolo dla pala 5 3L Application Control nasa 6 3 1 1 Moi 6 Jah Man TOODI EE 9 Ge KE 10 SON Hawk Environment Node 13 a2 Cid 15 3 2 3 ASINO ila 16 3 2 4 Ru lebase Engine Node nesnenin rantena EAEAN TEENETE EEEE EER 16 323 eeh 16 3 2 6 ROLDA E eege 16 3 2 7 Microacent Group Re E 18 3 2 8 IVT OCI NO dici 18 3 2 9 Microagent Method Group Node 19 3210 Microarent IVT EOIN EE 20 3 2 11 Mirador ET 37 39 Aln Dale P TE 38 4 CONFIGURATION AND PERSISTENCY csssscssssccsccccsccscsccsceccssecssssssssssees 40 Al Application Proper E 40 4 1 1 Hawk Environments tee 4 4 1 2 Pia 44 4 1 3 tee 44 copyright centeractive ag Page 2 of 57 centeractive User Manual Mirador Release 2 1 4 1 4 Medline 44 e Savne Work E TE 45 4 2 1 Hawk Environment Confgeuraton 45 4 2 2 Microagent Method Subscriptions 47 5 AGENT COLLECTION MICROAGENTS esseseesescoesescesoscescesoscescesossescesossesceseesee 49 6 ENHANCED CHEN 51 6 1 BusinessWorks Kurt 51 6 1 1 Process Engines Group Node ritardo iaia 52 6 1 2 ProcsEgheNceo cat 53 6 1 3 Process Denmitions EE 54 Z REPORT GENERATION EE 57 copyright centeractive ag Page 3 of 57 centeractive User Manual Mirador Release 2 1 2 INTRODUCTION The Mirador program lets you monitor computer systems in a distributed enviro
26. TEST Communication Channel Rendezvous Rendezvous Service 600 Rendezvous Network Rendezvous Daemon tcp 7600 copyright centeractive ag Page 40 of 57 centeractive User Manual Mirador Release 2 1 4 1 1 HAWK ENVIRONMENTS The Hawk Environments page lets you define the Hawk environments you want to monitor Through the F button and the button you can add or remove single environment definitions The environment definition cannot be removed if it corresponds to the one that is currently selected for monitoring The buttons and let you change the position of environment definitions by moving them up or down The details from the selected table row environment appear on the bottom of the page according to the following description Description Definition Name Every definition must have a distinct name that gets freely assigned by the user Please note that the name cannot be changed if the environment definition corresponds to the one that is currently selected for monitoring Hawk Domain Hawk domains are used if you wish to isolate groups of Hawk agents into independent monitoring sets Communication Channel This lets you select the communication channel Mirador uses to gather information from the monitored Hawk agents and to remotely invoke microagent methods Depending on the options you chose when installing the Mirador program you have the choice between the communication channels Rendezvous
27. a structured view on non structured entities All microagent methods depend directly on a microagent node hence logically they are all on the same hierarchy level The separators used to split microagent method names into group names can be changed in the Microagents panel of the application properties dialog To display the dialog select the menu item File gt Show Application Properties 3 2 10 MICROAGENT METHOD NODE Micoragent methods may expect arguments parameters provided by the user and may return data as the result of the method invocation Methods are named synchronous if they can directly be invoked through the Mirador program Asynchronous methods on the other hand are invoked by the Hawk environment if a certain event occurs To have asynchronous methods interact with the Mirador program the user must subscribe to them You can also subscribe to synchronous methods by providing a time interval this instructs the Hawk environment to invoke and re invoke that method as long as the subscription exists There are special types of microagents where the Mirador program itself orchestrates synchronous subscriptions Such microagents are the ones that get loaded locally on to the inbuilt pseudo agent but also the so called agent collection microagents that are used to collect data from microagents found on different remote agents copyright centeractive ag Page 20 of 57 centeractive User Manual Mirador Release 2 1
28. agent methods synchronous invocations and asynchronous event notification is collected and passed to the Mirador presentation layer in tabular format Every such table has two leading columns named Cluster and Agent respectively which indicate from where each individual table row comes from copyright centeractive ag Page 50 of 57 centeractive User Manual Mirador Release 2 1 6 ENHANCED VIEWS 6 1 BUSINESSWORKS MONITORING Mirador offers a special view on BusinessWorks BW process engines by using certain data retrieved from the TIBCORuntimeAgent microagent COM TIBCO admin TRA and the individual BW process engine microagents COM TIBCO ADAPTER bwengine lt domain gt lt engine name gt Process Archive The original microagents appear unchanged with all their methods as do all other microagents but the program creates additional tree nodes and panels underneath the BusinessWorks Engines folder node d The alternate view only access data from read only microagents where no side effects occur Therefore in order to increase user comfort Mirador automatically requests and shows the current data from the corresponding microagents each time the user navigates to a different node or selects a different panel The data of the current selected panel can also be refreshed manually at any time by activating the top right located invoke button P If you want the data to be refreshed at a fixed interval simply activate the s
29. agent names display name tokens are represented If the checkbox is selected and a name token represents a name value pair with the format lt name gt lt value gt the name part together with the equals sign get removed from the token Microagents to be A list of microagents that should not be structured but simply be excluded contained in the default group node named Microagents When adding new entries to the list please be sure to enter the name of the microagent and not its display name To find out about the name of a microagent simply select the corresponding node in the navigation tree and select the description tab in its detail view the name appears there in the first line Excluding single microagents from being structured can make sense in a case where an otherwise widely useful separator character is contained in the microagent display name and that splitting that name would produce an undesired result The slash separator character for example makes sense to be used for a microagent with the display name TIBCO RepositoryServer ca domain but its use doesn t make sense for the microagent with the display name JMS controller tcp localhost 7222 4 1 4 2 METHOD INVOCATION This box lets you define options related to microagent method invocations Description Result history size This option defines how many rows shall be retained shown in the result table when the historic view gets cho
30. arnings remain in the table until they get actively dismissed by pressing the button located top right of the table The top level Hawk environment node in the navigation tree is shown with red color Ei if the table contains non dismissed console warnings All Alerts Console Warnings Date Time Warning 2007 07 11 20 28 37 Internal AgentMonitor Warning Initial never received for CAO001 none defaulk 1181391275203 30 2007 07 11 20 27 07 Internal AgentMonitor Warning Initial never received for CO0001 none default 1181391275203 30 2007 07 11 20 25 37 Internal AgentMonitor Warning Initial never received for CA0001 none default 1181391275203 30 2007 07 11 20 24 07 Internal AgentMonitor Warning Initial never received for CO0001 none default 1181391275203 30 2007 07 11 20 22 37 Internal AgentMonitor Warning Initial never received for CAO001 none defaulk 1181391275203 30 2007 0 11 20 21 07 Internal AgentMonitor Warning Initial never received for CAO001 none defaulk 1181391275203 30 2007 07 11 20 19 37 Internal AgentMonitor Warning Initial never received for CA0001 none default 1181391275203 30 2007 07 11 20 18 07 Internal AgentMonitor Warning Initial never received for CA0001 none default 1181391275203 30 2007 07 11 20 16 37 Internal AgentMonitor Warning Initial never received for CO0001 none default 1181391275203 30 2007 07 11 20 15 07 Internal AgentMonitor Warning Initial never received for CO0001 none default 11813912
31. art described above The bars however appear in 3D mode Arguments Process Name sY Result at 2007 07 30 11 06 46 27 500 25 000 22 500 20 000 17 500 15 000 12 500 ni AA At las 1164 1232 1380 1456 1644 6 1812 1956 2656 ID Process E CPU Time MM Mem Usage F Page File Usage copyright centeractive ag Page 30 of 57 centeractive User Manual Mirador Release 2 1 Result View Description The pie chart is used to visualize the data proportionately representing a total of 100 era a Therefore the result control box lets you choose belcolume 2 ID Process a single value column with numeric data value Columns ID Process Parent Process ID CPU Ti One of the table columns has to be chosen as CRU time Ce Mem Usage the label column The label column defines the CH Peak Working SetSize name of individual pie segments and must Page File Usage contain unique values over all table rows If the S Ge ee SCH value of the chosen label column is not unique potation eebe the label can be extended and made unique by section Labels the value of a second row Label Column 2 View pie chart The pie can be easily rotated by using the slider control The section labels can be shown or hidden by changing the selection of the related checkbox Arguments Process Name sv Result at 2009 11 03 15 00 40 Mem Usage per Process Name ID Process svchost exe 3216 10
32. can easily replace it with a file from within the mirador bin backup folder Saving the monitored Hawk environments is especially useful should you want to make sure all current displayed agents also get detected during a subsequent Mirador session If one of the agents would not be detected then it would still be shown as being unknown The save button has to be pressed each time you change the application properties otherwise these changes will be lost should your Mirador program unexpectedly terminate When you close the Mirador application through the menu item File Save Environment gt Exit the program also asks you if you want to save the current Hawk environment state see figu re J Shall the current Hawk environment configuration be saved beside Press the Yes button only in case you re i id Cancel sure the current state shall be used as the reference state in further Mirador sessions copyright centeractive ag Page 46 of 57 centeractive User Manual Mirador Release 2 1 4 2 2 MICROAGENT METHOD SUBSCRIPTIONS All microagent method subscriptions from any agent including the Mirador pseudo agent can be saved and easily loaded to one or several agents at any time in the future This feature is commonly used if an identical set of microagent method subscriptions need to be present simultaneously on different agents You would then first define all subscriptions on a single agent and carefully
33. centeractive User Manual Mirador Release 2 1 The Description panel shows a detailed description of the method from its arguments and from the expected result Invocation Description Synchronous method getProcess 4 This method returns process information by process name If the Process Name argument is blank then all processes are returned If a Process Name argument is provided then it serves as a regular expression used to filter the processes returned Argument name Process Name type java lang String description The process name Returns name return type COM TIBCO hawk talon TabularData description columns name Process Name type java lang String description The process name name ID Process type java lang Integer description Process ID or process name Parent Process ID type java lang Integer description Process ID of parent name Command type java lang String description Command line used to start process name CPU Time type java lang Integer description The total CPU time for process in milliseconds user time system time name Class type java lang String description Scheduling priority class of process name User Name type java lang String description User account name of process name Mem Usage p type java lang Integer description Process working set in kilobytes name Peak Working SetSize type java lang Integer description Process peak working set in kilobytes
34. cially within the Activity Hierarchy and the Process Monitor panels you ll see the real benefit of this alternate BusinessWorks view In fact it s not just a view but the data gets retrieved from different microagents aggregated and displayed in a way to give an accurate and quick overview of what s going on copyright centeractive ag Page 54 of 57 centeractive User Manual Mirador Release 2 1 7 6 1 3 1 ACTIVITY HIERARCHY The activities of the selected process definition are shown in a hierarchical structured way Activities must have been executed at least once in order to appear in the structure Subprocess definition nodes with all their activities can be collapsed and expanded individually by clicking the plus minus icon in front of the node You can also expand the entire process definition structure using the top left o located expand all button i or the collapse all button If you have to deal with a very large process definition structure you may also find useful the following buttons el o MO A SH E expands all subprocess definitions that contain an activity whose last return code was ERROR ua med D wu e D e e Gi expands all subprocess definitions that contain an activity whose last return code was WAITING Activities Activity Hierarchy Active Processes Process Monitor ei i if A 7 Activity Activity Executio Error LastRetu MinEla MaxElap mt Max E Rendezvo
35. configure the individual method result views Once the set has been successfully tested simply save the subscriptions from that host to a file and reload them to the other agents of your choice Saving microagent method subscriptions is initiated by selecting the menu item Subscriptions gt Save Choose Agent _ I I I Hawk Agents Subscriptions This opens a dialog that contains a list with OF Mirador Agent all current detected Hawk agents The list also contains the Q ca office can001 Mirador agent should one or several microagents have been er ca office cal005 loaded from the local Mirador plugin directory The user ca office ca0007 now has to select an agent that shall ensure all its method subscriptions are saved to a file The agents that do not have any active subscriptions are grayed out and cannot be selected When the OK button gets pressed another dialog appears where the user can freely choose the name of the target file The program by default proposes to store subscription definition files in the mirador export subscriptions folder The default file extension is sub If the user chooses to overwrite an already exiting subscription definition file its previous version gets copied to the mirador export subscriptions backup folder with a name of the format lt yyyyMMddHHmmss gt lt previous filename gt Saved subscription definitions can easily be loaded through the menu item Subscriptions
36. context If you select an activity from the table all its sibling activities are represented with a yellow background color This useful feature adds clarity especially when parallel execution of subprocesses occurs Activities Activity Hierarchy Active Processes Process Monitor ZB Process History Size C Adjust table to panel Process ID Start Time End Time Duration ms 1007227 2009 10 29 16 48 24 500 2009 10 29 16 46 26 671 1007229 2009 10 29 16 48 24 906 2009 10 29 16 48 29 015 1007231 2009 10 29 16 48 25 406 2009 10 29 16 48 29 562 1007233 2 2009 10 29 16 48 25 921 2009 10 29 16 48 30 015 1007235 2009 10 29 16 48 26 406 2009 10 29 16 48 30 593 1007237 2009 10 29 16 48 26 906 2009 10 29 16 48 31 109 1007239 2009 10 29 16 48 27 406 2009 10 29 16 48 31 562 1007241 2009 10 29 16 48 27 906 2009 10 29 16 48 32 015 4109 1007243 2009 10 29 16 48 26 406 2009 10 29 16 48 32 640 Start Time End Time Duration ms ProcActivity Name 2009 10 29 16 48 27 906 Rendezvous Subscriber 2009 10 29 16 48 27 921 2009 10 29 16 48 29 968 2047 Call Process 2009 10 29 16 48 27 921 Call Process gt Processes SubProcesses SubProcess 1 process Start 2009 10 29 16 48 27 921 list recoverable jobs 2009 10 29 16 48 27 921 Call Process gt Processes SubProcesses SubProcess 1 process Checkpoint 2009 10 29 16 48 27 921 Iteration Group start 2009 10 29 16 48 27 921 2009 10 29 16 48 28 968 Call Process gt Proces
37. croagent node shows a tabbed pane with a description panel that contains the name and description of the microagent For some microagents the detail view contains an additional tab named Attributes that lets you view and edit attributes in a quick mode A closer look shows that microagents do not know about a concept of attributes but they expose methods that may be used for reading and writing an attributes value the attribute accessor methods This concept is based on the properties accessor methods described in the JavaBeans API specification see http java sun com products javabeans docs spec html Mirador analyses all methods of a microagent and provides a field on the Attributes panel in case a method is considered to be an attribute getter method If for that same attribute there is also a setter method the field is made editable and its background color is changed to white Methods with a name that start with _get or _set can also be accessor methods the underscore is used by Tibco to mark attribute accessor methods in certain products that extend Hawk standard functionality The values on the Attribute panel get retrieved from the corresponding microagent methods when the microagent node is selected the first time and each time the node is re selected If you want to refresh the values while the node selection remains unchanged you have to press the refresh button E located top right on the panel copyright centeractiv
38. ction microagents e Current active subscriptions e Al pinned dialogs The user can determine the location and the name of the view file The program by default proposes to store them in the folder mirador export views folder located in the user home directory the default file extension is mvw If the user chooses to overwrite an already exiting view definition file its previous version gets copied to the mirador export views backup folder with a name of the format lt yyyyMMddHHmmss gt lt previous filename gt Persistent view definition can be reloaded during the same session or during any other Mirador session later on through the menu item View gt Load View When reloading a view the Mirador program will first do the following clean up activities if the user confirms the related question e Cancel all active microagent method subscriptions e Remove all agent collection microagents e Close all pinned dialogs The user will then have to choose the file that contains the view definition you may also select a file from within the mirador export views backup folder The view definition file however should have been saved from within the same Hawk environment otherwise the microagent method subscriptions and pinned dialogs cannot be re created copyright centeractive ag Page 48 of 57 User Manual Mirador Release 2 1 centeractive 5 AGENT COLLECTION MICROAGENTS With agent collection microagents you can invoke i
39. dentical microagent methods on a series of remote Hawk agents within the monitored environment and present the return data in a compact form depending on your needs You interact with the agent collection microagent methods just as you would with any other microagent method That way you can create subscriptions that suit your whole network and present result data in form of tables and charts A typical use case would be to display the resource usage CPU time and or memory consumption of a number of servers within a single time chart The agent collection microagent is a Mirador software component that gets defined added by the user through a simple mouse click within the detail view of a mircroagent method node If such a KEE node references a microagent method on a remote node you will see the button E amp that adds a new agent collection microagent to the Mirador program or simply a new method on an already existing aa one Agent collection microagents appear underneath the Agent Collection node Pl that becomes visible only when the first agent collection microagent gets defined Mirador 2 0 ca_domain Domain ca_domain RV Transport 7474 tcp 7474 File Yiew Environment Monitoring Subscriptions Tool Bu pw 2 2 Ts ts x Sea Help Invocation Subscription Description E G ca_domain Environment S Agent Collection G Microagents E amp Process 8 BEE E ca office 4 A Q ca0001 amp
40. ding agent node gets selected in the project tree and the agent detail view will show up The detail view can be detached from its default E Backoffice 5 location and be shown in an independent dialog see example on the right by selecting the menu item Tool gt Pin Detail View In Independent N I E 5 gt DE De Dialog The same action can be triggered by accO0i0 accO0z0 hrooid sec0010 tc0030 pressing the button in the main toolbar This convenient feature lets you quickly move to the detail view of different agents or it can be placed outside the Mirador main window to constantly show the health status of the whole cluster The following table lists the different types of icons with which an agent can be identified Icon Status Description The Mirador program has not yet detected any event from this agent its status is unknown This icon gets used if the represented structure of a monitored Hawk environment was built during the previous monitoring session or it was loaded from a previously stored session The agent is alive and there is no open notification warning or error The agent is alive but it reports at least one open notification no warnings nor errors The agent is alive but it reports at least one open warning but no errors There may also be open notifications copyright centeractive ag Page 15 of 57 centeractive User Manual Mirador Release 2 1 Status Description The agent is ali
41. e ag Page 18 of 57 centeractive User Manual Mirador Release 2 1 The following figure shows a sample Attribute panel that contains fields for three attributes two of them Description and Name are editable The background color of the Description attribute field is gray because it contains multi line text that cannot be edited in the single line field directly but must be edited in a dialog that pops up if a mouse click occurs on the field or the edit button e that appears right of it Attributes Description Description The purpose of the simulator program is to show i I 1265 3 2 9 MICROAGENT METHOD GROUP NODE This tree node optionally groups microagent methods depending on their name The Mirador program does not do any method structuring by default Depending on the user preferences the program checks for certain characters in the method name and uses them as separators to build a group node hierarchy Therefore certain microagent methods are not placed directly beneath the owning microagent node but within a group node or even a branch of group nodes The microagent method with the name mgmt mib 2 interfaces getlfTable for example would be represented as follows E P mgmt G K mib 2 gt Pop interfaces Zu EL getIfTable copyright centeractive ag Page 19 of 57 centeractive User Manual Mirador Release 2 1 Keep in mind that the group node provides
42. e method again at any time in the future If the Subscription panel is no longer used you can remove it by selecting the appropriate menu item from the pop up menu that appears when you right click on the tab copyright centeractive ag Page 24 of 57 centeractive User Manual Mirador Release 2 1 Description ES Clear Historic Restult Table Removes all rows from the historic result table This button appears only if the historic view can be selected in the context of the current panel Clearing the historic view is useful when you have an active method subscription and all previous results from that subscription are no longer of any interest Hide Result Controls Hides the result control box that appears right on the Invocation panel This frees up space for showing the method result LE show Result Controls Displays the result control box right on the Invocation panel and lets you change the result view 3 2 10 1 RESULT VIEW Depending on the method the Invocation as with the Subscription panel let you enter method arguments and they both display the results from synchronous method invocations and or asynchronous event notifications The default look of the result view can be changed within the result control box that appears right on the Invocation and the Subscription panel The following result views can be selected from a combo box within the result control box Result View
43. ebase then the rulebase is always in schedule 3 2 6 RULEBASE NODE E Every rulebase installed on an agent gets represented by such a node optionally decorated with a small icon that represents the status of the rulebase The detail view of a selected rulebase node shows a detailed description of it You cannot create new rulebases or change existing ones through the Mirador program copyright centeractive ag Page 16 of 57 User Manual Mirador Release 2 1 centeractive The example below shows the detail view of the Hawk standard rulebase HawkWindowsEventLog Rulebase HawkWindovwsEventLog author TIBCO Hawk 4 2 0 Release Rules rule test 1 COM TIBCO hawk Ama EventLog on4 pplicationEvent Source TIBCO Hawk Agent expression action clear condition expression action clear condition Type Equals Warning clear after 900 seconds Type Equals Error clear after 900 seconds COM TIBCO hawk Ama Eventlog on4pplicationEvent Source TIBCO Hawk HMA expression action clear condition expression action clear condition Type Equals Warning clear after 900 seconds Type Equals Error clear after 900 seconds COM TIBCO hawk Ama Eventlog on4 pplicationEvent Source TIBCO Hawk Event expression action clear condition expression action clear condition Type Equals Warning clear after 900 seconds Type Equals Error clear after 900 seconds copyri
44. ed blue text in the table and within the row detail view represents a link to another tree node If a mouse click occurs on them the referenced node gets selected This lets you easily navigate between related nodes Status Memory Usage Process Definitions Process Starters Process Count Process Exceptions Locks Recoverable Processes DB Connections Result at 2009 10 29 16 23 23 Table Row Details Name Starter Created Suspended Swapped Queued Aborted Completed Checkpointed TotalExecution AverageExecution TotalElapsed AverageElapsed MinElapsed MaxElapsed MinExecution MaxExecution MostRecentExecutionTime MostRecentElapsedTime TimeSinceLastUpdate CountSinceReset Processes onStartup process Rendezvous Subscriber 69662 O O 0 0 69654 278630 6089439 87 287707689 4130 4000 14265 O 10218 78 4109 foe 69654 C Adjust table to panel Name Starter Created Suspended Swapped Queued Processes onStartup process Rendezvous 69662 0 O 0 Processes Fail Fail4fterCheckpoint process 3 O 0 O Processes ErrorHandling GenerateError process Rendezvous 69686 O O 0 Processes SubProcesses SubProcess 2 process 139320 0 O lo Processes Fail ForceFailures pracess Timer 1 O 0 O Processes SubProcesses SubProcess 1 process 276636 O 0 lo lt ill gt View Label Column Label Column 2 Value Columns O O O O O
45. efault proposes to store the subscription definition file in the mirador export subscriptions folder located in the user home directory The default file extension is Sb Saved subscription definitions can easily be loaded to the same agent or any other agent during the same Mirador session or during subsequent sessions see menu item Load Subscriptions below Load Subscriptions Loads microagent method subscriptions from a file on to one or several agents and starts them The user can choose the target agents from within a dialog The subscriptions on these agents will be created only if the corresponding microagent method can be found there Stop All Subscriptions Stops all active microagent method subscriptions REL I Clean Up GUI Resources Cleans up GUI resources that are currently not visible and are no longeractive This may significantly free up memory Result charts and tables as well as specific node settings will be lost Ef Pinin Independent Dialog Pins the current detail view or part of it i e a tabbed panel in an independent dialog that remains open even if another node gets selected in the Hawk environment tree This function is available for the agent overview of the cluster nodes and for the subscription panels of microagent method nodes Mirador Help This shows the Mirador user manual in a browser window Show System Properties Shows an independent dialog and displays the current system
46. environment can be changed by selecting a different item from within the Environment menu That menu shows all the environments that were defined in the application properties dialog Changing the environment is only possible if the monitoring session is not running The Hawk environment node is responsible for the communication with the Hawk system against which it maintains event listeners It delegates detected events to depending nodes i e agent node which in turn change their appearance to show the new state The detail view of the environment node contains two tabs named All Alerts and Console Warnings respectively 3 2 1 1 ALL ALERTS The All Alerts tab shows a table that contains the whole set of alerts reported by all agents of the current monitored Hawk environment The details of an alert are shown within a panel below the table as soon as an alert row gets selected by the user A detailed description of this panel can be found in the chapter titled Alert Table Panel copyright centeractive ag Page 13 of 57 centeractive User Manual Mirador Release 2 1 3 2 1 2 CONSOLE WARNINGS The Console Warnings has a table that contains warnings issued by the underlying Hawk console Such warnings report some unexpected events that happened while monitoring a Hawk environment Such a warning would appear if you unplug the network cable from the computer that is running the Lef Mirador program W
47. gent has been defined invoke Invokes the microagent method with the argument values if any entered by the user and displays the result unless the method impact is of type Action 8 subscribe Subscribes to the microagent method In case of a synchronous method the user has to enter the Initialize Subscription Please enter the interval to be observed For the method subscription method invocation interval within the pop up dialog as seen in the example Such an interval should Keep previous results be at least 5 seconds Hawk agents usually can t cope with Jen smaller intervals However if the subscription is created on a microagent method from within the Mirador agent also small intervals i e 1 second will be applied correctly In order to free up the Invocation panel for other method invocations or additional subscriptions an independent Subscription panel gets added to the detail view of the microagent method as soon as the subscription is created When an agent expires all subscriptions to its microagent methods are terminated When an expired agent is discovered again during the same monitoring session Mirador automatically tries to re create all the subscriptions that were active when the agent expired WR Unsubscribe Unsubscribes from a microagent method The Subscription panel remains in place after you unsubscribe from a method On that same panel you can subscribe to th
48. gent that acts like a pseudo Hawk agent in the way that it is able to load Hawk microagents present in the directory named plugin If no microagent is present or if none can be loaded this node does not appear in the tree copyright centeractive ag Page 12 of 57 centeractive User Manual Mirador Release 2 1 The following nodes are related to BusinessWorks process engine monitoring They will appear only in case BusinessWorks process engine microagents are present on one or several Hawk agent within the monitored environment Description EF BusinessWorks Engines This folder node contains one or several BusinessWorks BW process engine nods Mirador offers a specialized view on BW engines and allows user friendly access of their data M BusinessWorks Engine This node represents a single BW process engine The node name corresponds to the deployment name BW process engine nodes appear directly underneath the E folder node E initi This folder node is used to hierarchically structure the process Process Definition Folder y p definitions contained in a BW process engine Starter Process Definition This node represents a process definition that is directly linked to a process starter Process Definition This node represents a process definition 3 2 1 HAWK ENVIRONMENT NODE El The top most tree node represents the Hawk environment that is going to be or is already being monitored by the Mirador program The
49. gents within the monitored Hawk environment have at least one open error There may also be open warnings and or notifications This node contains structured agent collection microagents Such microagents are inbuilt components that invoke multiple identical microagents on different Hawk agents and present all results within a single table The Agent Collector node only appears if at least one agent collection microagent has been defined by the user Cluster nodes are containers that group a series of agent nodes The cluster name can be configured on each Hawk agent please consult the Hawk documentation The cluster node shows a number to the right of its name enclosed in parentheses This figure reports the number of agent nodes that are contained within that cluster node Icon Annotations One or several agents within the cluster have at least one open not cleared notification One or several agents within the cluster have at least one open warning There may also be open notifications One or several agents within the cluster have at least one open error There may also be open warnings and or notifications copyright centeractive ag Page 10 of 57 centeractive User Manual Mirador Release 2 1 Description Agent Node inactive This node represents a non detected or inactive Hawk agent Icon Annotations The agent is recognised by the Mirador software because it was detected when the Hawk environment
50. ght centeractive ag Page 17 of 57 centeractive User Manual Mirador Release 2 1 3 2 7 MICROAGENT GROUP NODE This tree node groups microagents depending on their display name The name of the default group node is Microagents By default the Mirador program checks for colons commas dots and slashes in the microagent display name and uses them as separators to build up a group node hierarchy Therefore certain microagents are not placed in the Microagents group but in a specific node or branch If the generated group names are of the lt name gt lt value gt format only the value part is shown by default The microagent with the display name Sample env test release 3 2 6 name Cleaner for example would be represented as follows CO CS Sample 5 E3 test SG 3 2 6 fa des Cleaner Keep in mind that the group node provides a structured view on non structured entities All microagents directly depend on an agent node hence logically they are all on the same hierarchy level The separators to be used to split microagent names into group names and the decision to partially blank out the group name can be changed in the Microagents panel of the application properties dialog To display the dialog select the menu item File gt Show Application Properties 3 2 8 MICROAGENT NODE The microagent node contains a logical group of methods each shown as individual nodes The detail view of the mi
51. hat directory Character Encoding Character encoding used by the TIBCO Rendezvous daemon copyright centeractive ag Page 42 of 57 Method Invocation Customizer Class Alert Description File centeractive User Manual Mirador Release 2 1 Description Name of the Java class that adds simple customized functionality for microagent method invocations within the Mirador program You can automatically set initial argument values disable individual input fields or show them as password fields where the entered characters are replaced by a placeholder character The entered class must implement the Java interface MethodInvocationCustomizer from the package com centeractive mirador custom and it must have a public accessible parameter less constructor its documentation can be found in javadoc format at the following location lt MIRADOR_HOME gt help html javadoc index html Mirador provides a convenient class that s ready to be used It is set by default when a new Hawk environment definition is created The full class name is com centeractive mirador agent microagent DefaultMe thodInvocationCustomizer and it acts as follows In case the name of an argument is user or user name not case sensitive its initial value is set to the same value as the system property named user name In case the name of an argument is password not case sensitive its edit field will not show the entered text but only subs
52. historic view table can be sorted by the Result Timestamp column only The historic view is not available for methods that return tabular data by default copyright centeractive ag Page 27 of 57 Result View User Manual Mirador Release 2 1 Description The line chart is available for methods that return tabular data where at least one of the columns contains numeric data Within the result control box one of the table columns has to be chosen to become the label column The label column makes the distinction between categories of data and must contain unique values over all table rows If the value of the chosen label column is not unique the label can be extended and made unique by the value of a second row Label Column 2 One or View Label Column Label Column 2 Value Columns Lower Bound centeractive line chart Process Mame ID Process ID Process Parent Process ID i CPU Time r Mem Usage kl Peak Working SetSize Page File Usage Page Fault Count Start time Label Orientation pp Mp peppy several columns representing numeric data can be selected to be used as the value columns The lower bound field can be used to explicitly define the lower bound of the chart s vertical value axis The label orientation can be changed through a slider control This is useful where long labels would otherwise be overlaid Arguments Process Name DA Result
53. ht centeractive ag Page 39 of 57 centeractive User Manual Mirador Release 2 1 To avoid high memory consumption due to a huge number of buffered hence non expired alerts Mirador also lets you configure the time after which cleared but not yet read alerts get removed from the tables This time period is important and needs to be defined shorter when the Mirador is not being watched permanently and cleared alerts are not marked as being read on a regular basis Otherwise the Mirador program may run out of memory or it may no longer properly react to monitoring events 4 CONFIGURATION AND PERSISTENCY 4 1 APPLICATION PROPERTIES The basic behavior of Mirador can be customized through the application properties dialog that is invoked by selecting the menu item File gt Show Application Properties from the main menu The je same dialog is also shown if you press the button from the main toolbar Here you can easily define Hawk environments you want to monitor date and time patterns to be shown in the display settings used to structure microagents etc Application Properties awk Environments Hawk Environments Formats Hawk Environment Definitions i Alerts i Microagents Mame Hawk Domain Communication Channel Default RY Transport 7474 7474 DEV DEV RR Transport 7600 7600 MESI TEST RY Transport 7600 tcp 7600 PROD PROD DV Transport 7700 tcp 7700 Definition Name TEST Hawk Domain
54. ivity 144723 A O O O 125 a Call Process gt Processes SubProcesses SubProcess 1 process CallProcess 144720 D O O O 10031 P Sleep 1 SleepActivity 144720 B O 0 O 234 End ProcessGroup 144719 DEAD p o 0 266 E Publish Rendezvous Message RYPubActivity 144718 d O O O 3141 E Sleep SleepActivity 144718 p O 0 O 140 E End ProcessGroup 72355 D O 0 0 79 copyright centeractive ag Page 55 of 57 centeractive User Manual Mirador Release 2 1 6 1 3 2 PROCESS MONITOR The process monitor gives real time information about the execution of BusinessWorks process instances Within the top located table every newly started process instance job appears as a new row with its start time end time and duration The top right located combo box Process History Size determines how many rows are shown in the table Old process instances are discarded automatically if a new instance exceeds the selected number The process monitor can be started by activating the start button el A running process monitor can be stopped again if you activate the stop button CH If you select a process instance row from the table you can follow its execution path within the panel that appears at the bottom of the panel Every executed activity gets listed together with its start time and also its end time and duration where applicable Processes often call subprocesses through multiple levels indentation is used to show the activity names in the correct
55. ne shown below Table Row Details Process Name java exe ID Process 2924 Parent Process ID 3604 Command C Program Files Java jre1 5 0_06 binjjava exe Mrs cp Cyftibco ems clientsfavasims jar C tibcofems chents java tibjms gargCit CPU Time 11749 Class NORMAL PRIORITY_CLASS User Name NT AUTHORITY SYSTEM Mem Usage 25 80 Peak Working SetSize 26152 Page File Usage 24716 Page Fault Count 150606 copyright centeractive ag Page 26 of 57 Result View centeractive User Manual Mirador Release 2 1 Description Other than the default view the historic view does not overwrite previous results each time a method is invoked Up to a certain number of results from different method invocations are kept and displayed in a table together with a timestamp The maximum number of retained results can be configured within the Microagents panel of the application properties dialog menu item File gt Show Application Properties Arguments Process Name java Last Result at 2007 07 30 10 33 11 Adjust table to panel Result Timestamp Process Mame Process Count java OOF 04 20 10 32 06 453 007 0730 10 32 07 328 007 07 30 10 32 15 765 007 07 30 10 32 17 546 00 07 30 10 32 33 875 00 7 07 30 10 32 42 562 007 07 30 10 33 11 031 mu to lt a Po Bo a Bo Po Bo a Po CH CH K mo CH p D mo Pd CH On Li E KEN apoyo yoyo yay DT a lt X ao a The
56. ngs match the values from the attributes Cluster Names and Agent Names If those remote methods return data this data is first collected and then passed to the Mirador presentation layer When a subscription is created on a synchronous agent collection microagent method Mirador orchestrates the subscription and invokes the agent collection microagent method repeatedly by observing the specified interval The requests get forwarded to the corresponding microagent method on all active agents where the settings match the values from the attributes Cluster Names and Agent Names at the time of every individual method invocation When a subscription is created on an asynchronous agent collection microagent method a corresponding remote subscription is created on all agents if their settings match the values from the attributes Cluster Names and Agent Names Results from asynchronous methods that arrive in form of notification events will always contain data from the Originating agent only When a remote agent expires its subscriptions are cancelled as soon as such an agent is alive again the Mirador program tries to re create the corresponding remote subscription This also applies if anew agent gets detected and its settings match the values from the attributes Cluster Names and Agent Names the Mirador program also tries to create a new remote subscription All response data if any from remote micro
57. nment It offers easy to use and convenient functionality to directly invoke remote methods and to show the result in different views such as tables forms and charts The program enables you to subscribe to events that may occur at any place within different networks Mirador uses TIBCO Hawk application programming interfaces In order to understand the Mirador program and the way it interacts with the TIBCO Hawk system it is recommended to be familiarized with the concepts of TIBCO Hawk It is not advisable to use the Mirador program as the sole monitoring and alerting console in a production environment The robust Tibco Hawk standard applications should primarily be used The Mirador program is a complementary tool that adds great benefit in terms of visualization debugging and testing of the overall monitoring solution The Mirador program cannot be used for creating new Hawk rulebases and schedules or editing existing ones copyright centeractive ag Page 4 of 57 centeractive User Manual Mirador Release 2 1 3 USER INTERFACE The Mirador program offers a customary structured user interface that has a menu and a toolbar located on its top On the left hand side a navigation tree appears that represents the structure of the monitored Hawk environment Right of that tree you see the detail view of the current selected tree node Some detail views can be pinned in separate dialogs T Mackedfice 9 E Mirador 1 2 PRID
58. ponding Hawk agent Level The level is also known as the alert severity The following values can appear Notification Low Medium and High As stated above the level is also represented by the background color of the table row The time the alert was generated The rulebase that generated the alert Alert Text The generated alert text A small toolbar appears right top of the alert table It contains the following buttons Button Description Si Export to Excel Exports the alerts from the alert table to an excel file defined by the user Ul Suspend Pops up the dialog shown below and lets the user suspend the selected alert for a number of minutes depending on his choice The default reason got suspended by user may be overwritten in order to clearly state why a particular alert got suspended Suspend Alert Alert ID 8 Time s minutes Reason got suspended by user os Mark All Cleared Marks all currently cleared alerts from the table as being read by the user As Read Mark All As Read Marks all alerts from the table as being read by the user Depending on the Hawk environment being monitored a high number of alerts may be generated These alerts remain buffered in the Mirador program until they expire Alerts expire a certain time after they were cleared and read by the user this time period can be changed in the application properties dialog within the Alert panel copyrig
59. r how much time in minutes cleared alerts shall after be removed from the alert tables regardless of whether the alerts are already marked as being read by the user An internal worker process repeatedly goes through all buffered alerts and checks whether the defined number of minutes has expired since an alert was cleared Each time the worker process has checked all alerts it waits a few seconds before it starts checking them again 4 1 4 MICROAGENTS This panel lets you customize both the structure of microagent nodes within the Hawk environment tree andhow certain microagent method results are displayed 4 1 4 1 MICROAGENT STRUCTURING copyright centeractive ag Page 44 of 57 centeractive User Manual Mirador Release 2 1 This box lets you define the way microagents get structured in the Hawk environment tree A detailed description of how microagents get structured and represented by the Mirador program can be found in the section 3 2 7 Microagent Group Node Description Hierarchically structure If this checkbox is selected the microagents get hierarchically microagents structured according to the settings in the other fields within this box If the checkbox is not structured all microagents appear on a same hierarchy level within the default microagent group node tokens from which the hierarchy structure is derived Omit name part This checkbox indicates how individual microagent group names and micro
60. scriptions e All pinned dialogs Such a persistent view definition can be reloaded during the same session or during any other Mirador session later on see menu item Load View below Load View Allows you to choose a view definition file and it s reloaded Such a view file must have been saved at some previous point through the menu item Save Current View described above The view definition file should have been saved from within the same Hawk environment otherwise the microagent method subscriptions and pinned dialogs cannot be re created The Environment sub menu shows all Hawk environments configured within the Mirador program lt Environment 1 gt New environments can be added and existing ones can be changed in the application properties dialog Hawk Environments panel The current selected environment is lt Environment n gt marked by the symbol The environment can be switched only if monitoring is not running Monitoring o Starts monitoring the current selected Hawk environment LI Stop Stops monitoring the current selected Hawk environment Enable Discovering New Agents Enables discovering of new Hawk agents As long as no agents appear in the Hawk environment tree discovering new agents is automatically enabled lt Environment 2 gt Enabling discovering new agents does not actively try to discover running agents Ratherit would only discover agents that star
61. sen within the result control box of a microagent method invocation panel 4 2 SAVING WORK SETTINGS Beside the settings available in the application properties dialog described in the previous chapter Mirador lets you save different aspects from your current defined workspace to files for further use 4 2 1 HAWK ENVIRONMENT CONFIGURATION copyright centeractive ag Page 45 of 57 centeractive User Manual Mirador Release 2 1 The current Hawk environment state with all clusters and agents visible in the navigation tree is saved to the mirador hmo file located in the mirador bifaj folder located in the user home directory This happens each time you press the save button or when you select the menu item File File gt Save The cluster and agent nodes in unknown state of the selected Hawk environment are re established as soon as you re launch the Mirador program or when you switch to another environment through the Environment menu Prior to start actively monitor your environment you ll already know what agents were there when you saved the environment last time The stored Hawk environment configuration can be considered to be a reference composition When saving the state of the hawk environment the previous version of the mirador hmo file initially gets copied to the mirador bin backup folder with a name of the format lt yyyyMMddHHmmss gt mirador hmo If you unintentionally overwrite the mirador hma file you
62. ses SubPracesses SubProcess 1 process Call SubProcess 2 2009 10 29 16 48 27 937 tration Grouplerd 2009 10 29 16 48 27 937 Call Process gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubPrc 2009 10 29 16 48 28 437 Call Process gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubP 2009 10 29 16 48 28 437 Call Process gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubP 2009 10 29 16 48 28453 Call Process gt Processes SubProcesses SubPracess 1 pracess Call SubProcess 2 gt Processes SubP 2009 10 2916 48 28968 Call Process gt Processes SubProcesses SubProcess 1 process Publish Rendezvous Message 2009 10 29 16 48 28 968 2009 10 29 16 48 29 968 1000 Call Process gt Processes SubProcesses SubProcess 1 process Sleep 2009 10 29 16 48 29 968 Call Process gt Processes SubProcesses SubProcess 1 process End 2009 10 29 16 48 29 968 2009 10 29 16 48 32 015 2047 Call Process 1 2009 10 2916 48 29968 Call Process 1 gt Processes SubProcesses SubProcess 1 process Start 2009 10 29 16 48 29 968 Call Process 1 gt Processes SubProcesses SubProcess 1 process Checkpoint 2009 10 29 16 48 29 984 2009 10 29 16 48 31 015 Call Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 2009 10 29 16 48 29 984 Call Process 1 gt Processes SubProcesses SubProcess 1 process Call SubProcess 2 gt Processes SubF Call
63. sfully loaded microagents appear as dependants of the top level node Mirador Agent 7 The Mirador Agent node appears below the Hawk environment node in the navigation tree Microagents of the Mirador Agent are presented the same way as those belonging to Hawk agents The interaction with microagents managed by the Mirador Agent works exactly the same as the interaction with microagents managed by any Hawk agent You can invoke methods or subscribe to them The Mirador Agent is meant to be used during development and testing of custom microagents it provides a straightforward way to check the correct behavior of these software components Unlike Hawk agents the Mirador Agent does not contain rulebases and it does not provide an interface to applications using the Hawk Application Management Interface AMI copyright centeractive ag Page 37 of 57 centeractive User Manual Mirador Release 2 1 3 3 ALERT TABLE PANEL The alert table panel shows alerts and notifications that are generated by the rulebases installed on the Hawk agents of the monitored environment Such a panel appears in the detail view of each individual agent node it contains alerts and notifications that were issued by this particular agent The detail view of the top level Hawk environment node also contains an alert table panel see below that shows alerts and notifications from all monitored agents All Alerts Console Warnings Cleared Level Ti R
64. t running from thismoment on W Disable Discovering New Agents Disables discovering of new Hawk agents This would still discover Hawk agents that appear in the navigation tree but were not yet discovered in the current session Subscriptions The Subscriptions sub menu contains menu items related to Hawk microagent method subscriptions copyright centeractive ag Page 7 of 57 centeractive User Manual Mirador Release 2 1 Submenu Menu Item Description lt Microagent method path 1 gt This is a dynamic list of tree paths to microagent methods that have an active subscription If a microagent has more than one active subscription it only appears once in the list lt Microagent method path n gt The unix type of tree paths start with the name of the cluster followed by the agent and every dependent node name down to the final microagent method name each of these names are separated by a slash An example of such a tree path could be TEST CLUSTER tst0034 Microagents Self getUp Time lt Microagent method path 2 gt If the current selected tree node is a microagent method node with that has one or several subscriptions its path within the list is marked by the symbol v Save Subscriptions Saves all microagent method subscriptions from one agent to a file The user has to select the agent of his choice from a dialog and he can freely choose the name of the target file The program by d
65. teAccessServer 4 run RemoteAccessServer java at java lang Thread run Unknown Source As explained above the result of a method invocation or a method subscription can be shown in different chart types All these charts are displayed together with a legend that may look like the example below Parent Process ID CPU Time Mem Usage Peak Working SetSize Page File Usage If you move the mouse pointer over a gm Series Properties legend and you observe that it turns into a Line Width hand cursor you can further adapt your oe chart Simply click on a legend item i e Swatches Hse CPU Time in order to open the Series Properties dialog shown right This dialog lets you change the color of the series represented by the legend item When working with line charts and time en ee charts you can also adapt the width of a line that represents a specific series Preview D C D Sample Text Sample Text E LJ C Sample Text Sample Text copyright centeractive ag Page 36 of 57 centeractive User Manual Mirador Release 2 1 3 2 11 MIRADOR AGENT Mirador acts as a pseudo Hawk agent in a way that it can load user defined Hawk microagents from a plug in directory At program start up Mirador automatically scans the plugin folder located in its installation directory and tries to load the microagents defined by the hma files service microagents are not loaded Succes
66. titution characters After each successful method invocation or creation of a subscription the class caches the entered attribute values and sets them as initial value to identically named arguments where method invocation panels are visited for the first time Where the microagent method descriptor specifies itself a default value for an argument above specified cases are overruled and the default value is set initially instead Full path of the XML file that contains further description of alerts issued by Hawk rules The format of such a file has to comply with the XML schema defined in the file HawkAlertDescription xsd which is located in the resource folder within the Mirador installation directory Maintaining and using such a file considerably improves the usefulness of Mirador as it immediately provides the user with information about alerts their context and possible solutions A detailed description and measures actions to be taken can be defined for any alert The alert defined in Hawk rulebases and corresponding entry from the XML file are linked by an alert ID If this ID prefixed by a S appears at the beginning of the alert text Mirador retrieves the description if any from the XML file and shows it to the user upon request Simply press on the EP button that appears on the alert detail panel right of the alert title copyright centeractive ag Page 43 of 57 centeractive User Manual Mirador Release 2 1
67. ubscribe button up and define the interval in seconds The different result views historical bar charts pie charts time charts etc are also available on most panels the same as in the standard microagent view copyright centeractive ag Page 51 of 57 User Manual Mirador Release 2 1 6 1 1 PROCESS ENGINES GROUP NODE centeractive The BusinessWorks Engines folder node E groups all detected BW process engines Its detail view contains a summary with useful resource data from all depending BW process engines Their status CPU and memory usage for example is visible on the fly Engine Resource Usage Result at 2009 10 29 16 30 01 ke C Adjust table to panel ID USAGE_P USED PROCESS CPU_LTOTAL CRU PER MEM_USAGE DEPLOYMENT We ee 1340 1 25671145 0 bwengine exe 282203 0 18333333 48720 RV RPC 2 4428 1 25671145 0 lbwengine exe 284218 0 33833333 61508 IRV RPC 1 Label Column 2948 1 25671145 0 bwengine exe 31203 0 07833333 42444 invoke_partner Label Column 2 4900 1 25671145 0 bwengine exe 14421 lo 0 34488 queueReceiver Value Columns USAGE_PERCENT 1468 1 25671145 0 bwengine exe 1813921 1 84833333 56660 jobRecovery USED 4488 1 25671145 0 bwengine exe 258562 0 20833333 59932 RY RPC CPU TOTAL CPU_PERCENT MEM_USAGE CREDENTIAL Table Row Details TYPE INSTANCE ID 1468 USAGE PERCENT 1 256
68. ulebase Alert Text E cp The IP a Alert Details Alert ID 13 generated at 2007 07 11 18 42 17 Alert Text Processor Load is at 99 261537231656397 Cleared Info Clear Time 2007 07 11 18 43 17 Reason test evaluated to FALSE Alert Context Agent rosario DAS none IP address 10 12 12 101 Hawk domain default Os Windows XF The alert table panel initially just shows the table with the alerts and notification each of them in a separate row As soon as a row gets selected by the user its details are displayed in a section below the table within the fields Alert Text Cleared Info and Alert Context These details can also be shown in a separate dialog by double clicking on a row The background color of each table row corresponds to the alert severity level according to the following list Notification copyright centeractive ag Page 38 of 57 centeractive User Manual Mirador Release 2 1 The individual alert table columns are explained below Column Name Description Read Indicates whether the alert has already been read by the user An alert is marked as read if the user clicks inside the Read cell or if he displays the alert data in the alert detail dialog The alert detail dialog gets shown if you double click on an alert row Cleared Indicates whether the alert is already cleared You cannot clear an alert yourself through the Mirador program this is an event issued by the corres
69. unique values over all table rows If the value of the chosen label column is not unique the label can be extended and made unique by the value of a second row Label Column 2 View Label Column Label Column 2 Value Columns Rotation Section Labels centeractive multiple pie chart Process Mame ID Process ID Process C Parent Process ID CPU Time Mem Usage Ww Peak Working SetSize iw Page File Usage Page Fault Count C Start time be As with the simple pie chart you can rotate the pies and show or hide their section labels Arguments Process Name sv Result at 2009 11 03 15 00 40 svchost exe 1936 svchost exe 1220 svchost exe 2008 spoolsv exe 344 svchost exe 672 svchost exe 3216 svchost exe 584 stacsv exe 384 CPU Time Mem Usage Peak Working SetSize Page File Usage Page Fault Count copyright centeractive ag Page 33 of 57 centeractive User Manual Mirador Release 2 1 Result View Description multiple This view is identical to the multiple pie chart described above except that the pies pie chart 3D appear in 3D mode You can also rotate the pies and show or hide their section labels An additional slider from the result control box lets you change the depth of the 3D pies Arguments Process Mame svchost exe Result at 2007 07 30 11 14 59 CPU Time Mem Usage Page File Usage copyright centeractive ag Page
70. us Subscriber ProcessGroup 72364 O 0 O O 63 j Call Process gt Processes SubProcesses SubProcess 1 process CallProcess nn pb 0 gt Start ProcessGroup 289444 np O 188 E Checkpoint Checkpoint 10031 E End ProcessGroup 289435 4 Call SubProcess 2 gt Processes SubProcesses SubProcess 2 process CallProcess 144723 E Start ProcessGroup 144723 E Sleep SleepActivity 144723 o o oa N CH GA _ N n CH o CH uy IS af Call Process gt Processes SubProcesses SubProcess 1 process CallProcess 144721 E Sleep 1 SleepActivity 144720 End ProcessGroup 144719 E Publish Rendezvous Message RVPubaActivity 144719 E Sleep SleepActivity 1144719 CH N GA gt CH CH N CH N CH n _ N n CH a CH J N N mx GA Val T Aa a Se Se Se Se Se Se Se Se TST Ss E list recoverable jobs EngineCom gt Iteration Group start LoopGroup 72363 i DEAD 0 0 62 E Iteration Group end LoopGroup 72363 0 O O 0 313 j Call Process 1 gt Processes SubProcesses SubProcess 1 process CallProcess 72359 p O O O 10171 Start ProcessGroup 289443 O O 0 O 188 Checkpoint Checkpoint 289443 O 10031 End ProcessGroup 289434 DEAD 0 203 amp Call SubProcess 2 gt Processes SubProcesses SubProcess 2 process CallProcess 144723 0 WAITING 0 6 oO wem E Start ProcessGroup 144723 p O 0 O 62 E Sleep SleepaAct
71. ve but it reports at least one open error There may also be open notifications and warnings The agent doesn t send heartbeats anymore The agent is no longer running or there is a problem with the network connection 3 2 3 AGENT NODE Agent nodes in the tree are represented by an electric bulb If the bulb looks like being switched on the Mirador program still receives heartbeat messages that indicate that the agent is alive If the bulb is switched off the agent state is unknown because heartbeat messages are no longer being received The agent or even its host computer may not be running anymore or there may be a problem with the network connection The detail view of the agent node shows a table with notifications and alerts issued by the agent 3 2 4 RULEBASE ENGINE NODE D This node contains all rulebases deployed on the agent to which it belongs When an agent is newly detected its rulebases are not known immediately but their existence gets announced through notification events Therefore the rulebase repository node only gets dependent rulebase nodes added shortly after agent discovery Some agents do not have any rulebases installed hence the rulebase repository node will not contain any rulebases 3 2 5 SCHEDULES NODE a ii n i Ri Schedules can be used for determining if a rulebase or part of the rulebase should be in schedule or out of schedule at a given time If a schedule is not specified in a rul

User Manual - centeractive

Contents

Download Pdf Manuals

Related Search

Related Contents