.. include:: vars.rst .. _section-gsg_before: Before You Get Started ********************** .. _section-gsg_before_what_is: What is Connext DDS? ==================== .. figure:: static/what_is.png :scale: 50 % :alt: What Is Connext DDS? :name: FigureWhatIs :align: center *RTI® Connext® DDS* is a connectivity framework for building distributed applications with requirements for high performance and scalability. It includes these components: - An **SDK** that provides you with APIs to help you send and receive data using the communication patterns described in this documentation (see :ref:`section-gsg_intro_next`). These APIs allow you to connect your own applications to other applications on the databus. - **Tools** that help you visualize your data and debug your distributed system. - **Infrastructure Services** that can perform dedicated functions in your system, such as recording, bridging, and persisting data. .. _section-gsg_download: Downloading Connext DDS ======================= If you haven't already purchased a |CONNEXT| bundle, you can follow this Getting Started guide with an evaluation bundle. To obtain an evaluation bundle, click the Free Trial button at https://www.rti.com/. Fill out the brief form, and you will receive an evaluation package shortly. .. _section-gsg_install: Installing Connext DDS ====================== A |CONNEXT| installation typically consists of a host bundle followed by one or more target bundles. To install |CONNEXT|, you must first install the host bundle, then choose which target (SDK libraries) to install. .. note:: If you have installed a "license-managed" bundle (usually used for evaluation purposes), you do not need to install a target. License-managed bundles combine both the host and target in one package. They have ``lm`` in their name, such as ``rti_connext_dds-6.1.0-lm-x64Win64VS2017.exe``. The ``lm`` bundle already installed the SDK libraries, so you can go straight to :ref:`section-gsg-license`. |CONNEXT| distributions are provided in two types of bundles: - A **host** bundle that contains files such as documentation, header files, tools, and infrastructure services executables. The host bundle is provided in a **.run** or **.exe** file that will run an installer. |br| Host bundles are named: .. tabs:: .. group-tab:: Linux ``rti_connext_dds---host-.run`` .. group-tab:: macOS ``rti_connext_dds---host-.dmg`` .. group-tab:: Windows ``rti_connext_dds---host-.exe`` The ```` is usually ``pro``. |br| The ```` depends on your development platform, such as ``x64Win64`` for a 64-bit Windows® platform. |br| |br| - A **target** bundle that contains SDK libraries you will link against. If you are developing for a cross-compiled architecture, this will also include any applications that are supported for your architecture. A target bundle is an “RTI Package” (**\*.rtipkg**) file that must be installed on top of your host bundle. After you install the host bundle, you will have a script called ``bin/rtipkginstall[.bat]``. You can use this script to install one or more target bundles. Or you can use *RTI Launcher* to install the target bundles. (*Launcher* is installed as part of the host bundle.) See :ref:`section-gsg_install_gui`. |br| Target bundles are named: |br| ``rti_connext_dds---target-.rtipkg``. The ```` depends on your target machine (where you will deploy your completed application). Your ``architecture`` is the combination of a processor, OS, and compiler version that you will use to build your application. For example, if you have a 64-bit Windows machine with Visual Studio® 2017, use ``x64Win64VS2017``. For a 64-bit Linux machine with gcc version 5.4.0, use ``x64Linux3gcc5.4.0``. To see the full list of available architectures, see the "RTI Architecture Abbreviation" columns in the :link_platform_notes:`RTI Connext DDS Core Libraries Platform Notes <>`. .. note:: A few notes about target bundles: - You will need to install more than one target bundle if you are developing for multiple target architectures, such as developing for both Linux® and VxWorks® systems. - You must have a target bundle even if you are developing for Java®. This is because |CONNEXT| requires native libraries as well as the Java SDK. If you are on a Windows system, you can generally install any Windows architecture if you plan to develop with Java. - However, a target installation is not necessary for building or running C# applications. The NuGet package contains the necessary native libraries. Installing a Host ----------------- The host bundle is an application; thus, it can be started from a GUI or command line. To install the host bundle, do either of the following: - Double-click the installer. - Run the installation script from a command prompt. See :link_installation:`Installing RTI Connext DDS, in the RTI Connext DDS Installation Guide <>`. .. _section-gsg_install_gui: Installing a Target with a GUI ------------------------------ After you install the host bundle, you’ll have a tool called *RTI Launcher*. (See :link_launcher_starting:`Starting Launcher, in the RTI Launcher User's Manual <>`.) To install a target bundle from the *Launcher* tool, open the Configuration tab, and select “Install RTI Packages.” This will open a dialog that allows you to select one or more **.rtipkg** files that you would like to install. .. figure:: static/install_rti_pkg.png :figwidth: 80 % :alt: Install RTI Packages :name: FigureInstallPackages :align: center .. figure:: static/pkg_installer.png :figwidth: 80 % :alt: RTI Package Installer :name: FigurePackageInstaller :align: center .. _section-gsg_install_cmd: Installing a Target from a Command Line --------------------------------------- To install targets from the command line, type: .. tabs:: .. group-tab:: Linux .. code-block:: console $ /bin/rtipkginstall .. group-tab:: macOS .. code-block:: console $ /bin/rtipkginstall .. group-tab:: Windows .. code-block:: doscon > \bin\rtipkginstall .. _section-gsg_paths: Paths Mentioned in Documentation -------------------------------- .. include:: paths_gsg.txt .. _section-gsg-license: Setting Up a License ==================== Most installations require a license file to run the tools or features included in the |CONNEXT| platform. If your distribution requires a license file, you will receive one from RTI via e-mail. The easiest way to configure your license file is using *Launcher*, as shown below: .. figure:: static/config_license.png :figwidth: 80 % :alt: Configure License :name: FigureConfigLicense :align: center If you do not want to use *Launcher*, you can also install a license by placing it in one of these two locations: - ``/rti_license.dat`` - ``/rti_license.dat`` The workspace directory is in this location by default, depending on your operating system: .. tabs:: .. group-tab:: Linux ``/home//rti_workspace/`` .. group-tab:: macOS ``/Users//rti_workspace/`` .. group-tab:: Windows ``\rti_workspace\`` A third way to install a license is to configure the environment variable ``RTI_LICENSE_FILE`` to point to your license file. For more details, see :link_license_management:`the License Management section in the RTI Connext DDS Installation Guide <>`. .. _section-gsg_check_install: Checking What is Installed ========================== To find out what target libraries or add-ons you have installed, you can use the *Launcher* tool. See :link_launcher_starting:`Starting Launcher, in the RTI Launcher User's Manual <>`. Once in *Launcher*, open the Configuration tab: .. figure:: static/check_installed.png :figwidth: 80 % :alt: Check What Is Installed :name: FigureCheckInstall :align: center To check which target architectures you have installed, click on Connext Target Libraries, which will show you each installed target library and its version. If you do not see any target libraries listed, you are missing a vital part of the |CONNEXT| SDK, and you will not be able to compile your own applications. You can still run tools such as *RTI Admin Console*. .. _section-gsg_install_help: Where Do I Get More Help? ========================= Advanced installation help can be found in the :link_install_guide:`RTI Connext DDS Installation Guide `, which explains: - Installer command-line options - Controlling the location of the RTI Workspace directory - Additional license management options - Special backup of RTI libraries - How to uninstall |CONNEXT| Continue to :ref:`section-gsg_intro_cpp11` to start learning about the capabilities and features of |CONNEXT|. Additional documentation and user forums can be found on \ `community.rti.com `__\ .