You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 41 Next »

Enterprise Social Messaging Experiment (ESME) 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.   

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.

Details regarding scala, lift, Web, etc

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.

Highlights

  • 2008 SAP TechEd Demo Jam Participant: Las Vegas
  • 2008 SAP TechEd Demo Jam Participant: Berlin
  • 2008 SAP TechEd Demo Jam Participant: Bangalore

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

There are three types of ESME client.

  • Those that use the internal ESME JSON interface
    • Web UI
  • Those that use ESME's REST API
  • Those that use the Twitter API to access ESME
    • Twhirl

You are a developer

  • You can check out the ESME source
  • You can contribute patches to the ESME Core
  • You can develop your own clients using ESME's own REST API or our Twitter API.  Here are the instructions to create your client.
  • You can use the ESME mailing lists

You are a potential user

  • You can check out existing ESME installations
  • You can install ESME in your own environment 
Important Links
  • Rest API
  • Actions
  • Support of Twitter API
  • FAQ
  • Groups vs. Pools
  • UI Discussion
  • Integration patterns
Could not retrieve http://blog.esme.us/feed/rss/ - Page not found.
  • No labels