(Linux) How to install OpenMeetings?

OpenMeetings [1] is a software to conduct web conferences. It's developed by the Apache Foundation and this software is free with open source.
We have available dashboard, ability to upload files of presentation,drawing, desktop sharing, and more. 

Each room has its own configuration options, and each may be recorded. OpenMeetings can be integrated with LDAP, Active Directory (authentication), VOIP, SIP, platforms Sakai, Jira, Moodle, ATutor, Joomla, Drupal, Bitrix, Confluence, SugarCRM, Redmine. For each of these platforms is a plug to download and configuration – detailed configuration for the plug get on the [1] -> Plugins. 
OpenMeetings supports databases: Apache Derby, IBM DB2, Oracle, MySQL (recommended), Postgres, MSSQL.


At the beginning, make sure that you have access to the console as root, some points require root privileges, except those that download OpenMeetings code. 
If the first time you install OM – create the same database for OpenMeetings in MySQL (or another database). The database must be encoded in UTF-8. Create and assign a user to the database. OpenMeetings installer can indeed create such a database, but does not encode the database correctly, so the best yourself to create such a database. 
Database configuration can be found in [1] in section Configuration> DB Sample Configurations. 
I suggest you to benefit from my script which automates the installation process OpenMeetings.

openmeetings.sh (grant permissions + x)


in the console, go to the directory where we have stored the script, give it appropriate permissions:​

and then type: ​

./openmeetings.sh – called script 
install – you want to install OpenMeetings 
/opt/openmeetingse – the directory where you downloaded the OM 
mysql – selected by our MySQL 
nocompile – we do not want to compile ffmpeg sources and swftools, it is time consuming, but instead the script will download from my account with DropBox prebuilt packages and install them 

Already at the start of the script we will ask for the data to the database, if it is installed on the same server as the OM is host to confirm by the Enter key [localhost], if the port is not changed we enter, we give the database name, user name and password. 
Then, just waiting for the installation and download the appropriate packages and files. 

When you see the inscription:

This means that our instance of the OM is ready to run. 
It is also worth to remember or copy path, will be useful later. 
go inside the directory / opt / OpenMeetings 
and run red5-debug.sh
Now we wait patiently for it to start. 
Note: you can always run the script by screen or give the file rc.local if you want to run at system startup OM​

while OM starts up, you can turn on your browser and try to go to the website:
While still OM starts, we'll see a message that the OM is still not ready. 
Every few minutes, refresh the page in your browser. 
When we can go to OM – we need to go through several pages of the installer.
The first picture shows the information that should be good environment for OM. 
Click on the button Next..​
On the next screen, enter your: 
– The user name 
– password 
– email 
– Time zone 
– The name of the organization (maybe even invented) 
Click on the button Next.​
On the next screen, select the discretion of options, you should consider whether the installer defaults to add several conference rooms. 
Set the data for email, language, and so on. 
Click on the button Next.
On the next screen we need to spend more time. 
Select the quality of the "SWFTools JPEG Quality". The standard is the 85 If you want higher quality – enter 100. 
In the "FFMPEG Path:" enter /usr/local/bin 
In "JOD Path:" enter /opt/openmeetings/jodconverter 
That is the path to your instance OM /jodconverter 
Click on the button Next.​
On this screen, set the settings related to SIP and VOIP. We do not care. So let's go further. 
This screen is the last one. If all we have well pustawiane – click on Finish / install, basically the first right button.
Now patiently waiting for the installation to complete.​
After the installation process, see the screen from which you can go to our instance of OM "Enter the Application". Just sign in and you can manage the OM. 
If you want to abort the OM preferably in a separate console, navigate to the directory and type of OM​





It stops OM. 

If we ever want to update the OM is just use my script and enter:

where is important upgrade – nakaz aktualizacji
and /opt/openmeetings – ścieżka do aktualnej instancji OMthe rest of the options is irrelevant but required​
[1] – http://openmeetings.apache.org/