1. Pre-Configuration of LIVE EVENTS

In order to use the LIVE DASH web reporting component, the LIVE EVENTS software must first be installed and configured according to the required installation and configuration procedures.

Before LIVE DASH is enabled, LIVE EVENTS must be configured so that it can connect to the relevant SCADA and/or Event Recorder systems, access the required data archives, and keep the necessary services active.

Important: The LIVE DASH component cannot be used until LIVE EVENTS has been properly configured. Before proceeding with LIVE DASH installation, verify that the LIVE EVENTS configuration has been completed.

2. Configuring HTTP Publishing Settings

The required settings for the LIVE DASH component to access the HTTP publishing service through LIVE EVENTS must be configured in the EOSliveevents.xml configuration file.

  1. Open the EOSliveevents.xml file located in the directory where LIVE EVENTS is installed using Notepad or a similar text editor.
  2. Set the <HTTPYayinAktif> parameter to True.
  3. Enter the IP address of the computer running LIVE EVENTS in the <YayinServerIP> parameter.
  4. Enter the port number to be used for HTTP publishing in the <HTTPYayinPortu> parameter.
Default HTTP port: 80. A different port number may be configured depending on the plant network policies and the existing configuration.
Example Configuration: 
<HTTPYayinAktif>True</HTTPYayinAktif>
<YayinServerIP>192.168.1.50</YayinServerIP>
<HTTPYayinPortu>80</HTTPYayinPortu>
Note: The configured IP address and port must be accessible by LIVE DASH clients, and the relevant firewall rules must allow the connection. Restarting the LIVE EVENTS services after changing these settings is recommended.

3. LIVE DASH Report Data Preparation Start Date

LIVE EVENTS automatically prepares the report data used by LIVE DASH in the background. The <DTStartLimit> parameter in EOSliveevents.xml is used to define the date from which this preparation process should begin.

The <DTStartLimit> value specifies the starting date from which LIVE EVENTS begins preparing data for LIVE DASH reports. From this date onward, the data required for reports is automatically preprocessed and archived.

Example Configuration: 
<DTStartLimit>01.01.2025</DTStartLimit>

In this example, LIVE EVENTS will begin preparing data for LIVE DASH reports starting from 01.01.2025.

Preparing the data in advance in the background allows reports to be delivered more quickly when requested, without requiring the relevant data to be recalculated at the time of the report request.

Note: When defining the <DTStartLimit> value, the amount of archived data as well as CPU, disk, and memory resources should be taken into consideration. Selecting a very old date may cause the initial data preparation process to take a long time.

4. Live Data Update Settings

The LIVE DASH component supports the live data feature. This feature allows the latest state of the relevant data to be displayed live in report blocks where individual data is requested.

The live data update frequency is defined by the <LiveDataRefresh> parameter in the EOSliveevents.xml file. The value is specified in milliseconds (ms).

Example Configuration: 
<LiveDataRefresh>5000</LiveDataRefresh>
Default value: 5000 milliseconds (5 seconds). This value can be reduced or increased according to operational requirements; however, very short update intervals may increase the system load.
Note: A high number of users combined with short update intervals may create additional load on network traffic and LIVE EVENTS server resources. The update interval should be determined according to the plant's operational requirements and system capacity.

5. Saving the Settings and Restarting the Software

After completing the configuration changes, the EOSliveevents.xml configuration file must be saved.

For the settings to take effect, the EOSLiveEvents.exe application or the relevant LIVE EVENTS services must be restarted.

6. Verifying the HTTP Publishing Status

After the configuration has been completed and EOSLiveEvents.exe has been restarted, an HTTP LED indicator showing the HTTP publishing status appears on the status bar at the bottom of the LIVE EVENTS application.

HTTP LED GREEN: The HTTP publishing service has started successfully and communication with the LIVE DASH component is available.
HTTP LED RED: The HTTP publishing service could not be started. Possible causes include:
  • An incorrect IP address in the <YayinServerIP> parameter.
  • The port defined by <HTTPYayinPortu> is already being used by another application (port conflict).
  • The port is blocked by the operating system firewall or third-party security software.

After the required checks and corrections have been completed, LIVE EVENTS should be restarted and the HTTP LED status should be verified again.

7. Accessing the LIVE DASH Web Interface

If the HTTP publishing service is running, the LIVE DASH web interface can be accessed through any Internet browser.

Enter the following address in the browser's address bar using the <YayinServerIP> and <HTTPYayinPortu> values:

General access format: 
http://<YayinServerIP>:<HTTPYayinPortu>
Example: 
http://192.168.1.50:8080

If the <HTTPYayinPortu> value is 80, it is not necessary to specify the port number separately.

Example for Port 80: 
http://192.168.1.50

8. User Login

After accessing the LIVE DASH web interface, the user is presented with the LOGIN page.

On this screen, users can log in to the LIVE DASH system using any valid username and password defined in the SCADA project.

LIVE DASH uses the existing user and authorization infrastructure of the SCADA system for user authentication. This provides controlled access using existing SCADA users without requiring separate user definitions.

Note: The username and password must be active and authorized in the SCADA system. LIVE DASH cannot be accessed using unauthorized or inactive users.

9. Completing the Installation and Next Steps

After the username and password have been entered correctly, the LIVE DASH Home Page is displayed. Successfully opening the home page indicates that the LIVE EVENTS and LIVE DASH components have been configured correctly and that the installation has been successfully completed.

After the installation is complete, the reports to be displayed in the LIVE DASH web interface must be created. For this purpose, the ReportDesigner.exe application located in the LIVE EVENTS program directory is used to design the required reports through the Web Reporting Tool.

Report design includes steps such as selecting report blocks, defining data sources, specifying time ranges, and configuring visual components. Detailed information about these stages is covered in the relevant report design documentation.

10. Configuration Process Summary

Step Operation
1 Verify that the LIVE EVENTS software has been properly configured.

2 Define the HTTP publishing settings in EOSliveevents.xml.
3 Define the starting date for LIVE DASH report data preparation using DTStartLimit.
4 Define the live data update interval using LiveDataRefresh.
5 Save EOSliveevents.xml and restart LIVE EVENTS.
6 Verify the status of the HTTP publishing service by checking the HTTP LED indicator.
7 Access the LIVE DASH web interface through a browser.
8 Log in using valid user credentials defined in the SCADA system.
9 Display the LIVE DASH Home Page and then proceed to report design using ReportDesigner.
← Back to Previous Content