Simple System Integration

The Simple System Integration UI is the central UI to integrate technical systems into the Focused Run monitoring. It can be used for:

  • Integration and configuration of technical systems for monitoring with Focused Run applications
  • Search of technical systems and display of configuration status and possible issues
  • Change configuration parameters and trigger reconfiguration

For an overview on Simple System Integration please refer to the Product Information.

User Interface


The Simple System Integration UI is divided into three areas:

  • Search Area
    The user can search technical systems by some criteria. Most notable the Extended System ID, the System Type and Customer ID. If the Extended System ID is unknown, a wildcard ‘*' must be used. The search filter can be changed by with the Filters link in right upper corner (see next image).

  • Result Area
    The result area displays the result of a search. For each system, it displays some essential information. Depending on the technical systems found, several actions are available in the action buttons row. Some of the actions are also available for multiple selected technical systems: Establish Prerequisites, Configure Automatically and Refresh Selected.
    It's important to understand the meaning of the first two columns representing the status of the system:
    • Prerequisites Status: To configure a technical system for Focused Run monitoring, several prerequisites, depending on the type of system, must be met. The status symbol here represents the last known status of these prerequisites. To get the fresh results, select the desired technical system and use button Establish Prerequisites.
    • Configuration Status: The configuration status represents the last known status of the configuration of a technical system for Focused Run. Since the configuration, including communication settings between monitored system and Focused Run, depends on settings which can be influenced by or changed from other tools or administrative actions, this status may get outdated.
      • If a technical system needs to be (re)configured, select the system and use button Configure Automatically.
      • Button Configure Manually opens another UI, with a more detailed view of the configuration procedure. It can be used by experts in case of failing configurations.
      • Please note, a successful configuration requires a green status on the prerequisites.
  • Log Area:
    The Log Area provides a log of the actions and results taken by the procedures (establish prerequisites, configure technical system). The logs are only available for a single selected system in the result area.

Actions available in the result area:

  • Display System: Opens the LMDB UI for the selected technical system
  • Edit Configuration: Opens a dialog to adjust the technical system specific parameters. The parameters differ per technical system type. Closing the dialog and saving data will trigger a reconfiguration of the system if the Lifecycle Status of the selected system was Active.

  • Establish Prerequisites: Trigger the procedure to establish if all prerequisites for selected systems are met. The procedure is also part of a full configuration of a technical system to prevent erroneous configurations.
  • Configure Automatically: Trigger the procedure to configure selected technical systems for Focused Run.
  • Configure Manually: Opens an UI for experts to execute the configuration procedure with access to details.
  • Refresh Selected: Refresh the displayed information for the selected technical systems.


  • How can I speed up the search?
    Using more specific search parameters can speed up the search significantly. A wild card search on Extended SID without any other parameters will return all systems known and will therefore be considerably slower. If the search returns many systems, the number of displayed systems is limited by the relevant option (dropdown technical system to display) in the results area.
  • I changed parameters with the Edit Configuration dialog. The automatic configuration does not start. Why?
    The change of parameters will trigger a new configuration if the system has been configured before and the Lifecycle Status was therefore Active. If so, please check if there was any message about invalid parameter values.
  • A configuration of a technical system did not only configure this system but also triggers the configuration of databases. Why?
    Technical systems usually rely on a certain database. Since they make up a functional unit, the respective databases will be configured for Focused Run with their technical systems. Databases can also be standalone, without such affiliation to another technical system. Such databases must be configured explicitly just as any other technical system.
  • Why does a configuration take that long?
    The configuration of a technical system involves many steps, exchange of communication parameters and further configuration data for Focused Run applications for all hosts and affiliated databases involved. This can be time consuming, and it depends on the overall system workload. Use the action Refresh Selected to get the last known status of the system selected.
  • Where can I find more details about a Technical System?
    More details can be found in the LMDB, accessible for a selected technical system using the action Display System. More details about the configuration steps taken can be found using the action Configure Manually. It is recommended to use this option only if it is needed to troubleshoot failing configurations.