Ako nainštalovať OpenMeetings na CentOS 7

Apache OpenMeetings je open source webová konferenčná aplikácia. Je napísaný v jazyku Java a podporuje viacero databázových serverov. Poskytuje mnoho funkcií, ako sú audio a video konferencie, zdieľanie obrazovky, prieskumník súborov, systém moderovania používateľov, súkromné ​​správy a kontakty, integrovaný kalendár pre plány stretnutí a mnoho ďalších. Môžete tiež nahrať konferenčnú reláciu. Poskytuje SOAP/REST API a viacero doplnkov na jednoduchú integráciu s Moodle, Jira, Joomla, Confluence a ďalšími.

Predpoklady

• Inštancia servera Vultr CentOS 7 s najmenej 4 GB RAM.
• Sudo používateľ .
• Názov domény nasmerovaný na server.

V tomto návode budeme používať 192.168.1.1ako verejnú IP adresu a meetings.example.comako názov domény smerujúci k inštancii Vultr. Uistite sa, že ste nahradili všetky výskyty vzorovej adresy IP a názvu domény skutočným.

Aktualizujte svoj základný systém pomocou príručky Ako aktualizovať CentOS 7 . Po aktualizácii systému pokračujte v inštalácii Java.

Nainštalujte Java

OpenMeetings je napísaný v jazyku Java, takže na fungovanie vyžaduje prostredie Java Runtime Environment (JRE). Stiahnite si najnovší dostupný balík Oracle SE JDK 8 RPM, ktorý obsahuje JRE aj JDK.

wget --header 'Cookie: oraclelicense=a' http://download.oracle.com/otn-pub/java/jdk/8u161-b12/2f38c3b165be4555a1fa6e98c45e0808/jdk-8u161-linux-x64.rpm

Nainštalujte stiahnutý balík.

sudo rpm -Uvh jdk-8u161-linux-x64.rpm

Ak sa Java úspešne nainštalovala, budete môcť overiť jej verziu.

java -version

Uvidíte nasledujúci výstup.

[user@vultr ~]$ java -version
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)

Skôr ako budeme môcť pokračovať, budeme musieť nastaviť premenné prostredia JAVA_HOMEa JRE_HOME. Nájdite absolútnu cestu k spustiteľnému súboru JAVA vo vašom systéme.

readlink -f $(which java)

Uvidíte podobný výstup.

[user@vultr ~]$ readlink -f $(which java)
/usr/java/jdk1.8.0_161/jre/bin/java

Teraz nastavte premenné prostredia JAVA_HOMEa JRE_HOMEpodľa cesty k adresáru Java.

echo "export JAVA_HOME=/usr/java/jdk1.8.0_161" >> ~/.bash_profile
echo "export JRE_HOME=/usr/java/jdk1.8.0_161/jre" >> ~/.bash_profile

Spustite bash_profilesúbor.

source ~/.bash_profile

Teraz môžete spustiť echo $JAVA_HOMEpríkaz, aby ste sa uistili, že je nastavená premenná prostredia.

[user@vultr ~]$ echo $JAVA_HOME
/usr/java/jdk1.8.0_161

Inštalácia závislostí

Nainštalujte knižnice ImageMagick a GhostScript.

sudo yum -y install epel-release
sudo yum -y install ImageMagick ghostscript

ImageMagick poskytuje podporu na nahrávanie obrázkov a ich import na tabuľu. GhostScript vám umožňuje nahrávať súbory PDF na tabuľu.

Overte verziu ImageMagick a GhostScript, aby ste sa uistili, že sú úspešne nainštalované.

[user@vultr ~]$ identify -version
Version: ImageMagick 6.7.8-9 2016-06-16 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2012 ImageMagick Studio LLC
Features: OpenMP

[user@vultr ~]$ ghostscript -v
GPL Ghostscript 9.07 (2013-02-14)
Copyright (C) 2012 Artifex Software, Inc.  All rights reserved.

Ďalej budeme musieť do systému nainštalovať buď Apache OpenOffice alebo LibreOffice. Inštalácia jedného z nich umožní OpenMeetings importovať súbory vo formátoch kancelárskych dokumentov, ako sú .doc, .docx, .ppt, .pptxalebo .xlx. V tomto návode nainštalujeme Apache OpenOffice.

Prepnite sa do dočasného adresára a stiahnite si Apache OpenOffice RPM.

cd /tmp
wget https://downloads.sourceforge.net/project/openofficeorg.mirror/4.1.5/binaries/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-rpm_en-US.tar.gz

Rozbaľte archív a nainštalujte všetky balíky RPM.

tar xf Apache_OpenOffice_4.1.5_Linux_x86-64_install-rpm_en-US.tar.gz
cd en-US/RPMS
sudo rpm -Uvh *.rpm
sudo rpm -Uvh desktop-integration/openoffice4.1.5-redhat-menus-*.rpm

Ak chcete skontrolovať, či je OpenOffice správne nainštalovaný a funguje, zadajte openoffice4 -hdo príkazového riadku. Vytlačí svoju verziu a krátku nápovedu.

[user@vultr ~]$ openoffice4 -h
OpenOffice 4.1.5  415m1(Build:9789)

Usage: soffice [options] [documents...]

Options:

-minimized      keep startup bitmap minimized.
...

Nainštalujte si do svojho systému úložisko RPMFusion, pretože poskytuje vopred zostavené balíčky pre FFmpeg a Sound eXchange (SoX).

sudo rpm -Uvh https://download1.rpmfusion.org/free/el/rpmfusion-free-release-7.noarch.rpm

Nainštalujte FFmpeg a SoX.

sudo yum -y install ffmpeg sox

FFmpeg a SoX umožnia záznam stretnutia. Pomôžu tiež pri importovaní mediálnych súborov, ako sú .avi, .flv, .mova .mp4na tabuľu. Overte inštaláciu kontrolou verzií FFmpeg a SoX.

[user@vultr ~]$ sox --version
sox:      SoX v14.4.1

[user@vultr ~]$ ffmpeg -version
ffmpeg version 2.8.13 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11)

Nainštalujte PostgreSQL

OpenMeetings podporuje viacero typov databázových serverov, ako sú MySQL, PostgreSQL, Apache, Derby a Oracle. V tomto návode použijeme PostgreSQL server na hosťovanie databázy OpenMeeting.

PostgreSQL je objektovo-relačný databázový systém známy svojou stabilitou a rýchlosťou. Predvolené yumúložisko obsahuje starú verziu PostgreSQL, preto pridajte do systému úložisko PostgreSQL pre najnovšiu verziu aplikácie.

sudo yum -y install https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/pgdg-centos10-10-1.noarch.rpm

Nainštalujte databázový server PostgreSQL.

sudo yum -y install postgresql10-server postgresql10-contrib postgresql10 

Inicializujte databázu.

sudo /usr/pgsql-10/bin/postgresql-10-setup initdb

Start the PostgreSQL server and enable it to start automatically at boot time.

sudo systemctl start postgresql-10
sudo systemctl enable postgresql-10

Change the password for the default PostgreSQL user.

sudo passwd postgres

Log in as the PostgreSQL user.

sudo su - postgres

Create a new PostgreSQL user for the OpenMeetings user.

createuser openmeetings

You can use any username instead of openmeetings. Switch to the PostgreSQL shell.

psql

Set a password for the newly created user for the OpenMeetings database.

ALTER USER openmeetings WITH ENCRYPTED password 'DBPassword';

Replace DBPassword with a secure password. Create a new database for the OpenMeetings installation.

CREATE DATABASE openmeetings OWNER openmeetings;

Exit from the psql shell.

\q

Switch to the sudo user.

exit

Edit the pg_hba.conf file to enable MD5 based authentication.

sudo nano /var/lib/pgsql/10/data/pg_hba.conf

Find the following lines and change the values in the METHOD column from ident to md5.

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            ident
# IPv6 local connections:
host    all             all             ::1/128                 ident

Once updated, the configuration will look like this.

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5

Save the file and exit from the editor. Restart PostgreSQL so that the changes can take effect.

sudo systemctl restart postgresql-10

Installing OpenMeetings

Since all the required dependencies are installed. Create a new user for OpenMeetings. Using a non-root user for running OpenMeetings is recommended for the security of the server.

 sudo adduser -b /var -s /sbin/nologin openmeetings

The above command will also create the home directory of the openmeetings user in /var/openmeetings.

Check the Apache OpenMeetings download page to obtain the link to the latest available release. Download the OpenMeetings archive.

cd /tmp
wget http://www-us.apache.org/dist/openmeetings/4.0.1/bin/apache-openmeetings-4.0.1.tar.gz

Extract the archive into the /var/openmeetings directory.

sudo tar xf apache-openmeetings-4.0.1.tar.gz -C /var/openmeetings

Provide ownership of the files to the OpenMeetings user we have created earlier.

sudo chown -R openmeetings:openmeetings /var/openmeetings

Before we start the application, we will need to modify the firewall to allow ports 5080 and 1935.

sudo firewall-cmd --zone=public --permanent --add-port=5080/tcp
sudo firewall-cmd --zone=public --permanent --add-port=1935/tcp
sudo firewall-cmd --reload

You can now start the application.

sudo su -s /bin/bash -c 'cd /var/openmeetings/ && sh red5.sh' openmeetings

You can now access http://192.168.1.1:5080/openmeetings in your favorite browser. You will see the welcome screen with instructions to install GhostScript.

Since we have already installed GhostScript, proceed further. On next interface, you will be prompted to provide database server details. Select database type "PostgreSql" and provide your database server details that you configured during PostgreSQL installation.

Click on the "Check" button and you should get the message: "Database check was successful". Provide your administrator account details and a group name in the next interface.

Configure the basic settings of your installation; such as to allow self-registration, email verification, and default language. Also, provide your SMTP server details. If you do not have an SMTP server ready than you can also provide the SMTP details later in the administrator dashboard.

It will ask you for the path to the binaries of different applications. Provide /usr/bin as the path for ImageMagick, FFmpeg, and SoX. If the application is providing errors for the path entered, then you can use which <binary_name> to find the absolute path to the binary. For example, which ffmpeg should give you /usr/bin/ffmpeg as output. Use /opt/openoffice4 as the path to the OpenOffice binaries.

You can skip the configuration on the next interface since we are going to use the default values. Finally, click the "Finish" button to install the application and write the database.

OpenMeetings is now installed on your server. To make it more production friendly, we will setup Systemd to manage the OpenMeetings server. We will also configure Nginx with Let's Encrypt SSL as the secured reverse proxy to serve the application.

Setting up Systemd

Though we can easily start and stop the application using the command above, it is recommended to set up a Systemd service unit to manage the application. This will also ensure that the service is automatically started on boot time and failures.

Stop the OpenMeetings server either by pressing "Ctrl+C" or by killing the shell of the openmeetings user.

sudo pkill -KILL -u openmeetings

Create a new Systemd unit file for OpenMeetings Server.

sudo nano /etc/systemd/system/openmeetings.service

Populate the file.

[Unit]
Description=OpenMeeting Service 
After=network.target

[Service]
Type=simple
User=openmeetings
WorkingDirectory=/var/openmeetings 
ExecStart=/var/openmeetings/red5.sh
Restart=always

[Install]
WantedBy=multi-user.target

Start the OpenMeetings server and enable it to automatically start at boot time.

sudo systemctl start openmeetings
sudo systemctl enable openmeetings

To check the status of the service, you can run the following.

sudo systemctl status openmeetings

You will see a similar output.

[root@vultr openmeetings]# sudo systemctl status openmeetings
● openmeetings.service - OpenMeeting Service
   Loaded: loaded (/etc/systemd/system/openmeetings.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-01-31 15:40:56 UTC; 38s ago
 Main PID: 10522 (java)
   CGroup: /system.slice/openmeetings.service
           └─10522 /bin/java -Dred5.root=/var/openmeetings -Djava.security.debug=failure -Xms256m...

Jan 31 15:41:29 vultr.guest red5.sh[10522]: [INFO] [Loader:/openmeetings] org.red5.server.Serv...ngs
Jan 31 15:41:29 vultr.guest red5.sh[10522]: [INFO] [Loader:/openmeetings] org.red5.server.Serv...ngs
Jan 31 15:41:29 vultr.guest red5.sh[10522]: DEBUG 01-31 15:41:29.431 16603 343 o.a.o.c.r.Scope...se]
Jan 31 15:41:29 vultr.guest red5.sh[10522]: DEBUG 01-31 15:41:29.531 16703 124 o.a.o.c.r.Scope...ngs
Jan 31 15:41:34 vultr.guest red5.sh[10522]: DEBUG 01-31 15:41:34.421 21593 82 o.a.o.u.Version ...] -
Jan 31 15:41:34 vultr.guest red5.sh[10522]: ##################################################...###
Jan 31 15:41:34 vultr.guest red5.sh[10522]: #                              Openmeetings is up ...  #
Jan 31 15:41:34 vultr.guest red5.sh[10522]: #                      4.0.1 3795f14 2017-12-05T16...  #
Jan 31 15:41:34 vultr.guest red5.sh[10522]: #                               and ready to use  ...  #
Jan 31 15:41:34 vultr.guest red5.sh[10522]: ##################################################...###
Hint: Some lines were ellipsized, use -l to show in full.

Setup Nginx as Reverse Proxy

By default, OpenMeetings listens to port 5080. If the connection between the browser and server are not encrypted with SSL, then logins and other information will be sent using plain text. This might be a potential threat as someone eavesdropping on the network might obtain the information. To mitigate this issue, we will setup Nginx as the reverse proxy which will listen to the default HTTPS port and will proxy all the requests to the OpenMeetings server.

Install Nginx.

sudo yum -y install nginx

Start Nginx and enable it to automatically start at boot time.

sudo systemctl start nginx
sudo systemctl enable nginx

Install Certbot, which is the client application for Let's Encrypt CA.

sudo yum -y install certbot

Before you can request the certificates, you will need to allow ports 80 and 443 or standard HTTP and HTTPS services through the firewall.

sudo firewall-cmd --zone=public --add-service=http --permanent
sudo firewall-cmd --zone=public --add-service=https --permanent
sudo firewall-cmd --reload

Note: To obtain certificates from Let's Encrypt CA, the domain for which the certificates are to be generated must be pointed towards the server. If not, make the necessary changes to the DNS records of the domain and wait for the DNS to propagate before making the certificate request again. Certbot checks the domain authority before providing the certificates.

Generate the SSL certificates.

sudo certbot certonly --webroot -w /usr/share/nginx/html -d meetings.example.com

The generated certificates are likely to be stored in /etc/letsencrypt/live/meetings.example.com/. The SSL certificate will be stored as fullchain.pem and private key will be stored as privkey.pem.

Platnosť certifikátov Let's Encrypt vyprší o 90 dní, preto sa odporúča nastaviť automatické obnovovanie certifikátov pomocou úloh Cron.

Otvorte súbor úlohy cron.

sudo crontab -e

Na koniec súboru pridajte nasledujúci riadok.

30 5 * * * /usr/bin/certbot renew --quiet

Vyššie uvedená úloha cron sa spustí každý deň o 5:30. Ak platnosť certifikátu vyprší, automaticky sa obnoví.

Teraz zmeňte predvolený konfiguračný súbor Nginx, aby ste odstránili default_serverriadok.

sudo sed -i 's/default_server//g' /etc/nginx/nginx.conf

Vytvorte nový konfiguračný súbor pre server OpenMeetings.

sudo nano /etc/nginx/conf.d/meetings.example.com.conf

Vyplňte súbor.

server {
    listen 80;
    server_name meetings.example.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443;
    server_name meetings.example.com;

    ssl_certificate           /etc/letsencrypt/live/meetings.example.com/fullchain.pem;
    ssl_certificate_key       /etc/letsencrypt/live/meetings.example.com/privkey.pem;

    ssl on;
    ssl_session_cache  builtin:1000  shared:SSL:10m;
    ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
    ssl_prefer_server_ciphers on;

    access_log  /var/log/nginx/openmeetings.access.log;

location / {
    proxy_pass            http://localhost:5080;        
    proxy_set_header    host $host;
    proxy_http_version  1.1;
    proxy_set_header upgrade $http_upgrade;         
    proxy_set_header connection "upgrade";     
    } 
}

Skontrolujte chyby v novom konfiguračnom súbore.

sudo nginx -t

Ak uvidíte nasledujúci výstup, konfigurácia je bez chýb.

[user@vultr ~]$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Ak ste dostali nejaký druh chyby, nezabudnite dvakrát skontrolovať cestu k certifikátom SSL. Reštartujte webový server Nginx, aby ste implementovali zmenu v konfigurácii.

sudo systemctl restart nginx

Predtým, ako začnete používať aplikáciu na zabezpečenej stránke SSL, budete musieť vykonať zmenu konfigurácie v OpenMeetings. Prihláste sa do svojho administratívneho panela OpenMeetings a prejdite na „ Administration >> Configuration“. V tabuľke ID, kľúč a hodnota; nájsť application.base.url. Zmeňte jeho hodnotu na https://meetings.example.compodľa názvu vašej domény. Uložte konfiguráciu kliknutím na ikonu uloženia vyššie.

Reštartujte službu OpenMeetings.

sudo systemctl restart openmeetings

Teraz môžete prechádzať https://meetings.example.compomocou svojho obľúbeného webového prehliadača a prihlásiť sa, aby ste mohli aplikáciu používať.

Gratulujeme, Apache OpenMeetings je teraz nainštalovaný na vašom serveri. Môžete pozvať svojich priateľov a začať používať OpenMeetings na online konferencie.