Getting Started - Community RTI Connext Users
Contents
1. File View Publish Subscribe 48 RTI Shapes Demo Domain 0 Controls Help Output Legend Please select Configuration under controls and click Start In one instance of Shapes Demo create a reliable square publisher as follows a Select Publish Square b Choose the profile MonitorDemoLibrary MonitorDefault c Make sure the Reliability box is checked d Select OK In the other instance of Shapes Demo create a reliable square subscriber as fol lows a Select Subscribe Square b Choose the profile MonitorDemoLibrary MonitorDefault c Check the Reliability box d Select OK 1 The Configuration dialog may not appear at start up if you invoke Shapes Demo with the dataType 3 2 lt Shape ShapeExtended gt command line option Showing System Topology Sample Counts and Rates 4 Start Monitor On a Windows system double click lt installation directory gt scripts rtimon itor bat in your browser Or on a Linux system run the rtimonitor script gt lt installation directory gt scripts rtimonitor When Monitor starts you will be prompted to enter a domain ID If you used the default domain ID 0 when you started Shapes Demo enter 0 at the prompt Otherwise enter the same value you used when starting Shapes Demo Review the system topology a Expand the Physical View tree by clicking the button below the Physical View2. To enable a Connext application to provide monitoring data to Monitor the application needs to use the Monitoring Library plug in Connext notifies Monitoring Library every time an entity is created deleted or a QoS is changed Monitoring Library also periodically queries the status of all entities Monitoring Library sends all the data to Monitor once it gets the data from the Connext application Monitoring is enabled in the application by setting values in the DomainParticipant s PropertyQosPolicy programmatically or through an XML QoS profile Refer to the Monitoring Library Getting Started Guide included with the Monitoring Library bundle for details Monitoring Library is available from the RTI Support Portal accessible from https support rti com Chapter 2 Installation and Start Up 2 1 Instructions for Linux Systems 2 1 1 Installing Monitor is included with RTI Connext Messaging Use the installation instructions in this chapter only if you are installing Monitor independently not as part of RTI Connext Mes saging 1 Untar RTI_Monitor lt version gt Linux targz in a directory where you have write access For example enter gt cd opt rti gt gunzip RTI_Monitor lt version gt Linux tar gz gt gtar xvf RTI_Monitor lt version gt Linux tar The resulting installation will be in opt rti RTI_Monitor_ lt version gt 2 See Installing the License File Section 2 3 3 Monitor is designed to monitor C
3. initial DomainIds 31 32 Default If not specified you will be prompted to enter a domain ID when Monitor starts matchRefreshPeriodSeconds lt seconds gt Specifies the period at which to refresh the system overview panel s matches Default 5 seconds notificationHistoryDepth lt value gt Specifies the number of notifications to keep per entity Default 12 notifications pruneDeadObjectsPeriodSeconds lt seconds gt Sets the period at which Monitor should clean up user interface objects such as the Host and Process nodes in the tree views that are no longer current have no more children nodes in the tree view This value should be increased when dealing with very large systems where the time to complete discovery is lon ger than the default value of 3 seconds Default 3 seconds 2 4 Command line Options Table 2 1 Command line Options Option Description Instructs Monitor to use multiple threads according to the number of cores on the host to retrieve data from its DataRead ers which contain monitoring data This is typically onl spawnReadThreads 8 ypica y y needed for very large systems Default Not specified use a single read thread to retrieve data at a period of 1 second verbosity lt value gt Sets the verbosity for Monitor and the Connext Core Libraries 0 silent both Core Libraries and Monitor 1 errors both Core Libraries a
4. Showing a Samples Rejected Scenario c Check the Reliability box d For the Read method to use select Take e Select OK 5 Notice that the subscriber is not receiving all the samples Let s see why a Select the Expand All button for the Physical View tree in Monitor b In the Physical View tree select the DataReader then select the Status Panel button from the toolbar c Select the Advanced display mode Notice that the Total Count values for Samples Lost and Samples Rejected are non zero This indicates that not all samples are being received Samples Lost and Samples Rejected are both yellow to indicate that this may or may not be a problem depending on your use case Also notice further down under DataReader Cache that both Sample Count and Sample Count Peak are 2 you will see why this is significant later Samples Lost Samples Rejected Total Count 125s a7 Total Count Last Reason Liveliness Changed Last Instance Handle cac217c3 18363f8e f1160eee def9e886 Alive Count 1 A0 Requested Incompatible QoS Not Alive Count 0 A0 Total Count 0 40 Last DataWriter GUID c0a80167 1e54 3 80000002 Last Policy Id Invalid Policies Requested Deadlines Missed a CAA DataReader Cache oe 49 Sample Count Last Instance Handle Sample Count Peak d In the Physical View tree select the DataReader then select the Description Panel button from the toolbar File Domain Actions W
5. 2012 Last Update Wed Aug 08 22 50 25 EDT 2012 Update Period 5 0 seconds Update Period 5 0 seconds DataReader Statistics DataReader Statistics Sample Statistics _ _ r Sequence Numt Sample Statistics Sequence Nut Received Count 107 945 A80 First Available Sar Received Count 1 819 A20 First Available Received Bytes 8 203 820 AR O8t7 Received Bytes 138 244 A 1 520 Duplicates Count A0 tast Available Sar Duplicates Count 0 A0 LastAvailable Duplicates Bytes 0 40 Duplicates Bytes 0 40 f Filtered Count 0 40 Last Committed S Filtered Count EO E Filtered Bytes 0 40 t Filtered Bytes 0 40 u i ncommitted S Rejected Count 0 40 Uncommited ga Rejected Count 0 40 Delta value shows the change for the update period 15 Let s see how to save the current data to be used for future analysis a Select the Save Data button in the toolbar File Domain Actions Window Help oo ao AGS KE Swat earra Save Data b Select a location and enter a filename in the file dialog c Close the third instance of Shapes Demo the one started with pubInterval 250 that is publishing yellow squares Showing System Topology Sample Counts and Rates d In the remaining two instances of RTI Shapes Demo select Controls Delete All No shapes publications or subscriptions should be running in the system now e Select the Load Data button from the toolbar File D
6. 4 1 4 2 Debugging Problems with Monitor on Windows System If you run Monitor on a Windows system and it is not showing any error messages but the Monitor window is not showing up or you are not seeing any data in the Monitor window you can modify the file lt installation directory gt scripts rtimonitor bat to change javaw exe to java exe so that error messages will be displayed in a command prompt to help you debug the issue Running Monitor on a System with Limited Memory Monitor runs with Java and a default maximum Java heap size of 500m If you are moni toring on a system with very little memory and you are only monitoring a very small system you may be able to reduce memory usage by modifying the file in lt installation directory gt scripts rtimonitor bat on Windows systems or lt installation directory gt scripts rtimonitor on Linux systems to decrease the maximum Java heap size usage For example in the script change Xmx500m to Xmx300m Monitor will save some history of statistics to be displayed in the charts By default this value is 12 If you are running on a system with limited memory you can decrease this value with the command line option historyDepth lt value gt see page 2 4 4 1 6Buyoousejqnoll y Troubleshooting 4 3 4 4 4 2 Running Monitor with a Large System Monitor runs with Java and a default maximum Java heap size of 500m If you are moni toring a
7. 7 Prepare for the next demo a In one instance of Shapes Demo select Controls Delete All b Close the other Shapes Demo instance Showing a Samples Rejected Scenario 1 Configure the existing instance of Shapes Demo to use the profile MonitorDemoLibrary SamplesRejectedScenario a Select Controls Configuration Stop b Choose the profile MonitorDemoLibrary SamplesRejectedScenario c Select Start Create a reliable square publisher with the MonitorDemoLibrary SamplesRe jectedScenario profile a Select Publish Square b Choose the profile MonitorDemoLibrary SamplesRejectedScenario c Make sure the Reliability box is checked d Select OK Create a new Shapes Demo instance with a reliable subscribing rate of 1 000 ms For example on a Windows system open a command prompt and enter the fol lowing replacing the installation directory to match your system gt cd lt Shapes Demo installation directory gt gt scripts rtishapesdemo bat subInterval 1000 Or on a Linux system enter the following replacing the installation directory to match your system gt cd lt Shapes Demo installation directory gt gt scripts rtishapesdemo subInterval 1000 In the new Shapes Demo instance create a reliable square subscriber that uses take and the MonitorDemoLibrary SamplesRejectedScenario profile a Select Subscribe Square b Choose the profile MonitorDemoLibrary SamplesRejectedScenario
8. Data tab in the Description Panel iescri E System gt Host BOCAGRANDE 1t com gt Process 7020 gt DP 02 Subscriber gt DR Square ee Field v builtin topic data 8 key c0a80167 1b6c 2 80000007 D participant_key c0a80167 1b6c 2 1c1 5 topic name Square P type_name ShapeType v RE durability D kind VOLATILE_DURABILITY_QOS P direct_communic true v deadline period infinite v A latency_budget P duration 0 0 seconds M Ai liveliness P kind AUTOMATIC_LIVELINESS_QOS lease_duration infinite v RE reliability kind RELIABLE_RELIABILITY_QOS ES c Scroll down to see the content filter expression under builtin topic data content_filter_property filter_expression and builtin topic data content_filter_property expression_parameters 5 Prepare for the next demo a Close the Description panel b In the two instances of Shapes Demo select Controls Delete All A Demo using RTI Shapes Demo 3 3 3 18 Showing Deadlines The steps in this section assume you are using the same profile used in Section 3 1 for the two instances of Shapes Demo 1 In one instance of Shapes Demo create a reliable square publisher with a 100ms deadline a Select Publish Square b Make sure the Reliability box is checked c Set Deadline to 100 d Select OK In the other instance of Shapes Demo create a reliable square subscriber wit
9. Measurement Measurement Scale No Sd v FR BOCAGRANDE tti com v E Process ID 7020 Key Selected 0 Y amp DomainParticipant RTI Monitoring Y 9 Topics Display Name Controls Square Square ShapeType Host Terse x Topic Terse 2 DataReader Terse v F Subscriber t gt DataReader Square ShapeType Process ese i Subscriber Terse i Datawriter Terse v E Process ID 7764 DomainParticipant Terse ina Publisher Terse wy All Terse Y amp DomainParticipant RTI Monitoring h Y Topics Mire P Square Square ShapeType v Publisher OO z gt DataWriter Square hart Time Range minutes Yrs rrcr er eperereeeerpeereeeere penne eee ep ee ener H ITE CHF CFI ACFC 1 6 2 123 2 H 3 System Metrics Domains 1 Hosts 1 Processes 2 Participants 2 Topics 1 Publishers 1 DataWriters 1 Subscribers 1 DataReaders 1 Notes e To change the scaling of the numbers indicated in the color map use the Scale drop down menu e Move the mouse over the entities in the map to see a tooltip of the actual value e You can select different Display Name Controls for each kind of entity or all entities to control how much detail will appear in the map in the Sys tem Overview panel You can either Hide an entity kind show a Terse form of the entity name or show the full Name g Close the System Overview panel Showing System Topology Sample Counts and Rates h In the Physical
10. Requested Dead li Missed il Requested Deadlines Missed ines Missed you will see a i non zero Total Count high macom 2 906 420 lighted in yellow You may notice that the DataWriter s Offered Deadlines Missed Total Count is different than the DataReader s Requested Deadlines Missed Total Count That s because these entities were created with different deadline values 100ms for the writer 250ms for the reader e Close the Status panel 3 19 owad A Demo using RTI Shapes Demo 5 Look at the notifications a In the Physical View tree select the DataWriter then select the Notifications Panel button in the toolbar File Domain Actions Window Help Ab sos paga Suis LES Create a new Notifications panel The Notifications panel displays the selected entity s current status and a his torical list of all alarm statuses related to the selected entity c0a80167 1e54 2 80000007 Thu Aug 09 00 00 29 EDT 2012 Historical Problems Last Update Thu Aug 09 00 00 24 EDT 2012 State r Reasons Wed Aug 08 23 58 59 EDT 2012 Wed Aug 08 23 58 54 EDT 2012 b Close the Notifications panel 3 20 Showing Deadlines c Select the All Notifications Table button from the toolbar File Domain Actions Window Help 4 gt 4573068 Suase Create a new All Notifications Table The All Notifications Table
11. System gt Host BOCAGRANDE 1ti com gt Process 7764 gt DP 0 gt Publisher gt DW Square k Click on DP 0 in the list of parent entities This will select the DomainPartici pant in the Physical View tree and the Status panel will change to show the DomainParticipant s status Notice that the Status panel now shows an aggregation of the statuses of all the DataWriters and DataReaders that belong to the selected DomainParticipant 1 Close the Status panel 7 Review all the processes in the system a Select the Processes Table button from the toolbar File Domain Actions Window Help e o vEBS KE 2uliase FFO Create a new Processes Table b This will display a panel that shows the processor and memory usage of all monitored processes Select one of the processes and click on the Select in Physical View button this will select the same process in the Physical View tree Processes Table Select in Physical Vien i I Select in Physical View Find Host ID Total CPU User CPU Kernel CPU Physical Memory MB Total Memory MB B BOCAGRANDE rti com 7 020 0 o 0 31 852 111 09 a BOCAGRANDE ti com 7 764 0 oj 0 34 195 113 426 The Find button is useful for searching a large table for a specific process This is a simple string search so you must use the same format displayed in the table for example notice that the process ID includes a comma 3 8 Showing
12. System Topology Sample Counts and Rates c Click on the Total CPU column heading This will sort the table by the values in this column Clicking it again will sort in the opposite order This is useful to watch in real time to see which processes are using a lot of CPU You can sort based on any of the columns Click the E button just above the vertical scrollbar This allows you to choose which columns appear in the table For instance to remove the ID col umn uncheck it Note to enable the Pack Selected Column option select a cell in the top row Kernel CPU Phy Total Memory MB vV Host Pi 25 2 v ID Click here to v Total CPU see these Fi V User CPU options To resize columns such as this one to fit vV Kernel CPU their contents select this option V Physical Memory MB v Total Memory MB Horizontal Scroll Pack All Columns Pack Selected Column You can also change the order of the columns by simply dragging them to a new place in the table e Close the Processes Table 8 Review all the data types in the system a Select the System Types Table button from the toolbar File Domain Actions Window Help gt 2673088 Sulaee esas Create a new System Types Table 3 9 ow q A Demo using RTI Shapes Demo 3 10 This will display a panel that shows all the known data types in the selected domain In this case there is only one data type cal
13. View tree select the DataWriter then select the Status Panel button in the toolbar File Domain Actions Window Help oo 6573S KE SuiasS earra Create a new Status panel i Select the Advanced display mode j Scroll down to see Discovery Statistics Click the link next to Last DataReader GUID This will select the matching DataReader in the Physical View tree and the panel will switch to show DataReader status instead Stat Pane System gt Host BOCAGRANDE ti com gt Process 7764 gt DP 0 gt Publisher gt DW Square 0 40 First Unelapsed Keep Duration r Offered Deadlines Missed r Offered Incompatible QoS Total Count 0 A0 Total Count Last Instance Handle Last Policy Id r Reliable Writer Cache Fail Empty Cache 22346 aso Policies Full Cache 0 40 DataWriter Cache Low Watermark 22 346 A80 High Watermark 22 346 A80 Sample Count Unacked Samples 0 Unacked Sinne Peak A Sata EILE Discovery Statistics r Publications Matched Total Count Current Count Current Count Peak Last DataReader GUID 0a80167 1b6c 1 80000007 as Click here to select the matching reader A Demo using RTI Shapes Demo The top of the Status panel and some of the other entity specific panels that you will see later in this demo shows a list of parent entities to which the selected entity belongs For example Status Panel SAR 3
14. displays all the notifications in the entire system not just for the selected entity By default it shows both warnings and errors You can choose to see either just the warnings or just the errors by checking unchecking the options A All Notifications Table BaO Select in Views Show Problem Types W Warning J Error Entity State Status System gt Host BOCAGRANDE ti com gt Process 7020 gt DP 0 gt Publis WARN System gt Host BOCAGRANDE Iti com gt Process 7764 gt DP 0 gt Subsc WARN If a row is selected in the All Notifications Table clicking the Select In Views button in the All Notifications Table will select the corresponding entity in the tree views d Close the All Notifications Table panel e Select the System Overview Panel button from the toolbar In the System Overview Panel with the Notifications option selected all the entities in the system that have caused a notification are highlighted in the system map f Close the System Overview Panel 6 Clear the notifications a In the publisher shapes demo instance select Controls Resume Publishing b From Monitor s menu select the Clear All Notifications button from the tool bar This will clear all the yellow markers in the tree File Domain Actions Window Help gt 4 73 R08 Swath earra Clear All Notifications 3 2 owed A Demo using RTI Shapes Demo 3 4 3 22
15. tab TI File Domain Actions Window Help v Please enter the ID of the DDS domain you d like to join m kos cance Physical View DDS Logical View ee bcr Age Sula2 eama ae Description Type Y ds System v FR BOCAGRANDE ti com v E Process ID 7020 Expa nd Y amp DomainParticipant 0 RTI Monitoring Demo the Entity v Pes Square Square ShapeType tree v Subscriber J DataReader Square ShapeType v E Process 1D 7764 amp DomainParticipant 0 RTI Monitoring Demo v Topics Square Square ShapeType v Publisher b DataWriter Square ShapeType Sem Display Mode Basic Advanced Common Information NIA GUID Received Count Received Bytes Duplicates Count Duplicates Bytes Filtered Count Filtered Bytes Rejected Count Version Last Update Wed Aug 08 21 01 58 EDT 2012 Update Period 5 0 seconds DataReader Statistics Sample Statistics p Heartbeat Statistics 3 665 480 278 520 46 080 0 40 0 40 o 40 o 40 0 40 Total Count Samples Lost 0 40 Alive Count Not Alive Count Total Count Liveliness Changed Last DataWriter GUID Requested Deadlines Missed Last Instance Handle 14 A0 0 40 c0a80167 1e54 1 80002002 Heartbeat Count Heartbeat Bytes Gap Count Gap Bytes Ack Count Ack Bytes Nack Count ponies Samples Rejected To
16. very large system you may need to modify the file lt installation direc tory gt scripts rtimonitor bat on Windows systems or lt installation directory gt scripts rtimonitor on Linux systems to increase the maximum Java heap size usage For example in the script change Xmx500m to Xmx1536m Error Regarding Incompatible Shared Memory Segment If you see the following error messages D0000 ENABLE NDDS_Transport_Shmem_attach_writer incompatible shared memory segment found Found segment with max message size 9216 Needed 65530 These messages likely mean either a Another application is currently running on the same host in the same domain with different shared memory transport settings or b If you are on a Linux system there was an old application running on that domain ID before with different shared memory transport settings that was not terminated gracefully To correct problem a if you do not intend to monitor the application that has different shared memory settings on the same host you can use another domain ID for the moni toring topics both in Monitor and in the Connext applications that you want to monitor If you intend to monitor all the Connext applications in that domain on the same host make sure that all the applications running on the same host with the same domain ID have consistent shared memory transport settings The QoS profile used by Monitor is in lt installat
17. RTI Monitor Getting Started Guide Version 5 0 t j Your systems Working as one 2011 2012 Real Time Innovations Inc All rights reserved Printed in U S A First printing August 2012 Trademarks Real Time Innovations RTI and Connext are trademarks or registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Contents 1 Welcome 2 1 2 2 2 3 24 Installation and Start Up Instructions for Linux SYSteMS ccccceesseseseesessnesesescsesesesesescseseseecscssseseseecscssenseesesenenen 2 1 DVN Tins telat p arein eis aes lata axe bee case AEE sles yew ear easa ree E R via olaveed vee ot is 2 1 PI WRUNG EEEIEI AL sence saath si T OE AET 2 1 Instructions for Windows Systems s ssessesssesississesssesi
18. Range gt Range Axis c Close the two Chart panels ind 14 Let s see how to determine which DataWriter is contributing more received samples a In the Physical View tree select the Expand All button b Select the DataReader in the tree then select the Status Panel button from the toolbar For Filter by match select the first matching endpoint in the drop down menu 3 13 owad A Demo using RTI Shapes Demo 3 14 c Select the Status Panel button again to open a second status panel for the reader For Filter by match select the second matching endpoint in the drop down menu Now you have status for both of the reader s matching writers side by side The Received Count values will point out which one is contributing more samples Status Panel 2 System gt Host BOCAGRANDE tti com gt Process 7020 gt DP 0 gt Subscriber gt DR Square z saaan Status Panel System gt Hast BOCAGRANDE tt com gt Process 7020 gt DP 02 Subscriber gt DR Square e e Filter by match Host BOCAGRANDE ti com gt Process 7764 i Filter by match Host BOCAGRANDE rti com gt Process 8776 i ne vee Display Mode Basic Advanced Display Mode Basic Advanced Common Information Common Information Version 5 0 0 Version 5 0 0 Last Update Wed Aug 08 22 50 25 EDT
19. aWriter s Samples Written Counts and the DataReader s Samples Received Counts side by side Notice that the send and receive sample counts are about the same ill Chart Panel 2 Oe ill Chart Panel aox System gt Host BOCAGRANDE rti com gt System gt Host BOCAGRANDE rti com gt Process 7020 gt DP 0 gt Subscriber gt DR Process 7764 gt DP 0 gt Publisher gt DW Square Square ilter by m All Matches Filter by m All Matches Chart Data Samples Received Counts iy ChartData Samples Written Counts i lt lt t 80 m yp ot Notes e The default settings set the publish rate of the monitoring topics to 5 sec onds Therefore you may need to wait 5 seconds for the Monitor data to be updated The charts for Samples Written Counts and Samples Received Counts show the number of samples sent received in the last sample period In this case the sample period is 5 seconds Since Shapes Demo publishes 16 samples per second you will see approximately 80 5 x 16 samples per sample period The Chart Time Range slider at the bottom of Monitor changes the time scale of the graphs To unpin the panels press their pin buttons again Notice that now both chart panels are showing DR as the current entity at the top since that entity is selected in the Physical View tree 11 Start a third instance of Shapes Demo For example on a Windows system open a c
20. b Subscriber Pub Publisher DP DomainParticipant P process ID Showing System Topology Sample Counts and Rates d Select the Matches option in the System Overview panel Select DW or DR in the system map to see what entities are matched in the system i Highlight Mode O Notifications Matches Measurement Measurement Samples Received Count ky Scale No Scaling by Key r Display Name Controls Host Top DataReader Process subse Dataweter Domainpartcivant Punisher a Notice that when you select an entity in the system map that entity also becomes selected in the Physical View tree e Click the Back button on the toolbar it will change the selection back to the previously selected entity in the Physical View tree and the System Overview panel Try the Forward button ie too 3 5 A Demo using RTI Shapes Demo 3 6 f In the System Overview panel select the Measurement option and Samples Received Count in the drop down menu You will see a color map that indi cates the number of samples received by various entities in the system RTIM File Domain Actions Window Help gt 6578S KE Saza eaan Physical View DDS Logical View o System Overview Panel gjg ae IR Entity Description Type es ess v ads System O Notifications Q Matches
21. ctive Network Interface If you run Monitor on a computer that does not have an active network interface you may see an error message stating No interface found enabled for multicast Modify the QoS profile used by Monitor to turn off UDPv4 and only use the shared memory transport lt participant_qos gt lt transport_builtin gt lt mask gt SHMEM lt mask gt lt transport_builtin gt lt participant_qos gt The QoS profile used by Monitor is in lt installation directory gt config rtimonitor_qos_profiles xml See Section 3 8 in the Monitor User s Manual for more information on editing this file
22. e command line options in Table 2 1 Table 2 1 Command line Options Option Description Monitor periodically goes through all the monitored entities in the system this information is saved in its own database to cal aggregationPeriodSeconds lt seconds gt culate aggregated statistics and states This value controls that minimum period specified in seconds Default 5 seconds help Displays all command line options 2 3 dn upis PUD UuOIIDIIDISuI Z Installation and Start Up Table 2 1 Command line Options Option Description historyDepth lt value gt Monitor saves some statistics history so it can be displayed in the charts This option controls how much historical data num ber of samples is saved per monitoring topic Default 12 samples ignoreTypeConflicts Instructs Monitor to ignore any type conflicts In Monitor type conflicts are based on type code equality rather than type com patibility This command line option can be useful if you have types that have different type code but are compatible Default Not specified do not ignore type conflicts initialDomainIds lt domain_id_list gt Specifies which domains Monitor will join when it starts up lt domain_id_list gt is a list of domain IDs each separated by a comma To specify multiple domain IDs on a Windows system enclose the comma separated IDs in quotation marks For example
23. el However it should not affect the rest of the monitoring data To see the IDL representation of large type code in Monitor you can increase the maxi mum type code serialized size both in the monitored Connext application and in Moni tor However if you do that you will also need to increase the values in the transport settings to support large data in Connext discovery traffic both in the monitored Con next application and in Monitor A sample large data QoS profile is shipped with the Monitoring Library bundle it has large data support turned on for both the UDPv4 and shared memory transports and a larger maximum type code serialized size Please see the documentation in the Monitor ing Library bundle for an explanation of the large data QoS profile If you use the pro 4 5 6Huyoouse qnoll y Troubleshooting 49 4 10 4 6 vided large data QoS profile you can uncomment the corresponding settings in the Monitor QoS profile to enable support for large type code and large data Both the mon itored Connext application and Monitor must have a consistent maximum type code serialized size and consistent transport settings The QoS profile used by Monitor is in lt installation directory gt config rtimonitor_qos_profiles xml Running out of Memory If Monitor is running out of memory you can use a smaller value for the history Depth command line option or run Monitor on a 64 bit machine Running without an A
24. eneees 4 4 4 8 No Type Code for Some Entities in Description Panel eeesesseeeresesesssessssseasses 4 5 4 9 Running ort Of Memory assa mi s a etie aiia iea tina deae deian 4 6 4 10 Running without an Active Network Interface ieeerrseesserrseesserssesesrseressssssassesssaseess 4 6 Chapter 1 Welcome RT Monitor is a graphical tool that displays monitoring data from RTI Connext for merly RTI Data Distribution Service applications Monitor will help you L Understand your sys tem with an easy to use graphical view into your entire Connext applica tion C Notifications O Matches Measurement Measurement Samples Received Count TE Scale NoScaino ry System Overview Panel B08 Highiizht Mode Key Selecred 0 Ll Verify your design by oo ooa em ere making sure the entities so in your Connext applica tions are communicating as expected L Tune performance by providing deep statis tics on every aspect of the middleware s opera tion RTI Monitor L Optimize integration with detailed information on every entity in your system L Monitor real time operation with a dashboard of tools to see traffic patterns errors lost samples and more You can run Monitor on the same host as the Connext application or on a different host QWODIOM L Welcome
25. h a 250ms deadline a Select Subscribe Square b Check the Reliability box c Set Deadline to 250 d Select OK In the publisher Shapes Demo instance select Controls Pause Publishing Observe the results in Monitor a Select the Expand All button for the Physical View tree in Monitor Showing Deadlines Notice that all the entities in the Physical View tree are marked with yellow triangles to show there is a potential problem The root cause of the problem is in bold the DataWriter and DataReader in this case The parent entities are also marked with yellow triangles but not in bold Physical View DDS Logical View CE Entity Description Type v FA BOCAGRANDE Iti com v 7 Process ID 7020 v amp DomainParticipant 0 RTI Monitoring Demo v 778 Topics R Square Square ShapeType Y Publisher a DataWriter Square ShapeType v 7 Process ID 7764 v amp DomainParticipant 0 RTI Monitoring Demo v Topics R Square Square ShapeType v DW Subscriber gt DataReader Square ShapeType b In the Physical View tree select the DataWriter then select the Status Panel button in the toolbar c In the Status panel select the Ma Deadines Miased Advanced display mode Under Offered Deadlines 13 Count fret caso Missed notice the non zero Total Count highlighted in yellow d In the Physical View tree select the DataReader Now the Status Panel is showing values for the DataReader Under
26. indow Help gt 45738348 Sulaee esas Create a new Description panel 3 23 owseg A Demo using RTI Shapes Demo In the QoS tab scroll down and notice that the values for qos resource_limits max_samples max_samples_per_remote_writer are both 2 which is the same as the Sam ple Count and Sample Count Peak values we saw in the Status panel previ ously This shows that the reader s queue for receiving samples is full qos reader_resource_limits System gt Host BOCAGRANDE tti com gt Process 3956 gt DP 0 gt Subscriber gt DR Square QoS Builtin Topic Data DataType Description Panel Field Value pub BE fesource limits ke max_samples t D D re max_instances max_samples_per_instance initial_samples initial_instances instance_hash_buckets user_data value ownership kind time based filter minimum_separation ader data lifecycle autopurge nowriter samples delay J autopurge disposed samples delay type_consistency kind ader_resource_limits max_remote_writers max_remote_writers_per_instance a a ONIN SHARED_OWNERSHIP_QOS 0 0 seconds infinite infinite ALLOW_TYPE_COERCION 14 1 max samples per remote writer a T max infos A 6 Fix the problem by creating a DataReader with a larger queue si
27. ion directory gt config rtimonitor_qos_profiles xml The transport settings in this profile need to be consistent with the transport settings in all the Connext applications that are running on the same host with the same domain ID All shared memory transport settings are specified under the participant_qos and have property names that begin with dds trans port shmem builtin See the documentation for Monitoring Library for an explanation of the transport settings To correct problem b use the ipcrm command to clean up the shared memory and shared semaphore resources See the RTI Core Libraries and Utilities Platform Notes for Unable to Create Participant in Connext Application 4 5 details You can also run Monitor and the Connext application that you want to monitor with another domain ID that doesn t have any shared memory or shared semaphore resources left over from previous runs Unable to Create Participant in Connext Application If you see error messages similar to the following CREATE Participant RTIOsapiLibrary_open error opening library rtimonitoringnothing dll CREATE Participant DDS_DomainParticipantMonitoring_ initializeMonitoringLibrary ERROR Failed to get load monitoring library CREATE Participant DDS_DomainParticipantMonitoring_initializel create monitoring library instance CREATE Participant DDS_DomainParticipant_createI create builtin monitoring support CREATE Participant DDS_DomainParticipantFactor
28. is then pinned to the entity and the panel will periodically receive updated data for the Description Panel System gt Host BOCAGRANDE 1ti com gt Process 7020 gt DP 0 gt Subscriber gt DR Square DataType ShapeType 69fd54c6deb1ebc5 Typecode Serialized Size 130 Minimum Serialized Size 24 Maximum Serialized Size 152 Maximum Key Serialized Size 137 IDL Representation struct ShapeType string lt 128 gt color i key long x long y long shapesize k li Extensibility EXTENSIBLE_EXTENSIBILITY pinned entity even when another entity is selected in the tree a Select the Physical View tab on the left b From the menu make sure Window Auto Tile is checked c In the Physical View tree select the DataWriter then press the Chart button in the toolbar File Domain Actions Window Help gt 6573848 Sa a ear Create a new Chart panel d In the Chart panel press the pin button amp on the top left corner Notice that the button has changed to pinned amp to indicate that the panel is pinned to a specific entity For Chart Data select Samples Written Counts e In the Physical View tree select the DataReader then press the Chart button in the toolbar to create the second Chart panel and press its pin button For Chart Data select Samples Received Counts 3 1 owad A Demo using RTI Shapes Demo 3 12 f Now you can compare the Dat
29. led ShapeType System Types Table Domain 0 Type Name Type ID Keyed Min Serialized Max Serialized Max Key Serialized Type Code Serialized B ShapeType 69fd54c6d Yes 24 152 137 130 la Like the Processes Table we saw earlier this table also has a E button above the vertical scrollbar to control the columns that appear in the table You can also sort the table based on any of the columns by clicking the column head ing b Select the DDS Logical View tab on the left This is another display of the system tree arranged by domain and topics Select the Square topic from the tree and the corresponding row will be highlighted in the System Types Table c Close the System Types Table 9 Show details of each data type a Select the Physical View tab on the left b Select DataReader in the tree then select the Description Panel button from the toolbar File Domain Actions Window Help gt ccorAngaE Sasa ea Create a new Description panel Showing System Topology Sample Counts and Rates 10 c In the Description panel select the DataType tab to see the data type for the data reader in IDL You can also see other properties related to the data type d Close the Description Panel To show panels for two or more entities side by side for comparison you can press the pin button at the top left corner ot all the entity specific panels The panel
30. nd Monitor 2 warnings Monitor only 3 warnings both Core Libraries and Monitor 4 information Monitor only 5 tracing Monitor only 6 tracing both Core Libraries and Monitor Default 1 dn H0 S PUD UOlJD DJsu Z Installation and Start Up 2 6 Chapter 3 A Demo using RTI Shapes Demo Before going through the steps in this chapter make sure that both RTI Monitor and RTI Shapes Demo are installed 3 1 Showing System Topology Sample Counts and Rates 1 Starts two instances of Shapes Demo e To start Shapes Demo on Linux systems Enter the following in a command shell gt lt Shapes Demo install directory gt scripts rtishapesdemo e To start Shapes Demo on Windows systems If you have RTI Launcher you can use its Utilities tab to start Shapes Demo Or from the Windows Start menu navigate to RTI Connext lt version gt RTI Con next Messaging lt version gt Components RTI Shapes Demo lt version gt and select RTI Shapes Demo 3 1 oweg A Demo using RTI Shapes Demo 2 The figure to the right shows the main Shapes Demo window and the Configuration dialog that appears at start up Choose the profile MonitorDemoLibrary MonitorDefault No other configuration changes are necessary If you choose to use a different domain ID make sure to use the same value in both instances of Shapes Demo Press Start Repeat so you are running two instances of Shapes Demo
31. ngs that support large data you will need to change the corresponding settings in the QoS profile used by Monitor The maximum type code serialized size is configured under resource_limits for the participant_qos transport settings are configured under property for the participant_qos The QoS profile used by Monitor is in lt installation directory gt config rtimonitor_qos_profiles xml See Section 3 8 in the Monitor User s Manual for more information on editing this file A sample large data QoS profile is provided with the Monitoring Library bundle for your reference it has large data support turned on for both the UDPv4 and shared memory transports and uses large maximum type code serialized size support If you need to use large data or large type code in your Connext application you can use this provided large data QoS profile in the monitored application and also uncomment the corre sponding transport and maximum type code serialized size settings in the Monitor QoS profile this will enable consistent large maximum type code serialized size and large data transport settings Please see the documentation in the Monitoring Library bundle for an explanation of this large data QoS profile No Type Code for Some Entities in Description Panel If the type code for your user data type is larger than the default maximum type code serialized size the IDL for that data type may not show up in the DataType tab in Moni tor s Description Pan
32. omain Actions Window Help gt ccor AOE Swath aga Load Dota f You will see a prompt asking if you want to lose the current data and leave the domain Select OK to continue In the file dialog select the file in which you previously saved the data Notice that the title of the Monitor window has changed to Historical data mode and shows the name of the loaded data file Now you are seeing a snapshot of the system File Domain Actions Window Help eo sev m in Suwia2 earra g Select the Expand All button for the Physical View tree You can see all the previously created entities even though no publications or subscriptions are currently running h Select Domain Show Current Domain from the menu Notice that you are not joined to any domain now because Monitor is showing historical data instead of live data Click OK to close the dialog box 16 Prepare for the next demo a Select the Join Domain button from the toolbar You will see a prompt asking if you want to lose the currently loaded data Click OK to continue Rejoin your original domain by entering the domain ID then click OK Notice that the title of Monitor is no longer showing Historical data mode Monitor is showing live data again b Close all the panels 3 15 owseg A Demo using RTI Shapes Demo 3 2 3 16 Showing Content Filtered Samples The steps in this section assume you are using the same profile used in Sec
33. ommand prompt and enter the fol lowing replacing the installation directory to match your system gt cd lt Shapes Demo installation directory gt gt scripts rtishapesdemo pubInterval 250 Or on a Linux system enter the following replacing the installation directory to match your system gt cd lt Shapes Demo installation directory gt gt scripts rtishapesdemo pubInterval 250 Just like the other Shapes Demo instances choose the profile MonitorDemoLi brary MonitorDefault Showing System Topology Sample Counts and Rates 12 In the new Shapes Demo window create a reliable square publisher of a different color a Select Publish Square b Choose the profile MonitorDemoLibrary MonitorDefault c Select YELLOW d Make sure the Reliability box is checked e Select OK 13 Examine the data in chart a In Monitor System gt Hast BOCAGRANDE tti com gt notice the Process 7020 gt DP 0 gt Subscriber gt DR ra eee a een are The new number of Square i DataWriter received ilter by m All Matches increases thenumber samples i Chart Data Samples Received Counts of received increases in samples the chart b Right click in the white space in one of 801 the charts to see how you can change 70 Properties i the chart A can Save as 50 5 Print 40 O Zoom In L Both Axes 301 ZoomOut gt Domain Axis 20 Auto
34. onnext applications that are using Monitoring Library If you have not yet installed Monitoring Library for use with your Con next applications you may want to do so now Refer to the Monitoring Library Getting Started Guide that is provided with the Monitoring Library bundle Monitoring Library is available from the RTI Support Portal accessible from https support rti com 2 1 2 Running Start Monitor using the provided rtimonitor script 2 1 dn wns PUD UuOIIDIIDISuI Z Installation and Start Up 2 2 2 2 1 2 2 2 2 2 For example if you installed Monitor in opt rti start it by entering gt opt rti RTI_Monitor_ lt version gt scripts rtimonitor Command line options are described in Section 2 4 Instructions for Windows Systems Installing Monitor is included with RTI Connext Messaging Use the installation instructions in this chapter only if you are installing Monitor independently not as part of RTI Connext Mes saging 1 Right click RTI_Monitor lt version gt Win zip and select Extract All to install Monitor in the directory of your choice You must have write access to the direc tory If you choose c RTI the resulting installation will be in c RTI RTI_Monitor_ lt version gt 2 See Installing the License File Section 2 3 3 Monitor is designed to monitor Connext applications that are using Monitoring Library If you have not yet installed Monitoring Library for use with you
35. oring topics can have data that is larger than what is supported by the default transport settings especially for cases in which a lot of propagated properties are added to the PropertyQosPolicy or a large UserDataQosPolicy TopicDataQosPolicy or GroupDataQosPolicy is involved By default asynchronous publishing is used for the writers in Monitoring Library for these monitoring topics to resolve the large data issue transport settings and the maximum type code serialized size are left at the default values The maximum type code serialized size and transport settings must be consistent between Monitor and the Connext application in which monitoring is enabled By keep ing the maximum type code serialized size and all the transport settings at default val ues in the QoS profile used by Monitor all monitored Connext applications that use default settings will work with Monitor out of the box No Type Code for Some Entities in Description Panel 4 8 If you are not receiving monitoring data it is most likely because you do have inconsis tent transport settings or inconsistent maximum type code serialized size settings between Monitor and the Connext application in which monitoring is enabled maybe you are not using the default maximum type code serialized size or transport settings in the monitored Connext application If your monitored Connext application is required to use a large maximum serialized type code size or transport setti
36. r Con next applications you may want to do so now Refer to the documentation in the Monitoring Library bundle for details Monitoring Library is available from the RTI Support Portal accessible from https support rti com Running Start Monitor by double clicking lt installation directory gt scripts rtimonitor bat You can also start it from the command line if you need to use any of the options described in Section 2 4 Installing the License File 2 3 Installing the License File Monitor requires a valid license to run You will receive one via email after you down load the software Save the license file in any location of your choice When Monitor starts it will look in these locations until it finds a valid license 1 The last saved valid license location of the current user if Monitor has been run before The file specified in the environment variable RTI_LICENSE_FILE which you may set to point to the full path of the license file including the filename for example C RTI my_rti_license dat The file rti_license dat in the current working directory The file rti_license dat in the directory specified by the environment variable NDDSHOME If Monitor cannot find a valid license file automatically it will prompt you to enter the location of a license file If you have any questions about license installation please contact support rti com 2 4 Command line Options Monitor accepts th
37. sseesesstesiesissensneniententessnsneneeneesness 2 2 2 217 MPS balling nae a a aA e A S 2 2 222 ARUMMING sees iel a aaa ar are a A ave shies 2 2 Installing the License Filessssnieni dieni a aea e a E A E E TEE Eri E 2 3 Command line Options cccccessescsssesesesesessesesesesenssesesesesssesesesesesssesesesssssesesesssesesesesees 2 3 A Demo using RTI Shapes Demo 3 1 Showing System Topology Sample Counts and Rates eee cesses tees eeeeeeees 3 1 3 2 Showing Content Filtered Samples eeeeseeseerreressesseesssesessessssasessshssessesssssassessesss 3 16 3 3 Showing Deadlines ssie e R A ae easa deasa ie aig hea deen 3 18 34 Showing a Samples Rejected Scenario erereeseeserereerhsesesseshssessessesesessessssesssse 3 22 4 Troubleshooting 4 1 Debugging Problems with Monitor on Windows System eeeeersersseesserseeseeeseeesesss 4 1 42 Running Monitor on a System with Limited Memory ieerseeereeresesseeressseessssesseess 4 1 43 Running Monitor with a Large System cc ceeeececeeseseseececeesesnecececensnseeseeenes 4 2 44 Error Regarding Incompatible Shared Memory Segment eee ee seeeeeeeneees 4 2 4 5 Unable to Create Participant in Connext Application i eereeserrsseseerseeshesaseeeseseeees 4 3 4 6 Not Receiving Monitoring Data due to Inconsistent QoS eieeeeseeeeresessssessesesseasses 4 4 4 7 Not Receiving Monitoring Data for Entities ccccccccecsestenenesesesneeescececeseseansnen
38. t QoS If you see an error message similar to the following WARN com rti dds monitor util DebugDataReaderLis tener on_requested_incompatible_gqos Unknown Source topic rti dds monitoring domainParticipantDescription RequestedIncompatible QosStatus total_count 1 total_count_change 1 last_policy_id Dura bility policies QosPolicyCount policy_id Durability count 1 This message most likely means that the internal DataWriters created by Monitoring Library for publishing monitoring topics have QoS that are incompatible with the QoS of the internal DataReaders created by Monitor for subscribing to monitoring topics If you see this error message try specifying the rtimonitor config qos_library and rti monitor config qos_profile properties in the Connext application that has monitor ing turned on to ensure that the internally created DataWriters are using the correct QoS values The default QoS values used for the internally created DataReaders are listed in RTIMonitoringQosLibrary and RTIMonitoringPublishingQosProfile in the file lt Monitoring Library installation directory gt resource xml MONITORING_QOS_PROFILES xml in the Monitoring Library bundle Refer to Moni toring Library s documentation in the Monitoring Library bundle for an explanation of the QoS settings that are required to specify the QoS library and profile Not Receiving Monitoring Data for Entities Some of the monitoring topics the description monit
39. tal Count Last Reason tastinstance Handie a T Requested Incompatible QoS Total Count Last Policy Id Policies 0 cao 0 40 0 40 1 40 32 40 0 40 0 40 0 40 0 40 NOT REJECTED DataReader Cache Sample Count Sample Count Peak Sample Statistics Pushed Count Pushed Bytes Pulled Count Pulled Bytes 3 597 481 273 372 46 156 0 40 0 40 DataWriter Statistics Offered Incompatible QoS Total Count hart Time Range minutes H 2 System Metrics Domains 1 Hosts 1 Processes 2 Participants 2 Topics 1 Publishers 1 DataWriters 1 Subscribers 1 DataReaders 1 ummary of the current number of entities being monitored 3 3 A Demo using RTI Shapes Demo b Close the Status Panel on the right select the red E3 at the top right corner of that panel c Select the System Overview button in the toolbar to see a summary of the monitored domain x j Highlight Mode Notifications Matches Q Measurement Measurement Samples Received Count Scale No Scaling Key Display Name Controls T Host Terse w Terse DataReader Process Terse w Subscriber Terse nd DomainParticipant Terse a Publisher Terse i Visual map of the system Outer most box represents the host 3 4 T Topic DR DataReader DW DataWriter Su
40. tion 3 1 for the two instances of Shapes Demo 1 In one instance of Shapes Demo create a reliable square publisher a Select Publish Square b Make sure the Reliability box is checked c Select OK In the other instance of Shapes Demo create a content filtered reliable square subscriber a Select Subscribe Square b Check the Reliability box c Check the Use Filter box under Content Filter Topic d Select OK Notice that the subscriber only receives samples that are within the filtering square Observe the filtered samples in Monitor a Select the Expand All button for the Physical View tree in Monitor b In the Physical View tree select the DataWriter then select the Status Panel button from the toolbar In the Status panel notice that the Sample Statistics Filtered Count is non zero and keeps changing A In the Physical View tree select the DataReader Now the Status panel is showing values for the DataReader Notice that the Sample Statistics Filtered Count is zero This shows that content filtering is only happening on the writer side in this case d Close the Status panel Showing Content Filtered Samples 4 Show the content filter expression a In the Physical View tree select the DataReader then select the Description Panel button from the toolbar File Domain Actions Window Help Bulaee e 4 im ra Create a new Description panel b Select the Builtin Topic
41. y_create_participant_ disabledI create participant These messages most likely mean that your Connext application is configured to load the monitoring library dynamically but you don t have the monitoring library in your path If you are running on a Linux system make sure that your LD_LIBRARY_PATH envi ronment variable includes the monitoring library If you are running on Windows make sure that your PATH environment variable includes the monitoring library If you are seeing error messages similar to the following CREATE Participant DDS_DomainParticipantFactory_set_default_ participant_qos ERROR Inconsistent QoS more information at WARN ver bosity level CREATE Participant DDS_DomainParticipantFactory_load_profilesI ERROR loading profiles CREATE Participant DDS_DomainParticipantFactory_create_participant_ disabledI ERROR loading profiles These messages most likely mean that you are using a lot of properties in the Partici pantQos to configure monitoring and participant property string max length or participant_property_list_max_length in the ResourceLimitsQosPolicy in DomainPar ticipantQos is not large enough to accommodate all the properties Try increasing those values in your Connext application to fix the problem 4 3 Buyooys jqnor y Troubleshooting 4 6 4 7 4 4 Not Receiving Monitoring Data due to Inconsisten
42. ze a In the Subscriber Shapes Demo instance select Controls Delete All b Create a new reliable square subscriber that uses take and the MonitorDe moLibrary FixedSamplesRejectedScenario profile which will fix the prob lem by increasing the queue size c Select Subscribe Square d Choose the profile MonitorDemoLibrary FixedSamplesRejectedSce nario 3 24 Showing a Samples Rejected Scenario e Check the Reliability box f For Read method to use select Take g Select OK This profile uses a larger queue size Verify the new reader queue size in Monitor a Select the Expand All button under the Physical View tab b In the Physical View tree select the DataReader c In the Status panel that is already open notice that the Total Count values for Samples Lost and Samples Rejected are now zero In the DataReader Cache section notice the values for Sample Count and Sample Count Peak In the Description panel that is already open notice in the QoS tab that the values for qos resource_limits max_samples and qos reader_resource_limits max_samples_per_remote_writer are now 100 This is larger than the SampleCount and Sample Count Peak values seen in the Status panel This shows that now the reader queue still has a lot of room before it becomes full and starts dropping samples This concludes the demo 3 25 owseg A Demo using RTI Shapes Demo 3 26 Chapter 4 Troubleshooting
Download Pdf Manuals
Related Search