#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:

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

Now you may be thinking the main focus should be on measuring ESME performance. True. However, the ESME version that we used is based on a older Scala library with a known memory bug. Thus, the test results are not really representative of the current ESME code base.

If you look at other microblogging platforms (including Twitter) – irregardless of whether they are focused on the enterprise or not, you’ll be hard pressed to find any load test results that are published and available to potential users. However, such tests are usually mandatory for IT projects, especially for larger companies with many potential users.  Thus, we would like start publishing our results so that those interested in ESME can make better sizing decisions.

We will soon be starting a new round of load tests based on the Apache code base and a new Scala library, so expect a blog in the future with these results.

For those interested in performing the tests themselves, Daniel has also made the test scripts available

1. Download existing ESME source code from Stax
2. Create new application in Stax via the application console
3. Download the new application into the local installation
4. Create new database in Stax via the application console for the new ESME application
5. Copy the existing ESME source into the deployment directories of the new application
6. Change the source code to meet the basic style configurations of the new ESME installation
7. Change data-source configuration of the new application to point to new database
8. Upload the new application

 One shortcoming with this description is that as owner of the original ESME application, only I have the ability to create copies of the current installation.  At the current time,  just individuals who I invite to join my Stax application team have access to the ESME source deployment. Ideal would be the ability to create public clones of Stax-based deployments.  Then, other Stax users could very easily create new cloud-based ESMEs.  Although ESME is open-source and the source is available to all via the Apache repository, it would be easier if this was possible via Stax itself.

As a ESME supplier (someone who creates, maintains and/or supports cloud-based ESME installations for others), these steps could be patched together to create a process to very rapidly create micro-blogging sites for customers. The only task that requires more effort would be the customer-specific adaptions regarding styles, etc.

As I read this article, I realized that many of the use cases that micro-blogging tools are meant to solve are actually problems that have been around a long time – for example, the need for employees in distributed companies to be able to collaborate and discover individuals (those old “weak ties”) who can solve their problems. The high level of employee involvement at DEC regarding VAXNotes (irregardless of job title, location, etc.) shows that the assumption that active enterprise collaboration is just restricted to the generation who have grown up with Web 2.0 technology is wrong. VAXNotes emerged in an environment that was pre-Web 2.0 – indeed it was pre-Web 1.0.  Thus, the assumption that it is just Generation Y employees who will be the primary users of such micro-blogging tools is misleading. If the corporate culture (as evidenced by the DEC article) supports such tools, users from all generations will use them.  

Thus, microblogging tool vendors should examine in more detail knowledge management research and the associated case studies to get a better feeling for these requirements. Although we always assume that such vendors are on the cutting edge of the technology, the problems that they hope to solve have been around for a long time.   Obviously if the problems addressed by these tools have been around a long time, then there are obviously tools / technology that meet the associated needs. True. True. The question is what do the new generation of microblogging tools bring to the table – 1) ease of use, 2) the ability for users to decide for themselves what information they wish to see and 3) integration in a variety of environments within and beyond the corporate firewall.  However, microblogging tool vendors must realize that the technology itself  and the metaphor that it represents can be easily copied (as seen in the plethora of Twitter-clones and microblogging platforms). It is the social network and the information that this network provides that is the key.  Thus,  providing a microblogging tool itself won’t be enough to guarantee success – the services that surround its ramp-up and dispersion in an enterprise will be critical as well.

Once we get the ESME server up and running, I’ll post another blog with our experiences.

ESME is a microblogging tool and community project which originated in conversations amongst members of the SAP Community, moved to Google Code, and was the first submission in the history of SAP TechEds which was present at all three Demo Jams (Las Vegas, Berlin and Bangalore) in one year.

The Apache Incubator is the entry path into The Apache Software Foundation (ASF) for projects and codebases wishing to become part of the Foundation’s efforts. All code donations from external organizations and existing external projects wishing to join Apache enter through the Incubator. The Apache Software Foundation (ASF) provides organizational, legal, and financial support for a broad range of open source software projects. The Foundation provides an established framework for intellectual property and financial contributions that simultaneously limits contributors potential legal exposure.

Apache projects are considered the top open-source projects and many of have become standards in software development (Tomcat, Struts, etc.)

Why the inclusion of ESME in the Apache Incubator is ImportantAs I described in my last blog about innovation and the SCN community, I’d like to suggest that the evolution of ESME proves that the potential of the SCN community lies in looking beyond borders of the community itself and must include the experience gained from other communities in order to evolve itself. Although I am very much an Apache novice, I’ve been fascinated by the processes and policies that are present in this organization. For example, there is much that we (SCN) can learn from how Apache deals with IP-related issues. This cross-pollination is especially relevant based on the various open-source-related discussions occurring in background in the SCN.

 As SAP’s participation (including Senior Vice President of the SAP Community Network Mark Yolton) in the Open Source Meets Business (OSMB) Congress demonstrates, there is an increasing awareness that the relationship of corporations to open-source software should be more than just as consumers but also as contributors. This changing role requires a great deal of re-thinking in terms of corporate policies (legal, organizational, etc.); thus, the experience of the ESME team (many of whom are SAP mentors) in Apache will flow back into our involvement with the SCN as well as assist our respective corporations to deal with this new opportunity.

Note: This blog was also posted on the SDN.

• Messages / time period (hour, day, week, etc.)
• Number of links sent (internal vs. external)
• Which are clients are being used
• Number of users time period (hour, day, week, etc.)
• Number of users with 10, 50, 100, 200+ followers
• Number of users following 10, 50, 100, 200+ other users
• Percentage of following/followed ratio (For example, “Are there just a few opinion leaders who have many followers and the majority of users just have a few followers)
• Number of messages that have “retweeted”

Of course, these metrics just refer to information that is inherent in the micro-blogging platform itself.   Finding the ability to associate micro-blogging with more general corporate goals (for example, innovation) is obviously more difficult and requires more thought.

It is important to consider that such metrics are only available when enterprises have complete access to the data that lies at the heart of their micro-blogging platform. If their system is located in the cloud, then such access may be difficult. What is necessary is access to the database that acts as the archive for messages.   Once this access has been achieved, then the creation of tools should be relatively straight-forward. The fact that ESME runs behind your firewall in a database of your choice makes it easy to create such metrics.

I think that providing an application that provides such ESME-specific metrics is a perfect opportunity for a someone.

Each time ESME has been presented at one of this year’s Demo Jam, “local” team members have presented / supported. This is definitely one of the advantages of having a global team.  

Good luck next week to the ESME team at the Demo Jam.

P.S. We will posting the link to the live Internet video stream once it is available.

There is a now a message-receiving client for ESME that is written entirely in Javascript. This very first cut of a client was created as a proof-of-concept to show that a very simple client was possible without any dependence on the server-side programming language.  Based on the current implementation, it could be embedded in Java, C#, etc. It could run in a variety of environments including SharePoint, SAP Portal, etc.

This first version offers:

• Long-polling
• Flexible design
• The client uses XSL transformation to create HTML from the XML that originates from the ESME’s REST-API

The drawbacks of this first version:

• The UI is real ugly. Someone needs to redo the XSL file.
• The UI is not complete. I have not added all the features that are possible (reply, etc.). I was more intent on showing ESME messages in a Javascript-based environment.
• It is not bug-free
• I have only tested it in Internet Explorer 6.0. Someone might have to go and try it out in FF.
• XSL file is currently local instead of stored on server
• The token is currently hard-coded. 
• Documentation is still pretty poor.

Thanks to Darren for doing the initial corrections that started me out on the right foot.

The code is in the Google Code wiki. ]]> http://blog.esme.us/pure-javascript-messaging-client/feed/ 0