2.4.8.12. Process View

2.4.8.12.1. Overview

The Process View provides panels that display the DDS entities related or contained within a process, the process’s log (populated through Distributed Logger; this tab only appears if Distributed Logger is enabled for the process), and a basic information panel.

2.4.8.12.2. Graphical View

The Process Graphical View shows how a Process is connected to other entities in the DDS System. This view will help you understand the entities that matched with the DataWriters and DataReaders created by the process, and which DDS system entities are relevant for the selected process.

Process view graph view

The Graphical View uses the same approach as the Topic View to indicate the match analysis status of every DataWriter and DataReader in the graph.

Note

For information on how the Publishers and Subscriber are named, please see the section Publishers and Subscribers names

The information in this view is organized in a way to ensure that the Process Node is always located on the left side of the graph.

In the center of the graph, you will see the nodes that represent the Topics that the Process is connected to.

On the right side, you will see the other nodes that are connected to all the entities created by the Process. The Process node will move up and down as you scroll through the graph. Having the Process node always visible can help you see how the process is connected to the rest of the entities.

Note

This view is the only graphical representation in which you may see the same entity more than once. The Host node where the Process is running may appear on both the left and right sides, if it contains more than one process running, and the second process is relevant for the process that is driving the visualization of the graph.

2.4.8.12.3. DDS Entities

The DDS Entities tab displays a hierarchical view of the DDS entities that were created by that process. The tree starts with the process IMAGE_RUNNING_PROCESS itself, which then contains DomainParticipants IMAGE_PARTICIPANT, Publishers IMAGE_PUBLISHER, DataWriters IMAGE_DATA_WRITER, Subscribers IMAGE_SUBSCRIBER, and DataReaders IMAGE_DATA_READER.

Health badges for errors IMAGE_ERROR and warnings IMAGE_WARNING are also used to convey health state information.

Process view graph view dds entities

2.4.8.12.3.1. Log

The Log tab displays the processes’ log messages. This display requires that the process is using Distributed Logger.

Distributed log

The Distributed Logger table consists of these columns:

  • Message ID - The ID of the message.

  • Time - The time the log message was written.

  • Level - The level of the message.

  • Category - The logger category name.

  • Message - The message.

There are also buttons to pause updates to the table, export the contents of the table to a file, and adjust the settings used by the remote process’s Distributed Logger library.

2.4.8.12.3.2. Remote Settings Dialog

Distributed log settings dialog

The Distributed Logger remote settings dialog controls the instance of the Distributed Logger library being used by the remote process. You can adjust the filter level, print format, and verbosity of the individual log categories. This dialog also displays the state, and last update time.

2.4.8.12.3.3. Security Log

The Security Log tab displays the process’s security log messages. This display only appears when the Security Logger is enabled for the remote process.

Process view security log

The Distributed Logger table consists of these columns:

  • Time - The time the log message was written.

  • Level - The level of the message.

  • Message - The message.

  • Structured Data - Further details related to the log message.

There are also buttons to pause the updates to the table and to export the contents of the table to a file.

2.4.8.12.3.4. Process Information

Process view process information

The Process Information tab displays some basic information about the processes such as the Connext version being used, who is running the process, and some relevant timestamps. Note that the RTI Architecture Name reflects the native architecture and not that of a layered API binding. In particular, don’t be confused when Java and .Net processes are reported as OS-native architectures.