Page History

 Enterprise Apache ESME (Enterprise Social Messaging Experiment (ESMEEnvironment) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context.   

{deck:id=Home}

{card:label=Overview}

The ESME server is written in Scala and uses the Lift web framework to produce a browser-based user interface and also to expose a REST API. The ESME architecture has been devised to meet the business requirements associated with reliability and scalability. The use of the Scala programming language and the Lift web framework on the server provides rapid development capability as well as browser push functionality ("Comet") as standard. The open server side architecture allows other messaging environments - internal (Alerts, Enterprise Services, etc.) as well as public (Twitter, external web-services, etc.) - to be consumed as messaging sources. An event-driven actions framework within ESME allows users to filter their information flow as well as to forward ESME messages to other systems via HTTP or email.

{card}

{card:label=History}

If you look at the origins of the ESME project, you will find that the origin was in a plurk (a micro-blogging site like twitter) conversation that at some point moved to the SAP SDN wiki. The project then moved to Assembla and then Google Code
The team involved was originally primarily made of individuals associated with the SAP community but has since expanded to include others from outside that community. The global team includes members from a variety of different nations ranging from India, Spain, Norway, Bulgaria, UK, etc.

{card}

{card:label=Features}

Present Features

• Adobe Air client
• Web client
• Extensive set of built-in actions
• Login via Open-ID

Planned Features

• Federation scenarios
• Groups

A few requested Features

• ERP notifictions
• Prioritization
• Show local time for users

{card}

{card:label=Downloading}

ESME Core

There are three ways to access the source

• Web Access: The code repository can be browsed here
• Anonymous SVN: SVN URL for anonymous users is here Instructions for anonymous access are here .
• Committer SVN: SVN URL for committers is here Instructions for committer access are here

  Wiki Markup
  {card}

  Wiki Markup
  {card:label=Using ESME}

  Existing sites

There are a few sites that already have a working version of ESME

Installing ESME

{card}

{card:label=Getting Started}

Quick start with ESME

1. Check out, what can ESME do for you or your organization.
2. Get you an OpenID (either from an Use existing OpenID provider or your own OpenID provider setup).
3. Go to an existing ESME installation or create your own ESME installation.
4. Log on there using your OpenID identifier.
5. Happy social messaging!

Expand your ESME experience

• Check out the different client applications available and tested for ESME.
• Don't miss the features for actions and tracking.
• Check out the different means to integrate and interface with ESME.

What lies ahead

• What makes ESME different from other social messaging applications?
• Where can I post bugs and feature requests?
• What is your development roadmap?
• How can I contribute to ESME?

{card}

{card:label=Mailing Lists}

esme-dev: This is the list where developers of the ESME project discuss code changes, milestone progress, schedules, etc.

esme-commits: This list is for those who wish to be notified whenever files are committed to the ESME SVN repository.

{card}

{deck}

You can hardly turn a web page these days without seeing a story that describes how people are using social networks, whether it is Twitter, Facebook or some other service to develop and build their personal communities. In business, we increasingly see blogs and wikis demonstrating utility in problem solving and communications but the real time nature of business process problem solving largely remains untouched by social networking tools. Existing services, while attractive do not scale well and have proven unreliable. This is unacceptable to business which must be 'Always On' and able to support people in their daily working lives. Such applications must therefore be scalable and reliable but also provide a lot more.
When solving problems, how good might it be if a user was able to tap into the collective knowledge of her peers or surrounding groups of people with whom she might naturally network in the workplace setting? How much quicker and with greater precision might she be able to solve daily problems? What if there was a communications mechanism that takes the best of what services like Twitter offers and co-mingled that with readily recognizable business processes? That solution is Apache ESME.

The Apache ESME blog has more details about ESME as well as project news.