Home
User`s Manual - Community RTI Connext Users
Contents
1. rt RTI Connext Launcher 5 2 0 9 Copy to RTI install location all users Copy to RTI user home just for user juan n nn Code Generator Connext Headers gt Connevt Hast 530 gt Log RTI Package c Installer You have three choices Copy to RTI install location all users The chosen license file will be copied to the Connext DDS Installation Directory with the name rti license dat Launcher will use this license file not only for the current execution and the current user but for subsequent executions by any user in the system with access to the Connext DDS installation Note that if you have installed into a system directory selecting this option may require system privileges 3 4 Launcher s Tabs 3 3 Copy to RTI user home just for user lt user gt The chosen license file will be cop ied to the current user s rti workspace version directory The license file will thus only be visible for the current user in subsequent executions of Launcher e Skip The chosen license file will be applied by Launcher only for the current execu tion of the tool It will not be automatically detected by the tool in subsequent exe cutions I Copy the file manually to one of the aforementioned locations where Launcher will search by default and name the file rti license dat As mentioned before if the RTI license file is copied to the RTI user home it will only be visi
2. Haee c nete 3 4 3 9 Launcher S T bS8 54 eR eee teer TRE Pee PROP I Ee lee re a ERG e Let eee 3 5 3 9 S TOOIS Tabiran SR eee OH ha ties ie Bene dee E NU SU ee ni tum Du a SU heen LE ties 3 7 Bid 2 Services aD eed i et e e e ee aee se ei ecd eee ene teet 3 8 Door DJ trlities Tab 5s ree Ree E etti eee e e RERO Ere a RE t rue E S 3 11 3 34 Installation ab it ete ete ote ni e ete EEG ce ha TE Ao 3 12 5 9 5 Help Tab eot afa tn te t ent My cia A stes 3 13 SECO Labs TID aia n Olea cnr ives eves Bess RRR RRR T ese cs O O lie Gece tb ett 3 13 93 97 Third Party Iab a eh hh ee li s s a des Sod deem S a BO S teet ddr a coven n 3 14 3 2 6 User Tab iusto ERE 3 14 3 4 Installing Target Libraries and RTI Components sees eee ee enn 3 15 3 5 Troubleshooting with Baurichetrs sdu bins a i sast kdss lskutliklaasadas alkttuadika ra 3 16 4 Configuring Launcher uico nies eines cede roere etorri nisi duin obi dne dd in eA so teses 4 1 4 1 Launcher Tabs and Their Associated XML Files essere erret ennt 4 1 42 How Launcher Finds Im ges 2 rene te eee eee eet ten eoe thc 4 1 43 Example Adding a Button to Launcher s User Panel 1 see 4 2 ili Chapter 1 Introduction RTI Launcher is a graphical application that allows you to install configure and run RTI Con next DDS components It automatically detects which RTI components are installed and enables their launch
3. Portal Examples RTI Videos RTI Partners RTI Website Web Demos GitHub OMG DDS Portal Connext DDS Documentation Getting Started XML App Creation User s Manual API Reference Platform Notes QoS Reference What s New Launcher Docs Release Notes Browse complete set The Browse complete set button opens the root of the documentation folder in the Connext DDS Installation Directory Labs Tab This tab is reserved for RTI applications that are experimental It may be empty in some releases and thus not shown The XML file that defines this tab is in the RTI workspace in the user s home folder rti_workspace version user_config launcher panels labs xml 3 13 Launcher s Tabs 3 3 7 3 3 8 You can find experimental applications on our Community Portal https community rti com Visit it and download the new applications Most of them will also provide XML snippets to be added to Launcher configuration file that will allow you to run the new application as other Con next DDS ones Third Party Tab This tab is reserved for applications from RTI s partners For information about RTI s strategic partners see the RTI Partners website https www rti com partners Products downloaded and installed by using the Third Party tab in RTI Launcher are not part of RTT and you should contact the third party provider for more information about them Tools Services Utilities Third Party User Help Install
4. RTI Connext Launcher 5 2 0 Sie x Tools Services Utilities Third Party User Help Installation Select a workspace amp Works bider called a workspace for this session Eclipse Eclipse Development Environment Browse Right click for additional help and documentation Use this as the default and do not ask again OK Cancel Launcher s XML format for panels is described in the XSD file launcher panel xsd This file is located in the same directory as the userxml and labs xml files rti workspace version user config launcher panels This file provides complete reference for defining buttons for Launcher in XML 4 3
5. application has already terminated Data can be persisted to files or an external database L Database Integration Service provides bidirectional integration between Connext DDS and a database Oracle Database Oracle TimesTen In Memory Database or MySQL 3 8 Launcher s Tabs 1 Queuing Service provides a queue exactly once communication pattern in which each sample will be delivered to exactly one QueueConsumer If there are no QueueConsum ers available when the sample is sent the sample will be stored until a QueueConsumer is available to process the sample This pattern is very useful in load balancing applica tions The configuration dialog is similar for all the services For example the configuration dialog for Routing Service looks like this RTI Routing Service Working Directory C Users juan Documents rti_workspace 5 2 0 user_config routing_ Configuration Files Home _CARTI 5 2 rti_connext_dds 5 2 0 resource xml RTI_ROUTINC User C Users juan Documents rti_workspace 5 2 0 user_config r Custom lt no custom config file specified gt Configuration default from HOME M Application Name Confirm command These dialogs also include validation for wrong parameters or paths Text fields are highlighted with different colors depending on their validation status When a text field is highlighted with a color green indicates that the field has a valid entry yellow indicates it is missing
6. but not required red means it contains invalid values 3 9 Launcher s Tabs When you are done configuring the service click on the Run button to run the service If the dia log has some invalid entries the Run button will be disabled and a warning icon will appear next to it RTI Routing Service 5 o 3 RTI Routing Service Working Directory rs juan Documents rti_workspace s 2 0 user_config routing_servic Configuration Files Home _C RTI 5 2 rti_connext_dds 5 2 0 resource xml RTI_ROUTINC User CAUsersjuan Documents Vti workspace V5 2 0Nuser configw Open Custom lt ho custom config file specified T Open Configuration default from HOME v Application Name Run A Confirm command The warning icon s pop up will show you the why the dialog is invalid If you want to preview the command that will be used for execution check the Confirm com mand checkbox If the checkbox is checked when clicking on Run a pop up dialog will show the command and command line parameters that will be used and the working directory from which the command will be run Configuration Files Home CARTI 5 2 Vti connext dds 5 2 0Vresource xml RTI ROUTINC Open Working directory C Users juan Documents rti_workspace 5 2 user_config routing service C RTI 5 2 rti_connext_dds 5 2 0 bin rtiroutingservice bat cfgName default If the execution is successful this command will be stored in the Command Histo
7. current Connext DDS installa tion This tab l Displays the current installation directory for Connext DDS I Displays and allows changes to the license file License may not be necessary depending on the bundle installed Launcher detects the need for a license file on a per product basis J Displays a table with the installed products and libraries and their installed versions This table can be filtered by using a Filter text field The table can also be fully expanded collapsed by using the two buttons next to the Filter field 3 12 Launcher s Tabs 3 3 5 3 3 6 1 Provides another way to access the RTI Package Installer to install additional compo nents and libraries into an existing Connext DDS installation Tools _ Services Utilities Third Party Help Installation License Information CAUsers juan Documents rti_workspace 5 2 0 rti_licensedat Choose Details Installation Directory CARTI 5 2 rti_connext_dds 5 2 0 Installed Products Product Architecture Admin Console Code Generator Connext Headers gt Canneyt Hast gt Log Help Tab This tab provides relevant online and local installed links to documentation information e g the RTI Support Portal the RTI Community web page etc Tools Services Utilities Third Party Installation Web Links RTI Community Online Docs Forums Knowledge Base Support
8. in real time for formulas graphs and other Excel features You can also publish data from a spreadsheet into the DDS cloud 3 3 2 Services Tab Third Party Help Installation J Routing Recording Replay Service Persistence Service Service Service Ka gti Database Queuing Integration Service Log The Services tab provides buttons and dialogs to run RTI infrastructure services that require application specific setup The Services tab includes the following applications Routing Service integrates disparate and geographically dispersed systems It scales Connext DDS applications across domains LANs and WANS including firewall and NAT traversal It also supports Connext DDS to Connext DDS bridging by allowing you to make transformations in the data along the way 1 Recording Service records real time data without having prior knowledge of the data types or topics in the system This service is also available by using Recording Console in the Tools tab L Replay Service replays recorded data by injecting it back into DDS You can change data rates and QoS settings This service is also available by using Recording Console in the Tools tab Persistence Service saves data from Connext DDS publishing applications to memory or permanent storage so it can be delivered to subscribing applications that join the system at a later time even if the publishing
9. in the order specified below L The path indicated by the RTI LICENSE FILE environment variable The file does not need to be called rti license dat to use this method J The RTI user home This is the rti workspace version directory in the user s home folder The specific location depends on the operating system The Connext DDS Installation directory This is top level directory where you installed the Connext DDS bundle For example if a license managed version of Connext DDS is installed in C Program Files rti_connext_dds version on a Windows system and there is no RTI LICENSE FILE envi ronment variable set Launcher will first look for C Users your user name Docu ments rti_workspace version rti_license dat RTI user home Then if not found it will look for C Program Files rti connext dds versionwrti license dat Setting the License File Some of Launcher s tools may be license managed In this case if Launcher has no knowledge of a valid license file those tools will be grayed out and won t work until a valid license is provided A warning message will be shown to indicate that the license file can not be found When you have a valid license there are a few ways to tell Launcher about the license file 1 Use the Launcher Installation tab s Choose button This will open a file chooser dialog that will let you navigate to the license file After choosing the file Launcher will prompt you with the following dialog
10. RTI Launcher User s Manual Version 5 2 0 f t j Your systems Working as one 2015 Real Time Innovations Inc All rights reserved 9 Printed in U S A First printing June 2015 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 B o eco GCE ON PE iinsert ri eana aeu nr saasina o Tne easi 1 1 2 Paths and Environment Variables Mentioned in Documentation 2 1 S Using RIT Eaurnclier tossine ienesis sss res Sko RUE riea esis i 3 3 Sil Starting Launcher eere e n aen e n ER RRR 3 3 3 2 License Management isis oed gre iade vn rito pet e t pe Hn e vei pe aa 3 3 3 2 1 Setting the License File ihe meto eee e me e en
11. Services utilities Third Party User Help _ Installation The User tab is defined in the user xml file found in the Launcher configuration folder in the user home s RTI workspace When this file is opened for the first time it will contain the follow ing launcher xmlns xsi http www w3 0rg 2001 XMLSchema instance xsi noNamespaceSchemaLocation launcher panel xsd lt Add custom menu items here gt lt launcher gt All the tab panel configuration files start with the XML tag lt launcher gt Let s add a button entry for running Eclipse to the user panel definition Buttons are defined in a tag called lt button gt launcher xmlns xsi http www w3 0rg 2001 XMLSchema instance xsi noNamespaceSchemaLocation launcher panel xsd gt lt Add custom menu items here gt button name eclipse gt icon eclipse256 png icon lt tooltip gt Eclipse Eclipse Development Environment lt tooltip gt lt legend gt Eclipse lt legend gt lt toolexec gt C Eclipse eclipse exe lt toolexec gt lt popupmenu gt lt popupmenu gt button lt launcher gt Example Adding a Button to Launcher s User Panel This is how the different tags are interpreted by Launcher J name attribute Internal name of the button No specific rule for it I icon Path or name of the icon file that will be used to show the application in the panel Preferred image file formats for Launcher
12. are PNG and GIF Launcher may not be able to correctly render the file if other format is provided e g vectorial It can contain an abso lute path to the file or it can refer to the name of the file in which case the image file will be looked for in one of the two well known image locations see section 1 1 in this chap ter In our case we copied the eclipse 256 logo file eclipse256 png into rti workspace version user config launcher icons If the icons sub directory doesn t exist it can just be created normally I tool tip Required field It is used to define a title for the application and a brief descrip tion This information will be shown to the user as a balloon tool tip when hovering over the icon The format of this field must be Title Description the is necessary Launcher may fail to create the panel if not found J legend Title for the tool that will be shown right below the icon J toolexec Path to the executable to run when the user clicks on the application icon J popupmenu Required field needs to be present but it may be empty like in our exam ple This tag is used to describe entries in the context menu that will be shown when the user right clicks on the icon Once the user xml file has been modified and saved restart or start Launcher for the changes to take effect You should be able to see the User tab now and in it there will be a launch button for the Eclipse Development Environment fli
13. ation SimVentions InformeDDS User Tab The User tab is reserved for customizing Launcher Its purpose is to allow users to integrate their preferred applications in Launcher The User tab is not visible the first time Launcher is run because it s empty by default and Launcher doesn t show tabs that are empty Tools Services Utilities Third Party User Help Installation S The XML file that defines this tab is in the RTI workspace in the user s home folder rti workspace version luser config launcher panels user xml Installing Target Libraries and RTI Components You can modify this XML file to add shortcuts for any application in the system See Chapter 4 Configuring Launcher for more details on how to do this Installing Target Libraries and RTI Components Launcher uses the RTI Package Installer to install new libraries and components The Package Installer accepts files in RTIPKG format rtipkg RTI s target libraries and add on components are available in this RTIPKG format when downloaded from the RTI download portal The RTI Package Installer executable is in the Connext DDS Installation Directory in the bin directory It can also be executed from the command line prompt In Launcher the RTI Package Installer can be found in both the Utilities tab and the Installation tab When you click it a dialog will pop up like this Select RTI Package files
14. ay 10 2015 C RTI 5 2 rti_connext_dds 5 2 0 bin rtiroutingservice bat cfgName defaultBothWays appName withApplicationName C Users juan Documents rti_workspace 5 2 0 user_contig routing_service 1 Command Help Some applications provide usage notes regarding calling parameters services utilities etc For those applications this menu will show the available options gt Help window ee eee Help for command C RTI 5 2 rti_connext_dds 5 2 0 bin rtipersistenceservice bat help RTI Persistence Service v5 2 0 0 sel I es Utilities Third Party User Help Installation Usage rtipersistenceservice options I Options cfgFile file Configuration file This parameter is optional a since the configuration can be loaded from LY other locations X 4 cfgName name Configuration name This parameter is required and it is used to find a persistence service matching tag in the configuration files Recording Replay Service Persistence Ww appName name Application name Service Service Used to identify this execution for remote administration and to name the domain participants Default cfgName identifyExecution Appends the host name and process ID to the appName to help ensure unique names E z domainId lt int gt domain ID for the domain participants Queuing created by the service n Service Default Use XML value remoteAdministrationDomainId int Enables remo
15. ble for this user in subsequent execu tions of the tool When the file is copied to the RTI install location directly it will be visi ble for all users with access to that directory The file may be copied both when Launcher has already been started or when it is offline If the license file is copied while Launcher is executing Launcher will detect the change automatically and apply the license to the UI L Set the RTI LICENSE FILE environment variable with the path to the license file When setting this variable not only Launcher but all the RTI applications will use the license file environment variable when executing Notice that when copied to one of the known locations all RTI applications will also detect the license file After successfully setting a license file with Launcher all the tools that were disabled because of the license will become available and usable Launcher s Tabs Launcher has a Graphical User Interface with tabs for different application categories The con tents of the tabs are XML defined If a tab contains no entries buttons or none of the applica tions in a tab are supported on your platform that tab will not appear in Launcher There are five tabs that are always visible to the user LJ Tools Tab Section 3 3 1 LI Services Tab Section 3 3 2 LI Utilities Tab Section 3 3 3 J Installation Tab Section 3 3 4 Help Tab Section 3 3 5 Launcher also includes other tabs which may or may no
16. buttons providing a convenient graphical interface to the configuration and run time parameters You can use Launcher to install new components or target platforms into the current Connext DDS installation see what is already installed navigate to the documentation and web based resources create new source code projects via its integration with rtiddsgen and run all the Connext DDS tools and command line utilities Launcher is intended to be your window and management console for all your Connext DDS products Keep it handy and use it as the launch interface whenever you need to start any RTI tool or service In addition you can customize Launcher to run any program installed in your system such as third party tools that work with Connext DDS or commonly used editors This can be easily done by changing the XML configuration file in the resource app app support launcher panels subdirectory of your Connext DDS installation directory 1 1 Chapter 2 Paths and Environment Variables Mentioned in Documentation The documentation refers to J Connext DDS Installation Directory lt NDDSHOME gt These both refer to the installation directory for Connext DDS The default installation paths are e Mac OS X systems Applications rti connext dds version e UNIX based systems non root user home your user namelrti connext dds version e UNIX based systems root user lopt rti connext dds version e Windows systems user withou
17. eclipse exe I Log files Launcher logs output and errors to files in a special directory This directory can be found in the user home s RII workspace directory rti workspace version user config launcher logs Launcher s execution log files are named with the following pattern launcher log lt timestamp gt txt Every execution of Launcher creates a different log file For applications not launched in command prompt windows like the applications in the Tools tab Launcher also logs their output into text files for application troubleshooting These files are stored in the same place as the Launcher logs rti workspace version user config launcher logs They are named following this pattern log executable name timestamp out 3 17 Chapter 4 Configuring Launcher 4 1 4 2 Launcher Tabs and Their Associated XML Files Launcher s tabs are defined using XML There are two kinds of XML configuration files for Launcher predefined ones and user customizable ones You should not modify the predefined XML files These XML files are in the Connext DDS Instal lation Directory in lt NDDSHOME gt resource app app_support launcher panels These files configure the following tabs Tools tab tools xml LJ Services tab services xml LI Utilities tab utilities xml 21 Third Party tab third party xml There are other Launcher configuration files that are intended to be customized by users You will find these file
18. ides Connext DDS application developers with a quick and easy to use mecha nism to try out realistic scenarios on their own computer systems and networks and get immediate information on the expected performance resource usage and behavior of their system It includes an embedded Lua scripting language engine for fast prototyp ing 1 RTI Package Installer installs additional components and libraries into an existing Con next DDS installation This utility accepts RTIPKG rtipkg extension files as its inputs Launcher s Tabs When you click on a utility button a configuration dialog will pop up Every utility has a differ ent dialog customized for its own needs For example the Code Generator dialog looks like this EB RTI DDS Code Generator rtiddsgen Input Input file CAUsersyjuanDocumentsVti workspace V5 2 0Nuser co J New Edit Input file format lt auto detect gt Disable pre processor Output Output directory same as input directory Generation Example files create h Language Traditional C no nar v Type files create d Platform i86Win32VS2008 M Makefiles create M V Show only installed target architectures Generate typecode Unbounded support Confirm command Advanced Options Platforms filter 3 3 4 Installation Tab The Installation tab provides general information regarding the
19. is C Documents and Settings your user name Documents You can specify a different location for the rti workspace directory See the RTI Connext DDS Core Libraries Getting Started Guide for instructions J path to examples Examples are copied into your home directory the first time you run RTI Launcher or any script in lt NDDSHOME gt bin This document refers to the location of these examples as path to examples Wherever you see path to examples replace it with the appropri ate path By default the examples are copied here e Mac OS X systems Users your user namelrti workspace versionlexamples e UNIX based systems home your user namelrti workspace versionlexamples e Windows systems your Windows documents folderNrti workspaceNversionNexamples Note your Windows documents folder is described above You can specify that you do not want the examples copied to the workspace See the RTI Connext DDS Core Libraries Getting Started Guide for instructions L NDDSHOME environment variable This variable appears in makefiles and project files and will be set to the Connext DDS installation path If you use applications commands from RTI Launcher this variable will be automatically set for you For details see the RTI Connext DDS Core Libraries Getting Started Guide 22 Chapter 3 Using RTI Launcher 3 1 Starting Launcher To start Launcher J On a Mac OS X system If you installed Connext DDS in the A
20. pplications directory the LaunchPad utility should show RTI Launcher in the Connext DDS folder rti connext dds version Click on it to open Launcher L On a UNIX based system You must have a graphical environment such as X11 GNOME or KDE running e Open a command prompt and navigate to the Connext DDS Installation Directory Run the script bin rtilauncher Alternatively use your browser to navigate to your Connext DDS Installation Directory s bin directory and double click rtilauncher J On a Windows system There are three ways to run RTI Launcher on a Windows system Inthe Start menu under All Programs find the entry called RTI Connext DDS lt ver sion Underneath there you will see RTI Launcher lt version gt Select it to start Launcher e Use Windows Explorer to navigate to your Connext DDS Installation Directory s bin directory For example C Program Files rti_connext_dds version bin Dou ble click rtilauncher bat e From a command prompt navigate to your Connext DDS Installation Directory bin and double click rtilauncher bat 3 2 License Management Launcher itself does not require a license file However some of the Connext DDS components may require a license file Launcher will aid you in making sure a license file can be found by 3 3 License Management 3 2 1 these applications when started from Launcher Launcher will look for the license file named rti license dat in three locations
21. ry of the ser vice See Section 3 3 for more about viewing command history 3 10 Launcher s Tabs 3 3 3 Utilities Tab The Utilities tab contains helper applications provided with Connext DDS to assist you when testing designing or inspecting your DDS system It also provides a Package Installer utility which makes it easy to install target platform libraries or additional components not included in the original bundle Tools Services hird Party Help Installation mas Code DDS Ping DDS Spy Type Convert Generator XML CSV V ej Record DDS RTI Package Convert Prototyper Installer gt Log J Code Generator also known as rtiddsgen generates the code to serialize and deserialize application data on the wire from an IDL or XML description of the data type It also generates example code and makefiles project files so you can quickly build a working application J DDS Ping also known as rtiddsping publishes and subscribes to DDS ping messages to test system connectivity J DDS Spy also known as rtiddsspy can subscribe to any DDS Topic and print out all the data being published 1 Type Convert converts data type formats between IDL and XML J Record Convert converts database files recorded by Recorder into readable commonly accepted formats such as CSV XML and HTML J DDS Prototyper accelerates Connext DDS application development and scenario testing It prov
22. s in your RTI workspace rti workspace version user config launcher panels directory You can use these files to configure the following tabs J Labs tab labs xml L User tab user xml How Launcher Finds Images Launcher looks for the image files to be shown for the applications in the following places LJ In the Connext DDS Installation Directory in lt NDDSHOME gt resource app app_support launcher icons This folder is used for RTI related applications and appli cations by RIT s partners shown in the Third Party tab In your RTI workspace directory under rti workspace version user config launcher icons This folder may not exist after installing and first running the tool To add user related images you have to create this folder and add your icon image files there J Absolute paths Launcher can detect files described as an absolute path to the image 1 See Chapter 2 Paths and Environment Variables Mentioned in Documentation 4 1 Example Adding a Button to Launcher s User Panel 4 3 Example Adding a Button to Launcher s User Panel The User tab is not visible the first time Launcher is run because it s empty by default and Launcher doesn t show tabs that are empty This tab is intended to be configured by the user This section shows how to add a button to the User tab s XML file so that appears in Launcher We ll use the Eclipse development environment as an example Tools
23. s tab contains applications that can be run directly without requiring any additional application specific setup The Tools tab includes the following applications J Admin Console provides a centralized tool for administering supervising and visualiz ing your distributed system It provides control over RTI services such as RTI Routing Service and RTI Recording Service offers a centralized way to receive and view log mes sages detects configuration errors including type and QoS mismatches and even data visualization capabilities you can subscribe to the topics in the system to see the data being published in real time J Monitor provides a graphical view to the internal configuration and operation of Con next DDS applications including QoS and detailed statistics on connections traffic errors and resource usage L Recording Console is a graphical front end for the Record and Replay services It can record real time data without having prior knowledge of the data types or topics in the system it can also replay that data back into the DDS cloud 3 7 Launcher s Tabs J Shapes Demo demonstrates Connext DDS capabilities by publishing and subscribing to colored moving shapes J Wireshark captures RTPS packets shows their contents and analyzes network usage L Spreadsheet Add in for Microsoft Excel integrates Connext DDS with Microsoft Excel You can use Excel cell functions to subscribe to topic data and then use the data
24. t Administrator privileges your home directory Nrti connext dds version e Windows systems user with Administrator privileges C Program Files rti_connext_dds version for 64 bits machines or C Program Files x86 Nrti connext dds version for 32 bit machines Wherever you see Connext DDS Installation Directory or lt NDDSHOME gt used in a path replace it with your installation path Note for Windows Users When using a command prompt to enter a command that includes the path C Program Files or any directory name that has a space enclose the path in quotation marks For example C Program Files rti_connext_dds version bin rtiddsgen or if you have defined the NDDSHOME environment variable SNDDSHOME bin rtiddsgen RTI Workspace directory rti workspace The RTI Workspace is where all configuration files for the applications and example files are located All configuration files and examples are copied here the first time you run RTI Launcher or any script in NDDSHOME bin The default path to the RTI Work space directory is 2 1 e Mac OS X systems Users your user namelrti workspace e UNIX based systems home your user namelrti workspace e Windows systems your Windows documents folderNrti workspace Note your Windows documents folder depends on your version of Windows For example on Windows 7 the folder is C Users your user name Documents on Windows Server 2003 the folder
25. t be visible LJ Labs Tab Section 3 3 6 1 Third Party Tab Section 3 3 7 LJ User Tab Section 3 3 8 To start one of the applications in a tab click on the application s button Some applications will launch directly such as RTI Admin Console Other applications like the ones in the Services or Utilities tab will pop up an application specific dialog This dialog allows you to configure the settings to run the application and then execute it 3 5 Launcher s Tabs Right clicking or Command Click on Mac OS a button will open a context menu with addi tional information and options Utilities Third Party User Help _ Installation M g View command history Command help Getting Started Guide PDF local User s Manual PDF local Release Notes PDF local The context menu may vary for every tool but in general the options are J View command history Launcher keeps track of all the successful command executions in the current Launcher session When you click this menu item it will open up the appli cation s Command History dialog which shows the command that was executed when it was launched and the working directory from where it was launched Timestamp Command Worlong Directory May 10 2015 C RTI 5 2 rti_connext_dds 5 2 0 bin rtiroutingservice bat cfgName default C Users juan Documents rti_workspace S 2 0 user_config routing_service M
26. te administration and sets the domain ID for the communication Default Use XML value restore 0 1 Indicates whether or not persistence service must restore its state from the persistent storage Default Use XML value noAutoStart Use this option if you plan to start RTI Persistence Service remotely Launcher s Tabs 3 3 1 For example J Document links Every application provides its own set of documentation or informa tion links these are shown in the context menu They may be local PDF files online PDF files online HTML links etc If a tool is not installed or cannot be used due to an expired license for instance its button will appear grayed out and will not work Launcher automatically detects the presence of the applications in various ways In the majority of cases Launcher looks for installed applications in the Connext DDS Installation Directory s bin directory For other applications it looks for in the Windows Registry On Linux systems Wire shark is found by using the UNIX which command Not all tools are available on all platforms For example the RTI Spreadsheet Add in for Micro soft Excel is only available on Windows systems Tools Tab Fr rti RTI Connext Launcher 520 UU cE Services Utilities Third Party Help M Installation s OOOO Recording Console Shapes Demo I Spreadsheet Add in for Microsoft Excel The tool
27. to be installed Record DDS RTI Package Convert Prototyper Installer gt Log J At this point select the RTIPKG files to be installed If you click on the button a file chooser dialog will appear allowing you to navigate to the file s you want to install You can also drag Troubleshooting with Launcher and drop RTIPKC files into this window Once the files are selected click the Install button The install commands are launched sequentially A progress dialog will appear o Running commands Executing command 2 2 C RTI 5 2 rti_connex t_dds 5 2 0 pro target i86Win32VS2010 rtipkg 3 5 Troubleshooting with Launcher Launcher provides two debugging or troubleshooting mechanisms Troubleshooting with Launcher 1 Log view Launcher produces log messages when it performs an action an error occurs etc You can access these log messages from any of the tabs by clicking on the expandable Log view When clicked the view will expand and show all the messages produced up to that point Tools Services Utilities Third Party User Help _ Installation DDS Ping DDS Spy Type Convert mov Record DDS RTI Package Convert Prototyper Installer hast v Log 13 58 15 RTI Connext Launcher 5 2 0 started 13 58 17 Error creating context menu for tool Eclipse 13 58 21 Run eclipse exe C Eclipse
Download Pdf Manuals
Related Search
Related Contents
添付資料 訪問支援報告書 A社 Tango Device Server User's Guide Delta 561LF-SSTP Installation Guide 千葉商談会出展マニュアル ARCTIC S151 Parite-bien-ordonnée-commence-par-soi-meme! FÉLICITATION ! Copyright © All rights reserved.
Failed to retrieve file