ESME Blog

enterprise microsharing in a process context
January 24, 2010

Integration with Thingamy

Author: anne - Categories: Uncategorized

We have over the last weeks been working closely with Thingamy on integrating ESME with their work processor. The result can be seen in the video below.

A few words from Sig Rinde from Thingamy:
Thingamy’s ‘Work Processor’ runs the workflow without glitch with path choices at most corners – punting a little ‘train’ of relevant and inter-realted objects (Workflow/issue/request/idea object – the main one + Assignment objects) through a workflow. The Assignment objects holds the task instructions and captures what’s done in the assignment while the Workflow objects holds the details about the issue/idea/request. That way an Assignee is presented with a list of relevant objects, all the pertinent information required for a specific task + the Assignment object to fill in with result and files.

When having been assigned a task, or when trying to get one’s head around the progress of a workflow there is always a need for ad-hoc communication with co-workers and/or other participants, “anybody
know…?”, “Could somebody help with…?” etc. Normally that would happen by email, phone or walking over – all of which limits the discovery of the unknown, like a co-worker having unknown but useful knowledge or ideas.

ESME adds that crucial part of ‘Discovery & Discussion’ that inevitably happens during any process, in a task or when studying the progress. In addition it should become the natural in-system conduit
for communication as well as the social pivot point, the water cooler, for the group/department/firm.

Most other E 2.0 efforts tries to add some notion of ‘process’ on top of separate and siloed apps drifting towards becoming middleware 2.0 – better is to have an underlying ‘process engine’ that gives the main
flow framework and datamodel using social media for the in-task ‘Discovery & Discussion’. Crucial is that the data in the two parts are related – in this case any ESME message can be related to any
Thingamy object adding context to both sides.

I don’t know what next step, as in features, will be – our philosophy is to keep it as simple as possible in the beginning and only add if it makes huge sense and works in practice. So we’ll see, the good thing is that both ESME and Thingamy are extremely nimble and doing crazy stunts underway should be easy!

 

January 2, 2010

Integration with Apache OFBiz

Author: dick - Categories: Integration, Vision - Tags: ,

Introduction

I have just finished integrating ESME into Apache OFBiz which is an open-source ERP platform.

The Apache Open For Business Project is an open source enterprise automation software project licensed under the Apache License Version 2.0. By open source enterprise automation we mean: Open Source ERP, Open Source CRM, Open Source E-Business / E-Commerce, Open Source SCM, Open Source MRP, Open Source CMMS/EAM, and so on.

I used OFBiz’s event environment to plug-in ESME functionality.

ECAs are pretty straight forward: when an Event occurs, if the Condition(s) are met then Action(s) are performed. The Events supported currently are Entity (EECA) events which basically correspond to database record CRUD events, Service (SECA) events which correspond the various stages of a given service’s invocation (invoke, validate, commit, return, etc.) and Mail (MECA) events which occur when an email is received.

I used the entity “Facility” as a prototype but any entity would be possible. I also selected that the events would just be sent when new facilities were created but I could have just as easily responded to other entity-related events (deletes, updates, etc.)

My goal was to easily integrate the two environments as quickly as possible. Once I figured out what to do, the integration was relatively easy. I used a local ESME instance that was separate from the OFBiz instance.

Screenshots

ofbiz1

Here I create a new facility https://localhost:8443/facility/control/CreateFacility.

Here is the screenshot from ESME that shows the message that was sent in response to the creation of a new facility.

ofbiz2

Technical details

Authorization

The use of the ESME REST API requires a token. I’ve manually stored this token in the externalAuthId value of the UserLogin entity. https://localhost:8443/webtools/control/ViewGeneric?entityName=UserLogin&userLoginId=system

I added a token to the system user to be used in the ESME REST API calls.

ofbiz3

Message Contents

I’ve selected just three attributes of the Facility entity to be displayed in the ESME message. I looked at the details of the entity and just selected those that were easiest to use. Other attributes could also be used as well. https://localhost:8443/webtools/control/ViewGeneric?entityName=Facility&enableEdit=true

ofbiz4

Implementation Details

For details on the implementation, see the Apache ESME wiki page here

Improvements

1. Use of externalAuthId to store the ESME token. The use of SSO would probably be better

2. Use of system as service user. For some reason, the user who fired the event was always “system” rather than the actual user who created the facility.

3. No OFBiz UI. Right now there is no UI in OFBiz to display the ESME messages.

4. Ideally, there should be a common service that sends the message to ESME and entity-specific services that compose the message to be sent.

5. Use of the new Streaming API to send to a specific pool rather than the public pool. Right now, I’m using the Twitter API to send the message. Ideally, the new API should be used to send to a specific pool.

December 15, 2009

12sprints integration

Author: dick - Categories: Design, Integration, Vision - Tags: ,

12sprints is a new collaboration tool from SAP that was in stealth mode for a while and now has surfaced with a bang.

12sprints is part of a new product category called collaborative decision-making.  Collaborative decision-making provides tools that bring people together with the latest information and analysis or decision techniques to drive towards a particular outcome.  Unlike products in the market that offer general collaboration platforms like Microsoft SharePoint, Google Wave, or Salesforce Chatter, 12sprints is a specialized application for goal-oriented work that can be used in conjunction with any of these products. [SOURCE]

 12sprints has a REST API that is still in development and which was introduced on SDN recently.

We decided to work on two simple use cases to test out the REST API from 12 sprints.  By using ESME’s action framework  - in particular using the HTTP Post action-  we enabled ESME users to interact with 12sprints via particular message tags.  The responses from the 12sprints REST API are then posted to ESME so that users can take the information and use it for later processing.

Note: The authentication for the 12sprints REST API is currently based on basic authentication. The syntax of the authentication is [username]:[password] that is uuencoded

Note: I would love to show screenshots from 12sprints with the created objects but, since 12sprints is still in beta, publication of screenshots isn’t permitted.

Use case 1:  Creating an activity

The first use case was the creation of a 12sprints activity from ESME.  The action takes the message string and creates a 12sprints activity with the activity title being the message text. The resulting activity id is returned to the user as a message.

The syntax of the action is:

https://[username]%40[password]@beta.12sprints.com/v1/activities
header:Content-Type=text%2fxml
<activity name=”%s”></activity>

12sprints1

 

Use case 2: Creating a decision

The second use case was the creation of a decision in a particular activity and the idea is the tag of the message is the activity ID which is necessary to create data objects. The message contents are then used as the contents of the decision.  The action is fired based on messages that contain the word “choice”.

The syntax of the action is:

https://[username]%40[password]@beta.12sprints.com/v1/activities/%25t/items
header:Content-Type=text%2fxml
<item name=”Decision item from ESME”><method_item><method_type name=”Decision”/><decision_item><goal><description>%s</description></goal></decision_item></method_item></item>

12sprints2

 

Current restrictions

This functionality is currently not part of our committed code base. I used a patch from Ethan Jewett to add the action-related functionality to repost the response of the HTTP Post action.  It isn’t committed, because we are still working on the optimal functionality that doesn’t compromise our existing concepts.

If you want to play with this integration, it is currently live on our Performance Instance in the cloud

Plans

These two uses were just first steps in our planned deeper integration with 12sprints. We decided to use to actions, because they are relatively easy to implement and are easy enough for most end-users to use. For more complicated use cases,  we are looking at ESME bots as the more appropriate programming model.  For example, we have one idea of taking an ESME conversation and creating a 12sprints activity with all the individuals and messages  being transferred to the activity.  Other ideas involve sending status messages from 12sprints (activity changes, etc.)  back to ESME so that users can follow activities without having to login on to 12sprints. Another crazy idea is to use “+1″ and “-1″ in ESME to express positive or negative reactions to particular activities.

 

December 14, 2009

Collaboration with akibot

Author: dick - Categories: Design, Integration, Vision - Tags:

We are now starting a collaboration with akibot.

Akibot is the first semantic actionable micro-blogging platform for the enterprise. Akibot not only allows real-time group collaboration and awareness through short, instant messages (like a Twitter for the company), but it also understands those messages and, if applicable, takes action.

What intrigued me about akibot was the semantic analysis of microblogging messages.

The basic idea is that akibot functionality can complement existing ESME functionality. The ESME community isn’t able to do everything on its own. Therefore, we look for partners who will work with us to further establish microblogging in the enterprise.

I’ve started a wiki page to describe the collaboration. The detail description of the use case that we are currently exploring is also present in the wiki.

As the diagram below illustrates, the use case focuses on the use of akibot’s Contextual Analyzer (C>A) module to semantically analyze messages and provide functionality that is currently not present in ESME’s action framework. The akibot Directive Processor (DP) then decides if additional processing is necessary and what additional actions are required.

akibot collaboration

Initial tests between ESME and akibot have proven successful and we are now further exploring collaborative options.

November 30, 2009

Ripples from Salesforce’s Chatter

Author: dick - Categories: Background, Design, Vision - Tags:

There were three events in the last few weeks that led to an massive increase in attention about ESME (leading to a record number of page views on our wiki!)

1. On November 19, Salesforce introduced Chatter which

lets employees set up profiles to connect with coworkers, issue status updates to say what they’re up to, and subscribe to feeds from people–and from applications. Also for collaboration, it lets people join groups to share updates and content. And the service integrates with today’s two hot social-networking services, Twitter and Facebook. [Source]

There are similarities between the functionality offered by Chatter and that offered by ESME which caused many individuals to take another look at ESME and its relevance.

2. In his keynote at the SAP UK & Ireland User Group Conference 2009,  analyst Ray Wang compared ESME and Chatter.

3. ZDNet Blogger Dennis Howlett wrote a blog entitled “Fawning over Chatter and how SAP missed its chance”

All three events fit in well with the increased activity in ESME that has occurred in the last few months.  As new contributors join and old contributors become active again, there is definitely a feeling of progress that has energized the extended ESME community.

I’m sure the next few months will be even more exciting.

November 19, 2009

Return of the performance test

Author: dick - Categories: Design, Development, Uncategorized - Tags: ,

In the past, we’ve blogged about our performance tests but in the chaos of our various development cycles we never really institutionalized such tests.

We are now reaching the point as we push towards our first release that we need to assure that performance considerations are met. One move in this direction was our use of Hudson as a base for building ESME on a daily basis. Now, we’ve started examining our performance in detail by planning a series of performance tests to examine ESME in various configurations (cloud-based, on-premise, etc.). The goal is to establish a performance testing component as part of our continuous integration efforts. There is now a Apache wiki page where the various performance test configurations and the performance test results will be listed.

We already started with this increased focus on performance tests with an initial test conducted by Markus Kohler on 2009-11-19. Here is a screenshot from this test.

memory_allUsers

The results of this test are described in full detail here.

For us, the most important thing is to establish a structure and format for such tests that makes it easy for us and ESME users to be able to compare results in a logical fashion. It is only so that users can decide what sort of infrastructure is necessary for their respective ESME installations.

Collaborative efforts with #ubimic

Author: dick - Categories: Marketing, Vision - Tags: ,

We are currently collecting ideas about how to best collaborate with #ubimic.

#ubimic is a group of university researchers interested in microblogging from different points of view (computer science, information systems, organizational science). Together we think that microblogging has great potential when it comes to integrating normal users and things like sensors, machines and software. We are experimenting with different microblogging tools and scenarios.

There are interesting collaboration possibilitites and we’ve already started describing potential uses cases where we might be able to collaborate. Examples of these use cases are:

  • Use Messages for Back-end Requests
  • Microblogging SAP System
  • Task management
  • Device-related Use Case (RFID)

The big picture of the collaboration efforts might look like this:

ubimic

Take a look at our wiki page for more details about our collabortive efforts.

November 15, 2009

Our new UI is coming

Author: dick - Categories: Design, Development - Tags:

We’ve waited far too long.

After our move to Apache, we were always saying that our Web UI was too primitive and a new one was top priority. Well, the design for the new web UI is finished. The web designer Joy Reyes has been working on the new UI design.

page 1
inside
tabs

The next step is to take this design and bring it to life with our existing code base.

Add formating to your messages: Textile

Author: dick - Categories: Development - Tags:

It is now possible to add formatting to your ESME messages. Through the use of the Textile formatting language, you can create messages with bold, italic, etc.

Textile

For example, the messages in the top message were created with the following lines:

_emphasis_
*strong*
__italic__ **bold** ??citation??
-deleted text-
+inserted text+
^superscript^
~subscript~
%span%
@code@

We haven’t gotten all the Textile possibilitites  to work but we are trying to get as many as possible to be available for users.

Have fun.

November 13, 2009

Internationalization efforts begin: ESME in Chinese

Author: dick - Categories: Development - Tags: ,

We’ve been cleaning up our code base to enable more international versions of the application. We also have some new contributors who are helping with the translation work.  Xuefeng Wu is a new contributor from China who is helping us with various aspects of the project. With his help, we are working on bringing out a Chinese language version of ESME.

esme chinese

Don’t be shocked by the UI. This picture was taken with the old UI (Our new UI is currently being designed! More soon).

One of the advantages  of having an international team is being able to crowd-source the translation work. Expect ESME in different languages once we get our new UI up and running.