ESME Blog

One idea that we’ve kicking around is an ESME client that is context-sensitive.  The idea would be that just ESME messages are displayed that reflect the particular contents on the page on which the ESME client is running.

For example, an ESME client is running on an internal blog page that deals with sales problems with a particular customer “Patriot Chairs”. The ideal situation would be that the ESME client shows all messages that are tagged with the words “sales”, “Patriot Chairs”. The idea is those reading the page could get a feeling for the corporate “heart-beat” dealing with these areas.  The blog reader would be able to see other messages relating to the particular customer in question and sales issues in general.  If desired, the blog reader could then interact with those individuals talking about these matters.

To meet these requirements, the ESME client would have to respond to how a particular blog page is tagged. Whether this tag is based on URL-based tags or another mechanism would be implementation-specific and would in all likelihood be based on the details of the integration environment.

This use case would also probably require new REST API functions (for example, “GetFilteredMessages” http://esme.example.com/messages?tag=sales) to be able to search the public timeline for particular tags.  Another option would be to have a client that performs the filtering actions in the JSON transformation.

Now that ESME works in the cloud, I was thinking about ways to take this existing installation and going viral with it so that a variety of cloud-based ESME  installations could be easily created.   The following steps would be necessary:

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.

In a recent blog about Enterprise Twitter,  Mike Giotta of the Burton Group described 10 questions that enterprises will ask regarding the use of microblogging tools. One question was “Integration with Microsoft Communicator and IBM Sametime”. At first, I disregarded the idea and thought “who needs an integration? They are two tools based on two different collaborative metaphors”.  After a round of sauna, I started to think about ways that the two might complement one another.  Based on this “heated” discussion with myself, I set out and tried to create use cases for this integration.

Read it all..

In my last blog, I mentioned my tests with the Stax.net cloud as hosting opportunity for ESME.  Well, after fighting various issues dealing with proxies and request timeouts,  I finally got ESME installed at Stax, then logged in via OpenID and posted my first cloud-based ESME message.

I really think the Stax environment is great once you get the hang of it.

To get ESME working, I used the sample application from Stax and then copied the files from the ESME war file from the Google Code site. I copied all the esme files into the “webapp” directory and then did a “stax deploy” command to load it all up into the Stax system.  I had to make some adjustments to the ant build file for the Stax deployment, because I have a limitation on the size of files that I can send via HTTP ( Therefore, the source code currently available in Stax is missing all the Jar files.)  Besides that problem, everything worked out well.

I also was able to use the cloud-database in the Stax environment rather than the existing Derby implementation. If you wanted to use a remote DB (for example, behind the firewall), you just have to change the details.

I just added the following snippet to the web.xml file:

<resource-ref>
<res-ref-name>esme</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

and the following snippet to the stax-application.xml

<resource name=”esme” auth=”Container” type=”javax.sql.DataSource”>
<param name=”username” value=”esme_2″ />
<param name=”password” value=”xxx” /> [password is hidden for this blog]
<param name=”url” value=”jdbc:stax://esme” />
</resource>

Now, that ESME is installed, it is possible to perform operations-related tasks -all from my browser.

Still open

• There are still exceptions dealing with file-based activities.  For example. the search interface via Compass currently doesn’t work, because it uses file. These have to be changed as well to have a fully functional application.
• It would be cool to be able to clone this application(including database)  for others.
• It would be useful to have the ability to restrict access to particular IP addresses (maybe, this is a function for which Stax could charge?)

I’m been playing with Stax -  “the fastest way for developers to build, manage and scale Java applications on EC2″ as a means to get ESME into the cloud. I’ve already created an example application (not ESME) based on the standard functionality and am now exploring the environment to get ESME up and running. Currently, the main problem is associated with the fact that ESME uses a local Apache Derby database for test purposes. One requirement on Stax is that local files can’t be created, so I have to use a JDBC data-source to a DB hosted in the Amazon cloud or somewhere else. I’ve created a database in the Amazon cloud (via Stax – real easy by the way -) and am now looking at configuring ESME to use this database. Once this step is done, the next step/scenario would be to use a remote database. This is an interesting scenario that I’ve discussed in another blog about architectural patterns which describes the possibility of a ESME server that  is cloud-based but the database is in the DMZ behind the firewall.  This pattern is interesting, because corporations often have problems with cloud-based installations, because the data is usually not under their control. There may be performance problems associated with such a pattern but this is something that might be able to be lessened via hardware and/or network-related measures.

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

Currently, ESME just supports OpenID for authentication purposes (Note: we are currently working on other authentication modes). Many corporations, however, don’t yet have OpenID providers available internally. Although there are a variety of OpenId providers externally,  internal security restrictions may hamper easy access to these sites.

I was looking for an easy alternative on an OpenId provider that could be deployed within the firewall.  I found a list of potential candidates and decided to try out a few.  I wanted a very simple provider that was easy to install but still worked with ESME.

I finally found one that was ideal for these requirements: java-based WSO2 Identity Solution (WSO2 IS). I was able to download the software and install it within 20 minutes. It is exceeding easy to install and worked out of the box without having to make any changes.  I installed the solution on my laptop where my test installation of ESME is running.  I was able to register as a new user, receive a OpenID and use this OpenID within ESME in approx. 10 minutes.   

WS02 is also based on the Apache 2.0 license which makes it easy to use in enterprise settings.

If you are trying to get an installation of ESME up and running rapidly, this solution is perfect for you.

Bill Fernandez created a long analysis (over 72 pages!) of ESME and its UI design. 

From Wikipedia:

Bill Fernandez is a user interface architect who was Apple Computer’s first employee when they incorporated in 1977. He worked on both the Apple I and Apple II personal computers, and in the 1980s was a member of the Apple Macintosh development team.

The analysis is split into various chapters including:

• The Rationale for ESME
• Conceptual Model
• User Interface Preliminaries

There are long descriptions of various UI components in the next generation user interface of ESME.

If you have comments concerning the new UI, please add them to the esme-dev Google Group.

Lately, I’ve been thinking about the typical ROI-related arguments about the use of Web 2.0 technology within the enterprise.  One thing that you always hear is the importance of metrics to justify the use of such new technology. I’ve had some dealing with wiki-based metrics and I wanted to try and start an initial list of metrics that might be useful. The following list is very preliminary

• 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.

We’ve submitted a proposal to join the Apache Software Foundation (ASF) which

… 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. .

 We are seeking admission to the ASF via the Apache Incubator which

… 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 organisations and existing external projects wishing to join Apache enter through the Incubator.

The process to become a “podling” in the Apache Incubator is well described and we are excited to have been provided this opportunity to participate.

The ESME project team is interested in joining the Apache Software Foundation for several reasons:

• To help the project attract contributors and service providers who will feel more comfortable with the licensing coming through a respected, well known and established organization such as Apache.
• To facilitate the growth of a broader community of users. The project currently lacks sufficiently clear direction, leadership, and process; we believe the project will benefit greatly from Incubator mentorship.

Voting on inclusion of ESME in the Incubator will take place in the next few weeks, we’ll keep you informed regarding our progress.

Last week, we received the amazing news that ESME will be participating in the Demo Jam at SAP’s TechEd in Bangalore. This will be the first time that any team has presented at all three Demo Jams.  Abesh Bhattacharjee and Mrinal Wadhwa will be on stage presenting ESME to the crowd. Athavan Raja Durairaj will backstage supporting the two.

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.