How to install atvise in Linux

This article explains how to install atvise in Linux operating systems.

1.  Go to the website and download the install package you need for your Linux system https://atvise.vesterbusiness.com/descarga-sistema-scada/

2. This example asumes a Linux Ubuntu 18.04 system is being used.

3. Download the file an place it in any folder in your regular Windows PC, the file name looks similar to this  "atvise-3-5-4-ubuntu1804_x64.deb".

4. Using an SFTP Client you will need to login to your Linux Server to see the Folder Structure

5. Browse to the "tmp" folder

6. Drag and drop the installation file to the "tmp" folder

7. Next you will need an SSH client, in this example PUTTY is being used

8.Login to the Linux server with the SSH Client

9. First an update cmd is recommended (not necesary) "sudo apt update"

10. Next execute the install cmd: "sudo dpkg -i /tmp/atvise-3-5-4-ubuntu1804_x64.deb"  (you should type your folder and installation file name).

11. Next we need to get the hardwarecode to request a license "atserver --hardwarecode"

12. This cmd will reply a long code you will need to copy 

13. Copy the code and send it to "soporte@vestersl.com" and we will reply to you with an "atserver.lic" file.

14. Place the license file in any folder in your regular Windows PC.

15. Using your SFTP client browse in your Linux system to the folder "/etc/atvise", drag and drop there the "atserver.lic" file.

16. Once done go back to the SSH client and execute "systemctl start atvise" this will start your atvise service

17. The command systemctl status atvise will return the status.

This finishes the installation process, please see below more commands

1. Important files and directories

==================================

* /etc/atvise

   - atserver.lic: atvise license file

   - atserver.ini: global atvise server configuration file (optional)

   - defaultimport: directory with user defined import files (optional)

* /lib/systemd/system

   - atvise.service: atvise server daemon unit file

* /usr/bin

   - contains symbolic links to the atvise binary shell helper

* /usr/lib/atvise

   - contains the atvise binaries as well as v8 plugins and shared libraries used by the atvise binaries

* /usr/share/atvise

   - contains various support files (PKI, import and translation files, webMI test server, ...)

* /usr/share/doc/atvise

   - contains basic documentation files (Release Notes, SLA, ...)

* /var/lib/atvise

   - is the default project directory (used when atvise server is running as daemon)

* /var/lib/atvise/webmi

   - is the directory that should be used as working directory for the webMI test server (contains default config and wwwroot directories)

Note: atvise builder and other atvise GUI tools are not available on Linux.

2. Licensing

============

1. To verify if the license has been correctly set, issue "sudo -u atvise atserver --checklicense" in a terminal window. If the license is valid, it outputs "1".

3. Start/Restart/Shutdown

=========================

3.1 Console mode

================

To start the atvise server in console mode, type "atserver --proj="path", where path> is the desired project directory.

Type '?' and ENTER at the atvise server command prompt for a list of supported commands.

To stop the atvise server, type 'x' and ENTER at its command prompt.

atvise server can also be stopped by sending it a SIGTERM signal.

3.2 Daemon mode (using systemd)

===============================

After installation the atvise server is installed as daemon and can be controlled by the following script:

* systemctl start atvise:   starts the atvise server

* systemctl stop atvise:    stops the atvise server

* systemctl restart atvise: restarts the atvise server

* systemctl status atvise:  provides the status of the atvise server

4. File handles

===============

The number of file handles a process can open defaults to 1024. The atvise server will not start up if this number is exceeded due to a high number of archive files.

You can overcome this issue in two ways:

- Decrease the number of archive files by configuring proper file limits of your archive groups

- Increase the allowed number of file handles (see e.g. https://unix.stackexchange.com/questions/36841/why-is-number-of-open-files-limited-in-linux)