Openfire alternatives and similar software solutions
Based on the "XMPP Servers" category.
Alternatively, view Openfire alternatives based on common mentions on social networks and blogs.
8.6 9.2 Openfire VS ejabberdRobust, Ubiquitous and Massively Scalable Messaging Platform (XMPP, MQTT, SIP Server)
6.7 9.9 Openfire VS MongooseIMMongooseIM is Erlang Solutions' robust, scalable and efficient XMPP server, aimed at large installations. Specifically designed for enterprise purposes, it is fault-tolerant and can utilise the resources of multiple clustered machines.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Openfire or a related project?
Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.
Openfire is a XMPP server licensed under the Open Source Apache License.
Only a few users have access for filling bugs in the tracker. New users should:
- Create a Discourse account
- Login to a Discourse account
- Click on the New Topic button
- Choose the Openfire Dev category and provide a detailed description of the bug.
Please search for your issues in the bug tracker before reporting.
- Documentation: http://www.igniterealtime.org/projects/openfire/documentation.jsp
- Community: https://discourse.igniterealtime.org/c/openfire
- Bug Tracker: https://igniterealtime.atlassian.net/browse/OF
- Nightly Builds: http://www.igniterealtime.org/downloads/nightly_openfire.jsp
Ignite Realtime is an Open Source community composed of end-users and developers around the world who are interested in applying innovative, open-standards-based Real Time Collaboration to their businesses and organizations. We're aimed at disrupting proprietary, non-open standards-based systems and invite you to participate in what's already one of the biggest and most active Open Source communities.
The project uses Maven and as such should import straight in to your favourite Java IDE. The directory structure is fairly straightforward. The main code is contained in:
Openfire/xmppserver- a Maven module representing the core code for Openfire itself
Other folders are:
Openfire/build- various files use to create installers for different platforms
Openfire/distribution- a Maven module used to bring all the parts together
Openfire/documentation- the documentation hosted at igniterealtime.org
Openfire/i18n- files used for internationalisation of the admin interface
Openfire/plugins- Maven configuration files to allow the various plugins available to be built
Openfire/starter- a small module that allows Openfire to start in a consistent manner on different platforms
To build the complete project including plugins, run the command
However much of the time it is only necessary to make changes to the core XMPP server itself in which case the command
./mvnw verify -pl distribution -am
will compile the core server and any dependencies, and then assemble it in to something that can be run.
Testing your changes
- Run -> Edit Configurations... -> Add Application
- fill in following values
- Name: Openfire
- Use classpath of module: starter
- Main class: org.jivesoftware.openfire.starter.ServerStarter
- VM options (adapt accordingly):
-DopenfireHome="-absolute path to your project folder-\distribution\target\distribution-base" -Xverify:none -server -Dlog4j.configurationFile="-absolute path to your project folder-\distribution\target\distribution-base\lib\log4j2.xml" -Dopenfire.lib.dir="-absolute path to your project folder-\distribution\target\distribution-base\lib" -Dfile.encoding=UTF-8
- Working directory: -absolute path to your project folder-
You need to execute
mvnw verify before you can launch openfire.
Although your IDE will happily compile the project, unfortunately it's not possible to run Openfire from within the IDE - it must be done at the command line. After building the project using Maven, simply run the shell script or batch file to start Openfire;
-debug as the first parameter to the script will start the server in debug mode, and your IDE should be able
to attach a remote debugger if necessary.
*Note that all licence references and agreements mentioned in the Openfire README section above are relevant to that project's source code only.