Cisco Jabber vs XWiki Collaboration Suite

• As an on-prem solution is possible to have voice access to the organization co workers and the PSTN, using the own extension number, even when connected from internet (using Expressway - no need to have a vpn or lan connection) from any device.
• Easy to collaborate from any device (mobile and personal computers). Multiplatform.
• Administrators able to customize the application's features as much as they need.
• Easy to integrate with Active Directory and Outlook. Unique user and password.
• Voice calls and messaging completely secure.
• Persistence chat for mobile.

Read full review

• XWiki makes it easy to manage semi-structured information, which is at the heart of every knowledge nexus of organizations. It makes it easy to manage in a single system both structured data (such as memberships, projects), and unstructured data.
• XWiki offers a very rich API for creating enterprise applications quickly that are easy to maintain and evolve collaboratively.
• XWiki templating and skinning system is extremely flexible and powerful.

Read full review

• There is some brand confusion that exists between Cisco communication products. This is more relevant to the support personnel and engineers that would be making decisions to implement the product. Cisco has their Spark/WebEx platform that provides collaboration/communication functionality and more to the end users. Cisco has stated at some conferences that I attended that they are committed to maintaining and developing the Cisco Jabber platform still so that is very promising since the product serves different needs.
• Cisco Jabber is a little complex to implement properly in your environment. The larger the communication cluster the more complicated it can become. There are also some additional features like persistent chat that require extra resources like a standalone database for persistent chat.

Read full review

• While the basic pieces are available for turning XWiki into an advanced semantic system, some features could be made available more prominently to the user for easing the use of faceted and typed links, paving the way for a new era of collaborative knowledge sharing.

Read full review

• Jabber has provided a very functional alternative to our company to Lotus Sametime. We had been using Sametime for years, and as we were moving out of the Lotus/Domino ecosystem, Jabber has provided a replacement with the chat system, but also means to do voice and video calls.
• Although handy, intensive usage of Jabber can be a curse for a company (including ours). Every information stored in Jabber is only available to the two people involved in the conversation. Without a proper knowledge management strategy, this can mean that a lot of valuable information can be shared privately as peer-to-peer conversations, and not available to people who need it.
• Another downside of Jabber is that it can multiply stress for some people, who can be contacted very often, and be interrupted at critical moments. This can introduce additional context switching, and reduce the productivity of some people.

Read full review

• XWiki has a positive impact on the OW2 communication and collaborations strategies. It saves time when developing applications.

Read full review