en en en en id en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en sk es en en en en en en en en fr en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en it en en en en en en en en en en en es en en en en en en en en en en fr en en es en en en en es en en en en en en en en en en en en en en en en en ru en en en en en en en en en en en en en en en ru en en de en en ml vi en en en en ru en en en en en en en en en en en en en en en en en en en de en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en pt en en en en en en en en en en en en en en
As I stumble through the world of linux, I've decided to log new tricks I learn because I often forget. I decided to share the log because…. eh, why not.
Formatting Numerical Input with Rails
Kubuntu 16.04 GUI Audio Controls not working
Polymorphic Associations The Smart Way: Using Global Ids
Get Firefox to display warning message when exiting multiple tabs
jaehoo on Kubuntu 16.04 GUI Audio Contro…
BennyBeat on How to download a file from so…
fastrapidleech.com on How to download a file from so…
neanderslob on How to download a file from so…
Openmeetings use of country, state and country codes
October 8, 2013October 23, 2013 neanderslobaddNewUser, country code, openmeetings, soap, state, state id, states_id, userLeave a comment
I’ve been developing using openmeetings SOAP API for a little bit (on which I hope to post soon) and I spent a bit of time getting REALLY confused on where the user’s Country field comes from, what “states_id” is for the addNewUser service, what sort of input it expects, and where it’s stored.
States_id, from the SOAP API, defines the country and stores it in the table address.  (I suppose that makes sense.)  You can find it under the column state_id. This is how the user’s “Country” is defined in the user management gui (see below)
But here’s where it gets weird.  You may have figured out that states_id expects a numerical input; however, this is NOT the standard E.164 three-digit country code that all of us can easily Google for.  Instead, the code is an index number corresponding to the country’s alphabetically organized row number in the Openmeetings table: state.  I think this is most likely a mistake, as the database contains all the Country Codes right there next to the id field, for seemingly, no reason at all.
For the time being, it’s pretty simple to get this working with this piece of information.  Simply enter the corresponding id number from the openmeetings table for states_id.  I’ve included the relevant columns below for reference:
Anyway, hope that helps someone.
Oh one last interesting fact!
Openmeetings use of country, state and country codes
October 3, 2013October 12, 2013 neandersloblogo, openmeetings, stylingLeave a comment
A quick one on Openmeetings here.  I’d been trying to figure out how to re-brand the Openmeetings software for my own application and I finally stumbled upon how to do it.
First if you want to change that “Apache Openmeetings” title on top, here’s where you do it:
Then just go down to where it says “currentappname,” and replace it with whatever you please.
Then, if you want to change the logo, get your own logo (should be 40px tall, and however wide you reasonably want to make it).  Then save it as logo.png, replacing the Apache feather with your own logo.  What if it’s too wide or not wide enough you say?  Not a problem, go down to the section (still in config.xml) “appdisplay” and change the x and y coordinates of both the text AND the logo to whatever looks good to give the logo and text as much spacing as they need.
Apparently there are hard-coded appearances of openmeetings that you can also change by overwriting the $APP_NAME placeholder but I haven’t quite figured this out yet.  I’ll save that for another post.
Re-branding the Openmeetings Interface
How to install Open Meetings on Ubuntu 12.04
September 27, 2013January 22, 2015 neanderslobinstall, openmeetings18 Comments
Openmeetings has been dramatically improved over the years, as has its documentation.  However, the documentation is still a little tricky and I found I needed to combine a couple sources to really understand what was going on.  The English in Openmeetings docs tends to be a little off, which I assume is because the software is of German origin.  Anyway, I figured I might be able to help make it more accessible.  (I’ve spent so much time using the work of others in the open source community, I might as well try to give something back for once.)
Primarily, the following is drawn from the these two pdf-documents:
Installation of Apache OpenMeetings 2.x on Ubuntu 12.10 and 12.04 – 32 or 64 bits
Installing OpenMeetings in Squeeze.pdf
The technical stuff (what you’re likely here for):
Note:  The following is what I used to get it working on my computer, running 64bit Ubuntu 12.04.
Flash:  Openmeetings is one great big flash application.  Everything on it is flash, the text, the video the entry boxes… everything.  Needless to say, I wasn’t so psyched about this (being a 64bit linux user) but I was happily surprised to find how stable it is and how much bitching it doesn’t do.  Really, I completely forget it’s flash…until I try to right-click something but eh, it’s not so bad.
Step 1: Install Flash on whatever computer you’ll be accessing open meetings on
I almost feel like this isn’t worth going into, there are a whole bunch of articles on it online depending on your operating system.  I figure if you have a computer and it’s hooked to the internet, you probably already have flash.
Step 2: Install oracle Java
You will need Oracle’s JDK.; substitutes such as OpenJDK won’t cut it.  For Ubuntu users, use the following steps:
Add the repository:   sudo add-apt-repository ppa:webupd8team/java
Update your system with the new repo: sudo apt-get update
Install Oracle Java6: sudo apt-get install oracle-java6-installer
Tech note: The above will install the Java6 installer, which will (as part of its install process) run and install the Java6 JDK after it’s installed.  I don’t really know why it works this way but there you have it.  Also I’ve read that Java7 plays with Openmeetings just fine but haven’t tried it myself.
Once the installer starts going automatically it will inform you that you MUST AGREE TO THE LICENCE (hit enter for ok).  Then it will ask you DO YOU AGREE TO THE LICENSE?  Since they’ve already given you the ultimatum that you have to, I guess you don’t have much choice; arrow over to yes and hit enter…only after reading the ENTIRE agreement at the url they provide of course ;-D (oh that’s too funny).
Step 3: Install Open-Libre-Whatever Office (or make sure it’s already installed)
Openmeetings has a really sweet document upload feature where all participants can examine word documents, ppt presentations etc in real-time.  This uses OpenOffice or LibreOffice to do the conversion (either one will work).  So make sure you have a copy installed on the server.
Step 4: Install more conversion software
You’ll need the following packages to properly convert uploaded files to display during the meeting.
1.  Sudo apt-get yourself the packages: sudo apt-get install imagemagick gdebi libgif4 libjpeg62 synaptic
2.  Download and install swftools using the method below.  This will render files into .swf flash when you’re using Openmeetings.
Install this repository: sudo add-apt-repository ppa:guilhem-fr/swftools
Update your system: sudo apt-get update
Install the package: sudo apt-get install swftools
Step 5:  Install FFMPG
FFMPG is necessary for the video stuff that Openmeetings needs.  The official documentation advises that one should compile FFMPEG…which is a bit of a pain.  Being lazy and a humble student of the sacred way of the half-assed, I just used the latest version from the repositories: sudo apt-get install ffmpeg.  I’ve found this to work well enough, though apparently it can present problems when trying to record Openmeetings video feeds.  Or, to quote the official documentation in its original prose:
Now should Compile FFMPEG for video. To install the one that comes in the repositories, we would find very possibly problems with the recording video. Our compiled ffmpeg will have characteristics that do not find in the normal version.
…hey at least it reads better than the nonsense I’d have written, were I to explain this in German.
But anyway, if you don’t want to find very possibly problems with the recording video, go ahead and compile ffmpeg.  I might add in how to do this later, but the Googler yields some great tutorials on how to make this happen in Ubuntu.  I haven’t needed to record the Openmeetings feed yet on my server and so the repo version has worked just fine for me.
Step 6:  Install MYSQL
It’s quite likely that you have this going already BUT if you dont…
1) sudo apt-get install mysql-server
2) It’ll ask you for a new password for the root user.  Make up a good one and don’t forget it.
Ok, now a little work here.  We need to create a database for Openmeetings to use.  So in your terminal and….
Get into mysql using: mysql -uroot -p
It’ll ask you for your password… enter it.  (As per usual with the terminal and password, no characters will appear)
Then enter: mysql> CREATE DATABASE open2final DEFAULT CHARACTER SET 'utf8';
There, you have now created the database “open2final”  Of course you can enter any name for your database you wish and just adjust the configurations to follow; this is just the name the official documentation suggests.
Now, with mysql still open, create the mysql user that will access the database for openmeetings: mysql> GRANT ALL PRIVILEGES ON open2final.* TO 'openmeetings'@'localhost' IDENTIFIED BY '123456' WITH GRANT OPTION;
Again, the name/password are pulled directly from the official documentation; call it whatever you like and adjust the settings below accordingly.
“open2final” is the database we gave the user access to,
“openmeetings” is the database username
“123456” is the password for the user openmeetings
Go ahead and quit out of your mysql terminal by typing “quit” and hitting enter.
Step 7:  Finally install the software you were after the whole time
So yea, finally we get to install Openmeetings.  Here’s how:
Go to openmeetings.apache.com and download the latest version ending in tar.gz.  (Zip will work too, but I’ll be doing the commands for tar.gz)
$ tar zxf /wherever/you/downloaded/openmeetings/to/apache-openmeetings-2.1.whatever.the.version.you.downloaded.tar.gz
Now rename the Openmeetings directory: mv apache-openmeetings-version/ red52/ (I don’t know why they call it red52 but it works with the install process)
To get rid of the compressed file: $ rm /wherever/you/downloaded/openmeetings/to/apache-openmeetings-2.1.whatever.the.version.you.downloaded.tar.gz
Backup the original configuration file: $ mv /opt/red52/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml /opt/red52/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml-ori
Create a new configuration file from template: $ mv /opt/red52/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml /opt/red52/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
Now we need to edit that configuration file: $ sudo nano /opt/red52/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml
Once in persistence.xml, we’re here to change the database settings.
Look for the line that contains: Url=jdbc:mysql://localhost:3306/openmeetings
Change “openmeetings” in that line to “open2final” …or whatever you ended up calling your database.
Then find the line containing :  Username=root
Change “root” to “openmeetings” or whatever you named your mysql user above.
And add the password to the line:  Password="/> so that it reads  Password=123456"/> or whatever password you gave your msql user.
Step 8:  Connect Openmeetings to MySQL
Wait, I know what you’re thinking “didn’t I just do that?”  Nope, not yet.  We need a little java-script package so that your username and password above can actually log into the database and do their thing.  (That’s as far as I’ll go into it… because that’s possibly a bit further than I understand it.)
Anyway, carry out the following:
Download the connector from here: http://dev.mysql.com/downloads/connector/j/
Copy the zip file into /opt/
$ cp /opt/mysql-connector-java-5.1.23/mysql-connector-java-5.1.23-bin.jar /opt/red52/webapps/openmeetings/WEB-INF/lib
$  rm -R mysql-connector-java-5.1.23/
$ mv red52/ /usr/lib
$ chown -R nobody /usr/lib/red52
Step 9: Install the JOD converter
The JOD converter is the thing that allows Openmeetings to talk with WhateverOffice.
So monkey see monkey do:
Step 10: Get the Red5-OpenMeetings Script
I found this step was especially confusing in the documentation and I really didn’t understand what was going on until I did some hunting around.  Red5 is the Openmeetings install script and can be found here:
But depending on this or that, the script needs to be modified, so I’ve saved you a little hunting/typing see below:
Here’s the directory that the install script (red5) needs to go to: $cd /etc/init.d/
Download from one of the two links:
If you are using OpenOffice: $ wget https://dl.dropboxusercontent.com/u/11993667/OpenofficeRed5/red5
If you are using LibreOffice: $ wget https://dl.dropboxusercontent.com/u/11993667/LibreofficeRed5/red5
Make sure it’s executable: $ chmod +x /etc/init.d/red5
Step 10: Run Openmeetings!
Ok just a few final instructions here:
You will get some sort of message to the following effect: start-stop-daemon: --start needs --exec or --startas  Try 'start-stop-daemon --help' for more information.  Just ignore it, everything should be fine.
Give it a minute, then open your browser and go to: http://localhost:5080/openmeetings/install
You should see the following page:
Click Continue with step 1
Then you’ll get this:
Configure your administrator name
Give your admin a password
enter your email address
Enter your time zone and the rest
Then you should get a page presenting you with a few technical options:
Your JOD path should be /opt/jodconverter-core-3.0-beta-4/lib
Configure any other unique settings (folks who complied FFMPEG from scratch, I might be looking in your direction)
Scroll down and click install.
Grab a snack and come back. (Actually it only took a minute or so on mine)
And you should get an affirming message in your browser.
To Get at Openmeetings
To access openmeetings for general use as an admin, go to http://localhost:5080/openmeetings/
There you should be asked for your username and password and then be free to go.
Anyway, that’s all!  Enjoy!  Openmeetings is a really great program and a lot of smart folks have apparently put a lot of work into it and are continuing to do so.
In the likely event that I screwed something up above, please do let me know.
Notice: I did pluck the pictures above from other documentation I found on the Apache Openmeetings site.  I figured they were used to promote the software and the writer wouldn’t mind me posting them to help users out.  If the owner has an issue with this, for whatever reason, please give me a shout and I’ll take them down and snap my own instead.
How to install Open Meetings on Ubuntu 12.04
My Adventures in OpenMeetings
September 26, 2013October 9, 2013 neanderslobintroduction, openmeetingsLeave a comment
So I’ve been spending a bit of time in the foreign and somewhat obscure world of Openmeetings.  For those of you who don’t know, Openmeetings is a free video conferencing suite that anyone can download and install on their server for free.  It runs entirely on flash (a little odd) but it’s astonishing how well it works.  I’m a bit of a programming hack and I got it running, though it does require a little bit of assembly (the action not the language).
Apparently it’s the project of a fellow in Germany and there’s been a company set up around it to provide tech support around the product (a-la most open-source business models).  Unfortunately, the documentation on this platform is a little vague (though it’s getting better) and there seems to be an existent, though a bit of a limited community surrounding it.  The existing documentation also has a stamp of “English is my second language but I’m doing my best.”  (Hey, it’s much better than if I were to try to write up documentation in German so no judgement here.)   I’ve decided to document some of what I’ve found about openmeetings, as I’ve benefited from so much open documentation in other areas already.  I don’t really fancy myself much of a blogger (if you couldn’t tell by looking at my wordpress site already) but I figure this is worth providing a bit of info on.
I’d highly recommend this software to anyone who (for whatever reason) is looking for a way to host online conferences themselves.   It’s got lots of great features that (in my opinion) are more conducive to working Google Hangouts or Skype.  Read more about more about what it’s got at http://openmeetings.apache.org/
My Adventures in OpenMeetings
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.