Expand
title Benutzte Symbole und Bezeichnungsschlüssel
Info Information Note Important information and warnings DELETE Windows function, e.g. Delete <xxxxxxxx> Syntax for placeholders. Placeholders are written between < > characters. >> Reference to a further chapter or document. → Path (e.g. Control > Panel > System > Remote). Italic Windows window text underlined Input during installation The representation refers only to a part of the user interface. Info In the interest of our customers, we reserve the right to make changes based on technical advances. Therefore, schematics, descriptions and scope of delivery may be changed without prior notice. This manual is valid as of version 2017.

1. System Requirements

1.1. Supplied Program Packets

The list below contains the software packets supplied.

3. Definition of Target System

Before you start the installation, define how the target system should look like.

3.1. Default Proposal to Create New Users

3.2. Default Proposal to Create New Databases

3.3. Default Proposal to Create Directories

4. Installing the Basic System

4.1 Server

4.1.1. Server Setup

• Standard server installation

• Configure server name

  Control Panel → System → Change Settings → Computer Name → Change

  • Enter new name:
    e.g. MONITOR

4.1.2. Firewall Configuration

4.1.2.1. Activate Remote Desktop Service

• Remote Desktop
  Control Panel → System → Change settings → Remote → Remote Desktop

  • Allow
    Allow remote connection on this computer only from computers running Remote Desktop with Network Level Authentication.

• Firewall Rules
  Control Panel → Windows Firewall → Advanced Settings → Inbound Rules

  • Allow
    Remote Desktop - User Mode (TCP-In) Profile Public

4.1.2.2. Allow Ping

• Firewall Rules
  Control Panel → Windows Firewall → Advanced Settings → Inbound Rules

  • Allow
    File and Printer Sharing (Echo Request - ICMPv4-In)

4.1.2.3. Firewall ports and protocol overview

4.1.2.4. Firewall Rules

http://msdn.microsoft.com/de-ch/library/ms175043.aspx

4.2 IIS Installation

IIS must be installed on the computer on which the web application is to run.

• Start Server Manager.

• Right-click Roles → Add Roles in order to start the Add Roles Wizard.

  • Depending on the version of the Windows Server, select Installation Type → Rolebased or feature based installation

• Select Web Server (IIS).

• Use the following Settings in the Role services section.
  Web Server
  Common HTTP Features
  Static Content
  Default Document
  Directory Browsing
  HTTP Errors
  Application Development
  ASP.NET (3.5 und 4.5) - only ECOLOG NET relevant
  .NET Extensibility (3.5 und 4.5) - only ECOLOG NET relevant
  ISAPI Extensions
  ISAPI Filters
  Health and Diagnostics
  HTTP Logging
  Request Monitor
  Security
  Request Filtering
  Performance
  Static Content Compression
  Management Tools
  IIS Management Console

4.2.2. Windows Update

• Execute Windows Update to ensure that all patches are installed for the .NET Framework.

4.3. MS SQL Server

4.3.1. Basic Installation (for example, with MSSQL 2019 Full Version)

• Start SQL Server Installer.

• Left-click Installation.

• Select New SQL Server stand-alone installation.

  • Click through the licensing instructions and confirmations.

• SQL Server Feature Installation

  • Select
    Database Engine Services
    Management tools – Basic
    Management Tools - Complete

• Define server instance.
  e.g. Default instance, InstanceID ELPRODBSERVER

• In the section Server Configuration under Service Account, set the Startup Type of the SQL Server Browser to Automatic.

• In the section Database Engine Configuration under Server Configuration → Authentication Mode, select the option Mixed Mode (SQL Server authentication and Windows authentication) and define a password for “SA” users.

• Click through to Installation and then close.

• Start SQL Server Configuration Manager.

• Navigate to SQL Server Network Configuration → Protocols for MSSQLSERVER and check if TCP/IP is set to Enabled.

• Double-click on TCP/IP to open Properties.

• a Change to the IP Addresses tab and in the section IP2, check the following settings and adapt, if necessary:
  IP Address: <Server IP address>
  TCP Dynamic Ports: <empty>
  TCP Port: 1433

• If changes to the settings have been made, save them by clicking Apply.

• Close SQL Server Configuration Manager and reboot the Windows Server.

4.4. Copy Program and Webclient files

4.5. Installing Redistributables

4.5.1. Installation MSVC 2013 Redistributables

• Execute …\Setup Files\MSVC 2013 Redistribuatable\vcredist_x64.exe.

• Select the checkbox "I agree to the license terms and conditions" and press Install.

• The redistributable is installed. After installation, confirm with Close.

4.5.2. Installation MSVC 2015 Redistributables

• Execute directory …\Setup Files\ MSVC 2015 Redistribuatable \vc_redist.x64.exe.

• Select the checkbox "I agree to the license terms and conditions" and press Install.

• The redistributable is installed. After installation, confirm with Close.

Anchor
4.6.-RabbitMQ-Installation 4.6.-RabbitMQ-Installation

4.6. RabbitMQ Installation

Find these prerequisite Installation FIle in the Release package or download here:

• RabbitMQ 3.12.10 - download from https://github.com/rabbitmq/rabbitmq-server/releases

• Erlang/OTP 26.1.2 - download from https://www.erlang.org/downloads

4.6.1. Install Erlang/OTP

Download the installer and run the exe file. Installer wizard help you through the install process.

4.6.2. Download rabbitmq_message_timestamp plugin

4.6.3. Install RabbitMQ

Enable the RabbitMQ Management web interface and MQTT

4.6.3. Install RabbitMQ

Enable the RabbitMQ Management web interface and MQTT

"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-plugins.bat" enable rabbitmq_management
"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-plugins.bat" enable rabbitmq_mqtt
"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-service.bat" stop
"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-service.bat" start

4.6.4. Apply the advanced configurations

• Stop the service

"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-service.bat" stop

• Copy the file RabbitMQ.conf from installation package to destination folder.
  destination folder: c:\Programdata\ELPRO\RabbitMQ

• Start the service

"c:\Program Files\RabbitMQ Server\rabbitmq_server-3.12.10\sbin\rabbitmq-service.bat" start

4.6.5. Settings to set in elproMONITOR’s database (dbo.Settings table)

Default values are shown below:

• RabbitMQPortAMQP 5672 unencrypted or 5671 encrypted

• RabbitMQPortMQTT 1883 unencrypted or 8883 encrypted

4.6.6. Import the RabbitMQ configuration on the management UI

• Open the >> RabbitMQ management interface - http://<IP-Address>:15672 (

• Login (Standard admin credentials User: guest, Password: guest)

• Navigate to Overview and select Import definitions

• Import the following file: (change credentials if needed)

{
	"rabbit_version": "3.12.10",
	"rabbitmq_version": "3.12.10",
	"product_name": "RabbitMQ",
	"product_version": "3.12.10",
	"users": [
		{
			"name": "mqtt-anonymous-user",
			"password_hash": "I6aekaYGkw8lzLTd162z123gM9l0komfZLGoVN16yH6tKUNT",
			"hashing_algorithm": "rabbit_password_hashing_sha256",
			"tags": "management"
		},
		{
			"name": "guest",
			"password_hash": "V/VMfaMiD8rqX5XUj/j6MelP0uYZ5wJOvZhNNu/9oMwT5+yl",
			"hashing_algorithm": "rabbit_password_hashing_sha256",
			"tags": "administrator"
		}
	],
	"vhosts": [
		{
			"name": "/"
		}
	],
	"permissions": [
		{
			"user": "mqtt-anonymous-user",
			"vhost": "/",
			"configure": ".*",
			"write": ".*",
			"read": ".*"
		},
		{
			"user": "guest",
			"vhost": "/",
			"configure": ".*",
			"write": ".*",
			"read": ".*"
		}
	],
	"topic_permissions": [],
	"parameters": [],
	"global_parameters": [
		{
			"name": "cluster_name",
			"value": "rabbit@WIN-2KUAD2N2RAI"
		},
		{
			"name": "internal_cluster_id",
			"value": "rabbitmq-cluster-id-orZSP-j34Bgdonr8S46dEw"
		}
	],
	"policies": [],
	"queues": [
		{
			"name": "uplink.module.measurements",
			"vhost": "/",
			"durable": true,
			"auto_delete": false,
			"arguments": {
				"x-queue-type": "classic"
			}
		},
		{
			"name": "uplink.module.others",
			"vhost": "/",
			"durable": true,
			"auto_delete": false,
			"arguments": {
				"x-queue-type": "classic"
			}
		},
		{
			"name": "uplink.bridge",
			"vhost": "/",
			"durable": true,
			"auto_delete": false,
			"arguments": {
				"x-queue-type": "classic"
			}
		}
	],
	"exchanges": [
		{
			"name": "rbr.uplink",
			"vhost": "/",
			"type": "direct",
			"durable": true,
			"auto_delete": false,
			"internal": false,
			"arguments": {}
		}
	],
	"bindings": [
		{
			"source": "rbr.uplink",
			"vhost": "/",
			"destination": "uplink.bridge",
			"destination_type": "queue",
			"routing_key": "~uplink.bridge",
			"arguments": {}
		},
		{
			"source": "rbr.uplink",
			"vhost": "/",
			"destination": "uplink.module.measurements",
			"destination_type": "queue",
			"routing_key": "~uplink.module.measurements",
			"arguments": {}
		},
		{
			"source": "rbr.uplink",
			"vhost": "/",
			"destination": "uplink.module.others",
			"destination_type": "queue",
			"routing_key": "~uplink.module.others",
			"arguments": {}
		}
	]
}

4.6.7. Nice to know: Configure RabbitMQ manually

rabbitmqctl.bat add_user "mqtt-anonymous-user" "Password1234"
rabbitmqctl.bat set_permissions -p / "mqtt-anonymous-user" ".*" ".*" ".*"
rabbitmqctl.bat set_user_tags "mqtt-anonymous-user" management

Name: rbr.uplink
Type: direct
Durability: durable
Auto-delete: false
Internal: false
Arguments: empty
Name: rbr.uplink.measurements
Type: direct
Durability: durable
Auto-delete: false
Internal: false
Arguments: empty

Name: uplink.module.measurements
Type: classic
Durability: durable
Auto-delete: false
Arguments: empty
Name: uplink.bridge
Type: classic
Durability: durable
Auto-delete: false
Arguments: empty
Name: uplink.module.others
Type: classic
Durability: durable
Auto-delete: false
Arguments: empty

From exchange: rbr.uplink
Routing key: ~uplink.bridge
Arugments: empty

From exchange: rbr.uplink
Routing key: ~uplink.module.others
Arugments: empty

From exchange: rbr.uplink
Routing key: ~uplink.module.measurements
Arugments: empty

Anchor
5.-Datenbanken-einrichten 5.-Datenbanken-einrichten

5. Creating Databases

5.1 Create Application-Specific DB Logins

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Create Login names:
  elproMonitorDBUser
  elproEventDBUser
  elproUserDBUser

5.1.2. Procedure to create new Login names

1. Right-click <server name> → Security → Logins → New Login… to open the window to create a new user.

2. Select the option SQL Server authentication, enter <Login name> under Login name:, and enter a password (e.g. elpro).
   Alternatively select Windows authentication and then select the required Windows User. Finally omit the next two steps.

3. Untick the following checkbox:

   • User must change password at next login

4. Left-click on Server Roles and tick the checkboxes for public in the list.

 5. Create login by clicking OK.

5.2. Setting up elproMONITOR

5.2.1. Create the New elproMONITOR Database

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Right-click Databases → New Database.

• Enter the database name under Database name. (e.g. elproMONITOR)

• If required, change DB Owner and the memory location for the database file and the database logfile (under Path).

• Create database by clicking on OK.

5.2.2. Create New Main User in elproMONITOR Database

• Start SQL Server Management Studio and connect to the database as DB Administrator.

• Right-click <server name> → Databases → <elproMONITOR> → Security → Users → New User… to open the window to create a new user

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproMONITOR.

• In the list on the Membership page, select the entries db_datareader and db_datawriter.

• Create User by clicking OK.

5.2.3. Create Database Schema

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Double-click on<Setupdirectory>\SetupFiles\SQLScripts\ MonitorSchema3.0.0.sql to open.

• Click in the window of the open script. Call Query → Specify Values for Templates Parameters…(Ctrl+Shift+M) and enter the name of the previously created database. (e.g.: DatabaseName elproMONITOR)

• Close the Template Parameters window by clicking OK.

• Click Execute(F5) to execute the script.

Create elproUserDBUser in the elproMONITOR Database and Assign User Rights

• Start SQL Server Management Studio and log in to the database as a DB Administrator.

  Right-clickthe<servername>folder→Databases→<elproMONITOR>→Security →Users→New User… to open the window for the creation of a new user.

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproUSER.

User type

SQL user with login

User name

elproUserDBUser

Login name

elproUserDBUser

Default schema

dbo

5.2.4 Remove Duplicate Null Measurements (Gap filler)

• for installing a brand new eM 3.x version with a clean database:
  nothing is required to be run manually after executing CreateSchema.sql as the original issue has been fixed.
  

• for freshly upgrading an existing older elproMONITOR installation to 3.x+ version:
  ELPRO.elproMONITOR.RemoveDuplicateNullMeasurements.sql is required to be run manually after executing CreateSchema.sql.
  
  This script is exactly the same as the one we used for fixing an existing eM 2.2.x installation. This script is part of the installation artifact we create and can be found next to the CreateSchema.sql file and it will delete faulty measure values with timestamp of 1900-01-01 00:01:01.000 and it will also delete faulty NULL measure values where other valid measure values are present.

5.2.5. Create elproUserDBUser in the elproMONITOR Database and Assign User Rights

• Start SQL Server Management Studio and log in to the database as a DB Administrator.

  Right-clickthe<servername>folder→Databases→<elproMONITOR>→Security →Users→New User… to open the window for the creation of a new user.

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproUSER.

• On the Securables page, click Search….

• In the following Add Objects window, select the option Specific objects… and click OK.

• In the following Select Objects window, click top right on the button Object Types…, tick the checkbox in Tables in the new Select Object Types window, and close the window by clicking OK.

• Back in the Select Objects window, right-click on Browse…. In the new Browse for Objects window appearing, tick the following checkboxes:

  • [dbo].[Applications]

  • [dbo].[FunctionNames]

  • [dbo].[Functions]

  • [dbo].[Languages]

  • [dbo].[Resources]

• Click OK to close the Browse for Objects and the Select Objects windows.

• Under Permissions for dbo….: tick the checkbox for Grant for these 5 tables in the following entries:
  Select
  View Definition

• Create User by clicking OK.

5.3. Setting up elproEVENT

5.3.1. Create New elproEVENT Database

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Right-click Databases → New Database.

• Enter the database name under Database name. (e.g.: elproEVENT)

• If required, change DB Owner and the memory location for the database file and the database logfile (under Path).

• Create database by clicking OK.

5.3.2. Create New Main User in elproEVENT Database

• Start SQL Server Management Studio and log in to the database as a DB Administrator.

• Right-click the <server name> folder → Databases → <elproEVENT> → Security → Users → New User… to open the window for the creation of a new user.

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproEVENT.

• In the list on the Membership page, select the entries db_datareader and db_datawriter.

• Create User by clicking OK.

5.3.3. Create Database Schema

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Double-click on<Setupdirectory>\Setup Files\SQLScripts\EVENTSchema2015.2.P5.sql to open.

• Click in the window of the open script. Call Query → Specify Values for Templates Parameters…(Ctrl+Shift+M) and enter the name of the previously created database. (e.g. elproEVENT)

• Close the Template Parameters window by clicking OK.

• Click Execute (F5) to execute the script.

5.3.4. Create elproUserDBUser in the elproEVENT Database

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Right-click the <server name> folder → Databases → <elproEVENT> → Security → Users → New User… to open the window for the creation of a new user.

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproUSER.

• On the Securables page, click Search….

• In the following Add Objects window, select the option Specific objects… and click OK.

• In the following Select Objects window, click top right on the button Object Types…, tick the checkbox in Tables in the new Select Object Types window, and close the window by clicking OK.

• Back in the Select Objects window, right-click on Browse…. In the new Browse for Objects window application-specific login name for elproUSER.

  • [dbo].[Applications]

  • [dbo].[FunctionNames]

  • [dbo].[Functions]

  • [dbo].[Languages]

  • [dbo].[Resources]

• Click OK to close the Browse for Objects and the Select Objects windows.

• Under Permissions for dbo….: tick the checkbox for Grant for these 5 tables in the following entries:
  Select
  View Definition

• Create User by clicking OK.

5.4. Setting up elproUSER

5.4.1. Setting up elproUSER

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Right-click Databases → New Database.

• Enter the database name under Database name. (e.g. elproUSER)

• If required, change DB Owner and the memory location for the database file and the database logfile (under Path).

• Create database by clicking OK.

5.4.2. Create New Main User in elproUSER Database

• Start SQL Server Management Studio and log in to the database as a DB Administrator.

• Right-click the <server name> folder → Databases → <elproUSER> → Security → Users → New User… to open the window for the creation of a new user.

• Define the database user on the General page. As login name, use the previously entered, application-specific login name for elproEVENT.

• In the list on the Membership page, select the entries db_datareader and db_datawriter.

• Create User by clicking OK.

5.4.3. Create Database Schema

• Start SQL Server Management Studio and login to the database as DB Administrator.

• Double-click on<Setupdirectory>\Setup Files\SQLScripts\USERSchema2021.3.P4.sql to open.

• Click in the window of the open script. Call Query → Specify Values for Templates Parameters…(Ctrl+Shift+M) and enter the name of the previously created database. (e.g. elproUSER)

• Close the Template Parameters window by clicking OK.

• Click Execute (F5) to execute the script.

6. Installation und Konfiguration

1. The following sections must be executed as Windows Administrator:
   >> 6.1. Setup Windows Event Display for elproEVENT
   >> 6.2. Setting up the elproMONITOR Web Application
   >> 6.3. Setting up the elproUSER Web Application
   >> 6.4 Creating and Configuring Dedicated Windows User

2. If a dedicated Windows user is created to execute the elproUSER and elproEVENT programs (>> 6.4 Creating and Configuring Dedicated Windows User), the steps from >> 6.5 Configurations Using the elproMONITOR Management Tool can be executed via login with this user.

Anchor
6.1.-Setup-Windows-Event-Display-for-elproEVENT 6.1.-Setup-Windows-Event-Display-for-elproEVENT

6.1. Setup Windows Event Display for elproEVENT

• Open Windows Powershell (powershell.exe) (by right-clicking → Run as administrator).

• Enter the following command: New-EventLog -LogName Application -Source "elproEVENT Library"

Anchor
6.2.-Einrichtung-der-elproMONITOR-Web-Applikation 6.2.-Einrichtung-der-elproMONITOR-Web-Applikation

6.2. Setting up the elproMONITOR Web Application

Anchor
6.2.1.-elproMONITOR-Service-einrichten 6.2.1.-elproMONITOR-Service-einrichten

6.2.1. Set up elproMONITOR Service

• As preparation, create the configuration directory.
  e.g. C:\ProgramData\ELPRO\License

• Execute the batch processing file <Programdirectory>\elproMONITOR<Versionnumber>\MonitorService\Install.bat (by right-clicking → Run as administrator).

• Complete the requests for required values in the prompt. Only enter a name without spaces for Service Name.

• Wait until the installation is complete and the prompt displays the following feedbacks:
  CreationService SUCCESS
  ChangeServiceConfig2 SUCCESS

Anchor
6.2.2.-Web-Client-einrichten-(IIS) 6.2.2.-Web-Client-einrichten-(IIS)

6.2.2. Set up Web Client (IIS)

6.2.2.1. Preparation

• Open file <Webapplicationdirectory>\WebClient\Web.config in Text Editor.
  e.g. C:\programdata\ELPRO\websites\elproMONITOR\WebClient\Web.config

• Search for Tag forms. Set the value of the associated Attribute name to the Service Name.

• Additional step if the WebClient is running on a different machine to the Service. (The connection from the web application to the elproMONITOR Service is defined via WcfBaseAddress.)

  • Search for key="WcfBaseAddress". The value of the associated attribute must be adjusted as follows. If the web application and the Service are not being run on the same computer, the IP address must be set to the value of the elproMONITOR Service computer.

• The default port number (8000) can be optionally changed. If the default port number is changed, this also has to be changed in the elproMONITOR table: Setting entry Keyname WcfBaseAddress.
  e.g. <add key="WcfBaseAddress"value="net.tcp://<Adresse>:<Portnumber>"/>
  <forms cookieless="UseCookies" loginUrl="~/Account/Login" name="elpro-MONITOR" />

• Save the changes.

6.2.2.2. Configure IIS

• Start IIS Manager (inetmgr.exe).

• Double-click to expand the <System Servername> of the Connections list.

• Expand Sites by double-clicking.

• Delete the entry Default Web Site.

• Right-click Sites → Add Web Site …

• Enter a name for the website under Site name: and a path to the web application directory under Physical path:
  e,g, Site name: elproMONITOR, Physical path: C:\programdata\ELPRO\websites\elproMONITOR <VersionNumber>\WebClient

• The remaining values may be left with the default values.
  Optional: The settings for Type, IP address, Port and Host name can be changed as required, (for example multi-tenant capability across various ports, connection to DNS, etc.)
  Exit the configuration and create new website by clicking OK.

• Click Application Pools (on left of window).

• Right-click elproMONITOR → Advanced Settings …

• Change property .NET Framework Version to V4.0 and confirm by clicking OK.

• Start command prompt with Command Prompt → Run as administrator.

• Enter
  cd C:\Windows\Microsoft.NET\Framework\v4.0.30319

• Enter
  aspnet_regiis –i

• Wait for prompt feedback
  Finished installing ASP.NET

Anchor
6.3.-Setting-up-the-elproUSER-Web-Application 6.3.-Setting-up-the-elproUSER-Web-Application

6.3. Setting up the elproUSER Web Application

6.3.1. Set up the elproUSER Service

• As preparation, create the configuration directory.
  e.g.C:\ProgramData\ELPRO\License

• Execute the batch processing file <Programdirectory>\elproUSER<Versionnumber>\Install.bat (by right-clicking → Run as administrator).

• Complete the requests for required values in the prompt. Only enter a name without spaces for Service Name.

• Wait until the installation is complete and the prompt displays the following feedbacks:
  CreationService SUCCESS
  ChangeServiceConfig2 SUCCESS

6.3.2. elproUSER Set up API (IIS)

6.3.2.1. Preparation

• Open file <Webapplicationdirectory>\elproUSER API\Web.config in Text Editor.
  e.g. C:\programdata\ELPRO\websites\elproUSER\WebApi\Web.config

• Additional step if the Web API is running on a different machine to the Service. (The connection from the web application to the elproUSER service is defined via WcfBaseAddress.)

  • Search for key="WcfBaseAddress". The value of the associated attribute must be adjusted as follows. If the web application and the Service are not run on the same computer, the IP address must be set to the value of the elproUSER Service computer.

• The default port number (8001) can be optionally changed. If the default port number is changed, this must also be changed in the elproUSER table: Setting entry Keyname WcfBaseAddress.
  e.g. <add key="WcfBaseAddress"value="net.tcp://<Adresse>:<PortNumber>"/>

• Save the changes.

6.3.2.2. Configure IIS

• Start IIS Manager (inetmgr.exe).

• Double-click to expand the <System Servername> of the Connections list.

• Expand Sites by double-clicking.

• Right-click on elproMONITOR → Add Application …

• Under Alias:, enter a name for the API and under Physical path:, enter the path to the web application directory.
  e.g. Alias: user-api, Physical path: C:\programdata\ELPRO\websites\elproUSER\WebApi

• Exit the configuration and create the new alias by clicking OK.

Anchor
6.3.3.-elproUSER-Client-einrichten-(IIS) 6.3.3.-elproUSER-Client-einrichten-(IIS)

elproUSER Set up Client (IIS)

6.3.3.1. Preparation

• Open file <Webapplicationdirectory>\elproUSER Client\config.json in Text Editor.
  e.g. C:\programdata\ELPRO\websites\elproUSER\WebClient\config.json

• Under "suffix", enter the suffix for the elproUSER API using the schema “/User-API”.

• If the standard port 80 is not used, enter the port of the elproMONITOR additionally under “port”.
  e.g. „port“: 80,"suffix":/user-api

• Save the changes.

 6.3.3.2. Configure IIS

• Start IIS Manager (inetmgr.exe).

• Double-click to expand the <System Servername> of the Connections list.

• Expand Sites by double-clicking.

• Right-click on elproMONITOR → Add Application …

• Under Alias:, enter a name for the API and under Physical path:, enter the path to the web application directory.
  e.g. Site name: elproUSER, Physical path: C:\programdata\ELPRO\websites\elproUSER\WebClient

• Exit the configuration and create the new alias by clicking OK.

Anchor
6.4-Dedizierten-Windows-Benutzer-anlegen-und-konfigurieren 6.4-Dedizierten-Windows-Benutzer-anlegen-und-konfigurieren

6.4 Creating and Configuring Dedicated Windows User

• Create a Windows user with default user rights. (e.g. ElproOperator)

• Read-only and write rights must be set for the configuration directory. (e.g. C:\ProgramData\ELPRO)
  >> 11.2 Access Rights to Configuration Directory

Anchor
6.5-Konfigurationen-mit-dem-elproMONITOR-Management-Tool 6.5-Konfigurationen-mit-dem-elproMONITOR-Management-Tool

6.5 Configurations Using the elproMONITOR Management Tool

• The elproMONITOR Management Tool configures database connection settings for ELPRO applications and activates the basic license for elproMONITOR.

Anchor
6.5.1-elproMONITOR-Management-Tool-starten 6.5.1-elproMONITOR-Management-Tool-starten

6.5.1 Start the elproMONITOR Management Tool

• Double-click on the elproMONITOR Management Tool <Setupdirectory>\Program Files\elproMONITOR ManagementTool\elproMonitorManagementTool.exe to start.

• First a browser appears for you to select the configuration directory.
  e.g. C:\ProgramData\ELPRO\License

• Then you access the main dialog.

6.5.2. Configure Database Connection Settings for elproMONITOR

• Under Create XML Setting, click elproMONITOR….

• Enter the service names and database information from the preceding installation steps in the elproMONITOR XML Settings window.

• Click Test Connection to check whether the configuration you entered works.

• Close Window

6.5.3. Configure Database Connection Settings for elproEVENT

• Under Create XML Setting, click elproEVENT….

• Enter the service names and database information from the preceding installation steps in the elproEVENTS XML Settings window.

• Click Test Connection to check whether the configuration you entered works.

• Close window.

Anchor
6.5.4.-Datenbankverbindungseinstellungen-für-elproUSER-konfigurieren 6.5.4.-Datenbankverbindungseinstellungen-für-elproUSER-konfigurieren

6.5.4. Configure Database Connection Settings for elproUSER

• Under Create XML Setting, click elproUSER….

• Enter the service names and database information from the preceding installation steps in the elproEVENTS XML Settings window.

• Click Test Connection to check whether the configuration you entered works.

• Close window.

6.5.5. Load Activation and License file for elproMONITOR

• Start the service elproMONITOR

• Open the Login Page (Website) of elproMONITOR

• Login with initial credentials (username: admin, password: elpro)

  

• You will be prompted to load the Activation file to activate elproMONITOR

• Install the Activation file

  

• You will be forwarded to the License page of elproMONITOR to load a License file

  

• Install the License file

  

Anchor
6.6.-elproEVENT-Programmverknüpfungen-anlegen 6.6.-elproEVENT-Programmverknüpfungen-anlegen

6.6. elproEVENT Create Program Links

• Create a link to the desktop for the application <Programdirectory>\elproEVENT<Versionnumber>\Application Folder\elproEVENT.exe.

• Right-click on this link to open the Properties window.

• In the Shortcut tab, go to the Target: field and add the parameter –tenant <Configurationdirectory>
  e.g. "C:\Program Files\elproEVENT<VersionNumber>\Application Folder elproEVENT.exe" -tenant "C:\ProgramData\ELPRO\License"

7. Multi-Tenant System Setup

elproMONITOR is capable of processing several tenants. This means that optionally, several elproMONITOR systems can be installed and operated in parallel on a computer system.

elproMONITOR systems run fully autonomously and completely separately from systems installed in parallel. Each system may have different program module versions. Programs and databases can each be operated by separate users so that they are protected against attacks.

Execute the following steps to set up several tenants on a computer system. Note that all name issues referring to a tenant (DB name, DB user, Service name, etc.) must be unique to ensure isolation between individual tenants.

• A separate database for the elproMONITOR, elproEVENT, and elproUSER applications must be created for each tenant. Accordingly, separate DB logins and DB users must be created.
  >> 5. Creating Databases

• Configurations must be created in a separate configuration directory for each tenant.
  e.g. C:\ProgramData\ELPRO\Tenant<TenantName>

• The configuration for each tenant must be made separately using the Management Tool.

• If different versions of elproEVENT and elproUSER are to be used, the corresponding libraries must also be imported to the Global Assembly Cache.
  >> 6.1. Importing Libraries in Global Assembly Cache

• Pro Mandant muss je eine Webapplikation in ein eigenes Webapplikationsverzeichnis kopiert werden. Dies gilt auch falls es sich um eine komplett identische Version handelt
  e.g. C:\inetpub\ELPRO\Tenant<TenantName>\elproMONITOR <VersionNumber>\

• Each individual web application must be set up separately. In particular, each application must be mapped to a separate port and assigned to the corresponding configuration directory.
  >> 6.2.2 Set up Web Client (IIS)

• A separate service instance of elproMONITOR must be set up for each tenant. Here each separate Service instance must have a port applied to it (8000 is standard for the first instance). This port is first defined in the elproMONITOR database in the "Setting" table in the Keyname WcfBaseAddress entry. Secondly, the same port must be configured in the file: Web.config of the web application in the WcfBaseAddress entry.
  >> 6.2.1 Set up elproMONITOR Service

• Optionally, a dedicated Windows user, under which the application runs, can be set up with the appropriate access rights for each tenant.
  >> 6.4 Creating and Configuring Dedicated Windows User

• The database connection settings must be configured for each tenant using the elproMONITOR Management Tool.
  >> 6.5.1. Start the elproMONITOR Management Tool bis >> 6.5.3 Configure Database Connection Settings for elproUSER

• The program links must be set up for each tenant accordingly.
  >> 6.6. elproEVENT Create Program Links

8. System Settings

System settings may be made in the following databases. Usually, settings only need to be made once and are therefore not included in the Settings.

8.1. Settings elproMONITOR - To Check

8.1.1. Tabelle "Setting" Section "UserInterface"

Name

Defaults

Description

AutoLogin

False

Checkbox for Autologin function is not visible

CalibrationColor

#fadcc5

Background color for calibration period

CalibrationColorOpacity

100

Opacity of background color for calibration period

CalibrationTimeoutInHours

18

Maximum calibration time

ChartColors

#0000ff,#008000,#ff0000,#00c0c0,#ff00ff,#c0c000,#000080,#00ff02,#800000,#ff8000

Chart color for sensors

CommentTextRequired

True

The user must enter a comment when acknowledging a deviation.

DateFormat

dd.MMM.yyyy

Date Format

DeactivatedColor

#e1e1e1

Background color for sensor alarm deactivated

DeactivatedColorOpacity

100

Opacity of background color for sensor alarm deactivated

DeleteButtonActive

False

Delete function for sensors and digital inputs deactivated

EcologProBaseMaintenanceUri

URL for ECOLOG-PRO Base Maintenance software (must be specified as absolute path http://<IP address>/Maintenance or as relative path /Maintenance)

EcologProBaseVersion

False

ElectronicSignature

True

The user must repeat his password entry for Activate sensors alarm, Deactivate sensor alarm, and Acknowledge deviation

ElectronicSignatureLoginRequired

False

Login Name must be entered along with the password when confirming deviations

ElproUserUri

URL for elproUSER software (must be specified as absolute path http://<IP address>/ elproUSER or as relative path /elproUSER)

FirstDayOfWeek

Sunday

Sunday is defined as the first day of the week (Sunday or Monday, depending on the country setting of the server

InstallationDate

11/15/2016 12:44:44

Date of installation This date is set automatically when the system is first installed

LongTermProcessTimeoutMinutes

20

Timeout for processes that last too long

MaxAnalysisSensors

25

Maximum number of sensors that are displayed in the chart

MaxCalibrationSensors

10

Maximum number of sensors which can be calibrated simultaneously

NumberDecimalSeparator

.

Delimiter character for floating point numbers

PollingInterval

15000

Refresh interval for MONITOR / DEVIATION page in milliseconds

ReloadedColor

#dae6dc

Background color for sensor values reloaded

ReloadedColorOpacity

100

Opacity of background color for sensor alarm reloaded

ReportTimeoutMinutes

20

Timeout (minutes) to generate a report

SessionTimeout

20

Session timeout (minutes)

TenantName

Name which is displayed along with the login name to distinguish an instance

Use24HourTimeFormat

True

The 24-hour time format is used (with False, the 12-hour format is used)

ValueDateTimeSeparator

;

Character between measurement value and date

MinSnrValue

0

Minimum signal to noise ratio value

MaxSnrValue

100

Maximum signal to noise ratio value

BadSnrValue

10

Industrial Standard for bad signal to ratio value

WeakSnrValue

25

Industrial Standard for bad signal to ratio value

8.1.2. Tabelle "Setting" Section "System”

Name

Defaults

Description

AlarmInterfaceRetryCount

3

Maximum number of communication retries to the Alarm Interface

AlarmInterfaceTimeoutMs

2000

Timeout (milliseconds) for communication to Alarm Interface

ConnectionFibonacciDelays

0,1,2,3,5,8,13,24

Delay Numbers for connection (using Fibonacci numbers)

ConnectionWaitTime

3600

Waiting for connection

CriticalDeviceErrorCycleCount

3

Number of cycles for deviation of critical device errors

DbTimeoutSeconds

30

Database time-out (in seconds)

DbTimeoutSensorDelete

60

Delete the database time-out for sensor (in seconds)

DbTimeoutWriteNC

60

Write database time-out for NC values (in seconds)

DO-WatchdogTimeOutInSeconds

60

Timeout for ECOLOG-PRO Watchdog (seconds)

ExportPdfFilenameForAllSensors

%TimestampUTC%;%ScheduleTaskName%

File name when the automatically generated PDF report contains all selected sensors

IntervalLengthDeviationTolerance

10

Tolerated interval length deviation in seconds

Language

en

The language setting is used for Audit Trail entries, deviation messages, and automatic reports

LaunchApplicationTimeout

00:01:00

Waiting time during program start

LoggerConnectRetryCount

3

Maximum number of connection retries to a logger

LoggerConnectTimeoutMs

2000

Timeout (milliseconds) for logger connection

LoggerReadRetryCount

3

Maximum number of retries to read out data from a logger memory

LoggerReadTimeoutMs

5000

Timeout for reading out data from a logger memory

LoggerReconnectDelayMs

5000

Delay time (milliseconds) until next connection retry to a logger

MaxDataSafetyClearanceMonths

24

Maximum number of months for data safety clearance period

MaxEcologNetReloadThreads

30

Maximum number of threads to reload data for ECOLOG-NET Loggers If more than 30 ECOLOG-NET loggers are used, set the value to 999.

MaxEcologProReloadThreads

1

Maximum number of threads to reload data for ECOLOG-PRO modules

MaxLoggerReadThreads

30

Maximum number of threads to read measured values

MktActivationEnergyKjMol

83.14

Activation energy for MKT calculation

MustConfirmAlarms

True

Alarm must be acknowledged

MustConfirmWarnings

True

Warning must be acknowledged

NewStartNcTimeRangeDays

7

Maximum number of days for recalculation of NC values after server downtime

NumberAllowedIntervalLengthDeviations

10

Number of permitted deviations in internal length

NumberOfAcknowledgements

1

"Four-eyes-principle" number of acknowledgements needed for a deviation

PerformaceLogHistoryLengthDays

7

Number of days after which data is deleted from the PerformanceLog table.

RawValueBackupTimeRangeMonths

24

Number of months after which data is deleted from the MeasureRawValueBackup table.

ReloadDelayMs

1000

Delay time (milliseconds) before reload starts

SkippedCycleAlarms

False

TimestampUTCFormat

yyyyMMddHHmmssfff

Time stamp format

UseIpV6

False

The Internet Protocol Version 4 is used by default. IPV6 is not currently supported

WcfBaseAddress

net.pipe://localhost

The address specifies where the Service Listener is located

8.1.2. Tabelle "Setting" Section "Plugin”

Name

Defaults

Description

OrganisationsId

0

Uniqe Id (number) of the tenant organisationId (autogenerated, do not change)

AutomaticIoModuleCreation

False

Adding Io modules automatically after pairing

AutomaticSensorCreation

False

Adding a sensor automatically after pairing

AutomaticSensorCreationGroupName

Auto-generated

Group name for the automatically created sensors

AutomaticSensorCreationIntervalMinutes

10

Interval in minutes for automatically created sensors

RabbitMQPortAMQP

5672

AMQP port

RabbitMQPortMQTT

1883

MQTT port

RabbitMQUsername

guest

Chosen user name for RabbitMQ

RabbitMQPassword

guest

Chosen password for RabbitMQ

SlidingWindowLength

2

• Configure Database Connection Settings for elproUSER

• The program links must be set up for each tenant accordingly.
  >> 6.6. elproEVENT Create Program Links

8. System Settings

System settings may be made in the following databases. Usually, settings only need to be made once and are therefore not included in the Settings.

8.1. Settings elproMONITOR

8.1.1. Table "Setting" Section "UserInterface"

8.1.2. Table "Setting" Section "System”

8.1.2. Table "Setting" Section "Plugin”

8.1.3. Table "Setting" Section "MailKeepAlive”

8.1.4. Table "Setting" Section "MailSendQueue”

8.1.5. Table "Setting" Section "MailServer”

8.1.6. Table "Setting" Section "SmsKeepAlive”

8.1.7. Table "Setting" Section "SmsModem”

8.1.8. Table "Setting" Section "SmsSendQueue”

8.1.9. Table "Setting" Section "SystemAlert”

8.1.10. Table "Setting" Section "Telemetry”

8.2. Settings elproEVENT

 8.2.1. "Setting" Table

8.3. Settings elproUSER

 8.3.1. "AppSettings" Table 

9. Operation

 9.1. Start

• Ensure that the Monitor Service is running and the web application was started in IIS. The applications can be started from the Windows Administrator account.

• To check this, start Internet Explorer and enter the address http://localhost. The elproMONITOR login page appears. Login using the user previously created in elproUSER (for example, admin).

9.1.1. Enter elproUSER URL in elproMONITOR Database

• Start SQL Server Management Studio and log in to the database as DB Administrator.
  e.g. /elproUSER

• In the elproMONITOR database, open the table dbo.Setting for Editing and in ElproUserUri , enter the web client alias from >> 6.3.3 elproUSER Client einrichten (IIS).

• After the changes in the table dbo.Setting, the following actions are necessary:

  • Restart of elproMONITOR Service

  • Restart of IIS

9.1.2. Set RabbitMQ credentials in the elproMONITOR Database

• Start SQL Server Management Studio and log in to the database as DB Administrator.
  e.g. /elproUSER

• In the ElproMONITOR Settings table set the RabbitMQUsername and RabbitMQPassword according to the credentials which was defined in 4.6

• After the changes in the table dbo.Setting, the following actions are necessary:

  • Restart of elproMONITOR Service

  • Restart of IIS

9.2. First Start-up of elproUSER

• Start elproUSER using the link you just created.

• Login to elproUSER for the first time using the following data:

  • Username: admin

  • Password: elpro

• You can then change the password immediately after.

• If you require integration in AD, click Application → Options to open the Application Settings window and open the "Active Directory":

  • Enter the Active Directory server name.

  • Enter the user name and password of an AD user with read-only rights to AD.

  • Click the "..." button and select the required subnode for user and groups. (If in doubt, simply select the root node.)

  • Click OK to save the changed settings.

10. elproMONITOR Management Tool

Configuring the basic settings of elproMONITOR is performed using the elproMONITOR Management Tool.

The elproMONITOR software requires a path to a so-called tenant list. When the management tool is started, specify this path as the start parameter. If you leave out the parameter, a window pops up for you to enter the path.

If other configurations already exist in this path, they are read out and displayed as defaults.

elproMONITOR is capable of handling several tenants, so several instances can be configured using a tenant list.

10.1. Create XML Setting

11. Additional Features

11.1. Creating Windows User

 11.1.3. Windows Server 2019

• Open the Control Panel.

• Go to User Accounts and click Change account type.

• Click Add a user account.

• Enter name, password, and password hint for the new user. Use the tenant's name by preference.
  User name: Customer01
  Password: MonitorCustomer1
  Reenter password: MonitorCustomer1
  Password hint:   <Passwort Hint>

12. FDA CFR 21 Part 11 Compliance

 If elproMONITOR is to be operated in compliance with FDA CFR 21 Part 11 Revision April 1, 2013, certain measures must be fulfilled.

13. EudraLex Volume 4 - Annex 11 Compliance

If elproMONITOR is to be used in compliance with EudraLex Volume 4 - Annex 11 Revision 1, 30 June 2011, certain measures must be fulfilled.