Downloading and Installing MindConnect Software Agent in Docker¶
Downloading MCSA Linux installer¶
Linux installer has a separate setup file based on the processor for,
- INTEL64 Linux : McsaInstallerLinux.zip
- AARCH64 Linux : McsaInstallerLinuxAarch64.zip
To download MCSA in Docker, follow these steps:
Select the Docker-Container download icon based on the processor during the MindConnect Software Agent asset creation in Asset Manager as shown in the below image,
Extract the downloaded McsaInstallerLinux.zip or McsaInstallerLinuxAarch64.zip file on the target Linux system.
Extract the file directly on a Linux system so that the file permissions will remain for the file mcsa-installer.sh extracted.
Extracting files from installer package¶
Starting from MCSA in Docker V03.06.02.07 b001 and V03.06.20.01 b001, it is possible to extract the files from the Linux installer package to a given output folder only:
Extracting files to an output folder
./mcsa-installer.sh -x yes -o /opt/siemens/mindconnect/mcsa
- mcsa-installer.sh needs to be executed with root permissions.
- mcsa-installer.sh also support -h option to show available options.
Starting the installation¶
Open a Linux terminal window as root and navigate to the folder where the mcsa-installer.sh file had been extracted.
It is mandatory to execute the MCSA installation with root privileges - either directly as root, by getting root rights using su command, or by executing it with sudo command.
If the installer is not being started as root, a message will be shown that it has to be started as root and the script will terminate.
Before installing MCSA Linux installer, check these components are installed on the target system. Following additional components are currently required to install, configure and run MCSA on Linux:
Furthermore, check if the Docker engine is already running.
If one of these components is not installed or the Docker engine is not running, the installer will show a message which components are missing and provides the option to exit the installation:
- To install the required components manually, or
- To continue the installation and to install the missing components later
In the latter case, the MSCA components will be extracted to the installation folder, so that the MCSA installation can be started manually after installing the required components.
Installation of required components
- dialog belongs to ncurses and can be installed by using the Linux package manager (e.g. apt).
- docker should be installed by following the steps described on the Docker installation.
- docker-compose installation is also described in the Docker documentation.
- xz can be installed by installing xz-utils using the Linux package manager (e.g. apt).
Installing MCSA Linux installer¶
To install "MCSA Linux installer", follow these steps:
- Open “Linux terminal” window as root.
- Navigate to the folder where the “mcsa-installer.sh” file had been extracted.
It is mandatory to execute the MCSA installation with root privileges - Either, directly as root, or - By getting root rights using “su” command. - "mcsa-installer.sh" can be started using "sudo" command to execute it with root rights. If the installer is not started as root, a message will be shown to start as root and the script will be terminated.
3.Enter the file path
/opt/siemens/mindsphere/mcsa and click "Enter".
By default, MCSA installer offers the possibility to install MCSA components in following folder: -
/opt/siemens/mindsphere/mcsa This folder will be used, if "enter" is being pressed without entering a file path. - After entering the file path click "enter", then the installer checks if the folder already exists. If the folder is already existing, it will offer the possibility to select another folder or to delete the folder, so that the new MCSA components can be installed there. - It is also possible to exit the installer at this point to manually remove the already existing MCSA installation folder, and to start the installer later again.
4.Extract the "mcsa-installer.sh" file to the selected installation folder for MCSA components.
While installing, the Docker engine should not be running, or docker, docker-compose, or xz should not be installed on the target system, the MCSA installer will end after extracting MCSA components. After the required components are installed, the “mcsa-install.sh” can be called manually to load the MCSA Docker image afterwards.
5.Load the Docker image into the local Docker repository.
- If docker and/or docker-compose had to be installed manually, “mcsa-install.sh” script should be executed manually with root privileges - either directly as root, or by getting root rights using “su” command. "mcsa-install.sh" can be started using "sudo" command to execute it with root rights.
- If the installer is not started as root, a message will be shown to start as root and the script will be terminated.
- It is also necessary to start "mcsa-install.sh" script directly in the MCSA installation folder to make sure that the internally used files will be available during script execution.
- If the MCSA Docker image is already loaded, the installer will offer the option to load it again or to skip this step.
- In case that the MCSA Docker image is required to load again, installer will check for the MCSA Docker containers exist and offer the possibility to automatically delete the existing containers or they will remain, but the Docker image will be untagged.
- After removing the previously loaded image, the MCSA Docker image will be loaded again.
6.Add a first MCSA Docker container.
- After loading the MCSA Docker image, the MCSA configuration (Page 109)will be started automatically to add a first MCSA Docker container.
- If application dialog is not available for the target system, the installer will end after loading the MCSA Docker image. After it has been installed, “mcsa-config.sh” can be called manually to load the MCSA Docker image later.
After MCSA installation is finished, the MCSA configuration dialog exits.
After the installation, a message is displayed that “mcsa-config.sh” can be called later again to create new or maintain existing MCSA Docker containers.