Open Realtime.
Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
Open Realtime.
Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
Hey everyone,
Since I took on the role of Openfire project lead, the Openfire developers have been working amazingly hard across almost every part of the server's code, with a view to making a new release we can all be really proud of.
After a huge amount of work, the Openfire team is really excited to announce we've reached a beta state with the 3.10.0 release, available from http://www.igniterealtime.org/downloads/beta.jsp
This release aims to improve security and stability over the current 3.9.3 stable release, provides a set of important new protocol extensions, and modernizes the XMPP core protocol support - in short, this is going to be the release we wanted to make.
While this is a beta release, we're not recommending it for critical production use; however this is running on igniterealtime.org itself and developer sites, and we'd appreciate people trying it out in non-critical production cases.
We're hoping it'll reach full release rapidly, and we'll be welcoming experiences of anyone deploying so we can add that last polish. Having dealt with the last remaining blocking bug, we're expecting this to move to a final stable release within a week or two.
Dave.
The Ignite Realtime community is happy to announce the first beta version of the upcoming Smack version 4.1. Smack is an open source XMPP client library written in Java with multi-runtime support. It can be used with Java SE and Android runtimes. If you haven't done already now is the ideal time to grab Smack 4.1.0-beta1 and try it out. Compared to the alpha versions of 4.1 the API is considered stable and API changes are unlikely to happen.
Release highlights include support for XEP-198 Stream Management (disabled per default), improved multi-threading performance, improved MUC API and support for SCRAM SHA-1.
Everyone is invited to test beta1 in his projects. The community forum awaits your feedback and bug reports. Although the beta version has proven reliable so far, please only use it productive after intensive testing.
An incomplete list of API changes can be found in the Smack 4.1 Readme and Upgrade Guide. Please consult the Readme before using Smack 4.1.
As always, Smack 4.1.0-beta1 is available from Maven Central.
Don't cha wish your openfire console was hawt like me? Don't cha?
Introducing the openfire jmxweb plugin
I have been using java-monitor.com's openfire probe for a while now to mange all my openfire servers for a while now and it pretty much works. The plugin and extra JMX mbeans developed by Guus der Kinderen have been very useful for checking the health on the servers. For various reasons which include the work done by Tom Evans to enable JMX for Openfire (Jetty. Mina, Hazelcast) I decided to monitor my openfire servers directly with an open JMX management console instead. I tried both jconsole and jvisualvm, but found them difficult to use with remote servers. I needed a web based console.
After a bit of investigation, I first found jolokia and then hawt.io and together, they are hot and spicey...If you want to know more about both jolokia and hwatio, follow the links. As far as openfire is concerned, hawt.io with jolokia are a perfect fit. The plugin design sits well with openfire's plugin architecture enabling hawt.io monitor plugins to be developed independently for openfire plugins, components. Anything server-side that can expose mbeans can be monitored and managed by a hawt.io plugin in html and javascript.
I have packaged hawt.io, jolokia and the openfire mbeans from the java-monitor.com probe into a new plugin called jmxweb. It uses the http-bind web service for hawt.io web console and jolokia's REST API. To access openfire's JMX mbeans, enable it with global property "xmp.jmx.enabled". By default, access is secure and only to admin users. Use "xmpp.jmx.secure" to disable.
How to use
To access hawt.io, point your browser at http://your-server:7070/hawt.io
To access jolokia rest api from your javascript applications use URL http://your-server:7070/jolokia. Make sure you provide headers for basic authentication.
The plugin only works with latest openfire server 3.10 because of changes to mina in 3.10. I might do a backward build for openfire 3.9/3.8 if there is any interest.
What next
I plan to release jmxweb on igniterealtime as a new openfire plugin and develop some mbeans for openfire meetings and a hawt.io plugin to manage them later on. It currently lacks the ability to accumulate jmx data on a central server like java-monitor.com over a period of time to analyse and I will look at implementing a push and store feature much later on.
Update
I have attached the jar file for jmxweb plugin that will work with openfire server 3.9.3 and possibly below. Use at your own risk.
Greetings all. Baring any significant community protest, the subversion server for Igniterealtime will be shutdown on 1 January 2015. All of the active and still relevant repositories have been migrated (with commit histories hopefully in-tact) to our Github presence.
The following Ignite subversion repositories were not migrated due to them likely no longer being relevant
- kraken
- transports
- wildfire
Some of the migrated repositories to Github have not seen development in a number of years. We are certainly interested to hear of any community members that may wish to revitalize any of these projects:
When the subversion service is shutdown, a copy of the repos will be maintained offline in case anything comes up in the future necessitating its revival. Github has been an awesome platform to collaborate on for our active projects that migrated a number of months ago. Hopefully this change helps breathe some life into the older Igniterealtime projects!
Ignite Realtime is pleased to announce "Openfire Meeting", a new plugin for Openfire that continues the development of the ofmeet web application which was part of the deprecated Jitsi-videobridge plugin.
PLEASE NOTE - You will need latest Openfire 3.10.0 to use this plugin. Use a nightly build or wait for the imminent official release.
Openfire Meetings is a complete standalone plugin powered by Jitsi Videobridge. It does not depend on any other plugins
The front-end we application is a combination of Candy and Jitsi Meet and enables the following features
- Openfire user authentication directly from web browser for both Candy and Jitsi Meet
- Audio, Video and Telephone (SIP) conferencing directly with Jitsi Meet and from Candy
- Desktop sharing (screen and applications) using the Openfire Meeting Chrome extension
- Fastpath user agent with audio and video using the Candy and Jitsi Meet web applications. It also requires Fastpath plugin to be installed.
- Configuration directly from Openfire admin web pages.
How to use
Jitsi Meet - https://your-server.com:7443/ofmeet
Candy - https://your-server.com:7443/ofmeet/candy.html
Discussion place is in the community plugins, here