From OpenSCADAWiki
Jump to: navigation, search

1 Install OpenSCADA

Installing OpenSCADA in general can be done in two ways. The first and simplest way is to get ready-made packages for the Linux distribution that you are using. The second is to compile OpenSCADA from the source code.

The installation procedure is highly dependent on the Linux distribution you are using and it is not possible to describe that exhaustively in this manual. Therefore, you may need to get a deep knowledge of the mechanisms of installing the software of the selected Linux distribution in its documentation. In the event that the user does not have such knowledge, skills and preferences for a Linux distribution, it is advisable to choose it according to the availability of OpenSCADA packages and even a packages repository, which provides the simplest and most trouble free installation.

If the user has trouble with installing not only OpenSCADA, but also the Linux distribution, then on the first time, he can use the "live" Linux distribution with installed and ready to work and studying the demonstration and full-featured OpenSCADA. If this environment of rapid availability is suited for you then you can stop on it and install it. At this time, "live" builds based on the Debian and ALTLinux (deprecated) distributions are available as hybrid CD/DVD/USB stamps at the page: http://oscada.org/en/main/download/. For more information see the "How to create Live disk" document.

1.1 Installing OpenSCADA from ready-made packages

Installing from the ready-made packages, in turn, can be done in two ways. The first one is simpler, when OpenSCADA packages are already present in their own OpenSCADA package repositories or the official — additional repositories of the used Linux distribution. Installing these packages is a matter of running a typical distribution package management program with the subsequent selection of OpenSCADA packages. In addition to simple installation, the package repository generally allows you to simply keep the operating system updated, safe and up to date! The second method involves obtaining and installing OpenSCADA packages manually.

You can check the availability of OpenSCADA packages in the repositories of Linux distributions or OpenSCADA, as well as download OpenSCADA packages for manual installation, on the download page of the official OpenSCADA site. Here you can also get the configuration for connecting the OpenSCADA package repositories to the package manager of your Linux distribution.

At.png You must download packages and connect package repositories directly to the version of the distribution that you use, otherwise there may be unresolved dependency problems at the installation process.

1.1.1 Adding a package repository and installing OpenSCADA from that

Package repositories are provided by the OpenSCADA project itself, whose service information is usually located along with the packages themselves and is updated automatically at the building, that is, these repositories are most up-to-date and preferable. Although OpenSCADA packages can still be found in the repositories of such Linux distributions: ALTLinux and distributions based on the package base Fedora, but they rather will be old ones since the packages building to the distribution repositories from the developers is not practiced right now!

Repository addresses and configurations for the repository manager can be found on the same OpenSCADA download page (http://oscada.org/en/main/download/) or in the examples below.

When installing from the repository, we select only the package with the configuration of the OpenSCADA project or the model. Everything else will be selected and installed automatically according to the dependencies. The following packages of this kind are usually provided:

  • openscada-model-aglks, openscada-model-boiler — projects of dynamic simulators of technological processes, which together perform the function of demonstrating OpenSCADA;
  • openscada-vis-station — template project of the SCADA station, usually run in a graphical interface and without a Web;
  • openscada-server — template project of the SCADA server, running in the background — the daemon mode;
  • openscada-plc — PLC template project, running in the background — the daemon mode;
  • openscada — typical-complete installation of OpenSCADA.

At.png In the case of the Automation Linux Distributive and LTS packages, the suffix "-lts" is added to the main package name — "openscada-lts", since the repository is one and it contains packages of the both branches: Work and LTS.

Installation-update from the repository is simple but specific to the Linux distribution, window manager or separate program for working with repositories and packages, so we will send the reader to the appropriate documentation for the distribution or program that it uses. Here's a brief look at adding a repository and installing OpenSCADA with standard command line tools:

Package repositories based on the package manager APT (Debian, Ubuntu, ALTLinux) — are added by the location of the downloaded file "openscada.list" to the /etc/apt/sources.list.d folder or by editing the /etc/apt/sources.list file by inserting one line:
Debian (LTS and Work, Automation Linux repository): "deb http://ftp.oscada.org/Debian/12/openscada ./"
Ubuntu (LTS): "deb http://ftp.oscada.org/OpenSCADA/LTS/Ubuntu/22.04 ./"
Ubuntu (Work): "deb http://ftp.oscada.org/OpenSCADA/Work/Ubuntu/22.04 ./"
Installing:

apt-get update
apt-get install openscada-model-aglks

ALTLinux (LTS and Work, Automation Linux repository): "rpm http://ftp.oscada.org/ALTLinux/7 openscada main"
Installing:

apt-get update
apt-get install openscada-Model.AGLKS

Adding the signature verification key (the authenticity) of the repository and packages in it (not necessarily and not in all repositories):

wget -P /etc/apt/trusted.gpg.d http://ftp.oscada.org/Misc/openscada-archive-keyring.asc
# or on old Debian systems
wget -O - http://ftp.oscada.org/Misc/pkgSignKey | sudo apt-key add -

Package repositories based on the package manager YUM (RedHat, Fedora, CentOs) — are added by uploading or creating a file /etc/yum.repos.d/openscada.repo with the contents:

[openscada]
name=OpenSCADA
#CentoOs (LTS)
baseurl=http://ftp.oscada.org/OpenSCADA/LTS/CentOs/7
#CentoOs (Work)
#baseurl=http://ftp.oscada.org/OpenSCADA/Work/CentOs/6
#Fedora (Work)
#baseurl=http://ftp.oscada.org/OpenSCADA/Work/Fedora/12
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=http://ftp.oscada.org/Misc/pkgSignKey

Installing:

yum install openscada-Model.AGLKS

The package repositories SuSE YaST — are added by the command:

zypper ar -f http://ftp.oscada.org/OpenSCADA/LTS/SuSE/15 OpenSCADA

Installing:

zypper in openscada-Model.AGLKS

1.1.2 Manual installation of the OpenSCADA packages

To manually install the OpenSCADA packages you need to download them from the official site or another source. You can usually download two sets of the packages.

The first set is represented by twelve packages:

  • openscada — package with all the files needed to launch OpenSCADA in full volume, including all modules;
  • openscada-server — contains dependencies, script file and configuration the server project to run OpenSCADA in the daemon-service mode;
  • openscada-plc — contains dependencies, script file and configuration the PLC project to run OpenSCADA in the daemon-service mode;
  • openscada-libdb-main — main OpenSCADA libraries for data acquisition and other in the SQLite database;
  • openscada-libdb-vca — visual component libraries in the SQLite database;
  • openscada-model-aglks — DB and configuration of the dynamic real-time model "AGLKS" (Demo: EN,UK,RU);
  • openscada-model-boiler — DB and configuration of the dynamic real-time model "Boiler" (EN,UK,RU);
  • openscada-doc-en — offline documentation of OpenSCADA in English;
  • openscada-doc-uk — offline documentation of OpenSCADA in Ukrainian;
  • openscada-doc-ru — offline documentation of OpenSCADA in mRussian;
  • openscada-dev — development package of creation separate OpenSCADA modules;
  • openscada-dbg — debugging package of debug information to the binary files for report and search for errors in the program.

The second set is represented by about fifty packages with separation of OpenSCADA modules by packages:

  • openscada-core — contains the OpenSCADA core, the basic configuration and the executable files;
  • openscada-db-* — modules of the subsystem "DB";
  • openscada-daq-* — modules of the subsystem "DAQ";
  • openscada-arh-* — modules of the subsystem "Archives-History";
  • openscada-tr-* — modules of the subsystem "Transports";
  • openscada-prot-* — modules of the subsystem "Transport protocols";
  • openscada-ui-* — modules of the subsystem "User interfaces";
  • openscada-spec-* — modules of the subsystem "Specials";
  • openscada — virtual package with dependencies for installing default configuration of OpenSCADA;
  • openscada-server — contains dependencies, script file and configuration the server project to run OpenSCADA in the daemon-service mode;
  • openscada-plc — contains dependencies, script file and configuration the PLC project to run OpenSCADA in the daemon-service mode;
  • openscada-vis-station — virtual package with dependencies for installing typical configuration of OpenSCADA as visual SCADA-station;
  • openscada-libdb-main — main OpenSCADA libraries for data acquisition and other in the SQLite database;
  • openscada-libdb-vca — visual component libraries in the SQLite database;
  • openscada-model-aglks — DB and configuration of the dynamic real-time model "AGLKS" (Demo: EN,UK,RU);
  • openscada-model-boiler — DB and configuration of the dynamic real-time model "Boiler" (EN,UK,RU);
  • openscada-doc-en — offline documentation of OpenSCADA in English;
  • openscada-doc-uk — offline documentation of OpenSCADA in Ukrainian;
  • openscada-doc-ru — offline documentation of OpenSCADA in mRussian;
  • openscada-dev — development package of creation separate OpenSCADA modules;
  • openscada-dbg — debugging package of debug information to the binary files for report and search for errors in the program.

The first set of the packages is more intended for simple-manual installation since it contains only twelve packages. The second set is intended to be located in the Linux repository and then to be installed by the package manager that automatically resolves dependencies, and also allows you to install only the required OpenSCADA components, thereby optimising the work environment.

Manual setup of the first set of DEB packages can be done by command, having previously changed the working directory to the directory with the packages:

dpkg -i openscada-libdb.main_0.9.0-1_all.deb openscada-libdb.vca_0.9.0-1_all.deb openscada-model.aglks_0.9.0-1_all openscada_0.9.0-1_i386.deb

Manual setup of the first set of RPM packages can be done by command, having previously changed the working directory to the directory with the packages:

rpm -i openscada-LibDB.Main-0.9.0-alt1.noarch.rpm openscada-LibDB.VCA-0.9.0-alt1.noarch.rpm openscada-Model.AGLKS-0.9.0-alt1.i586.rpm openscada-0.9.0-alt1.i586.rpm

At.png During the installation process there may be errors related to the unsatisfactory dependencies. When manually installing from packages, they will need to be handled manually just like installing the OpenSCADA packages or through the Linux distribution package manager. Cases of the dependency problems can exist even when installing through the packages manager if the OpenSCADA repository used that does not match the Linux distribution or its version, or the main package repositories of the distribution itself are not connected. In the APT package manager you can use the command to automatically resolve external dependencies that arose when manually installing OpenSCADA:

apt-get install -f

1.2 Installing-building from the source texts

When there is no way to get ready-made OpenSCADA packages for the selected distribution, a variant of the OpenSCADA build from the source texts only remains. This process is described in detail by the document "How to build from the source texts".