ESME Blog

The following diagram gives a big picture of the basic usage scenarios in  ESME. 

The ESME message cloud contains all messages that are created.

Note: This simplistic description is based in the assumption that there is just one ESME server instance. In reality, a federated environment may be present increasing the environment’s complexity as well its architectural possibilities to meet more sophisticated enterprise requirements 

The following users are present:

• Bob: This user creates messages. Bob is following no one and has created no actions to filter messages based on tags
• Sue: This user just receives messages. She is following Bob; therefore she receives all his messages
• CRM System Zeus: This user sends messages into the ESME message cloud based on certain business events. The messages’ contents and tags are set according to the particular business event that originated them.
• John: This user has created an action based on the tag “Acme”. John performs a certain activity (for example, sending him an email) when messages with the tag “Acme” are present in the cloud.  Although John does not know Bob and is not following him, John receives a message from Bob that is tagged with the word “Acme”.  Although John does not the CRM System Zeus and is not following it, John receives a message from this user that is tagged with the word “Acme”.  John also creates messages.
• Bot Timesheet: This user watches the ESME message cloud for messages with the tag “Hours” and receives messages that are tagged in this way. This user receives a message from John, processes the message, converts into a more appropriate format and passes it on to a back-end system – in this case, a xRPM system.

Lately, I’ve been spending some time considering the various possibilities to use ESME in the enterprise setting.  Based on these ruminations, I’ve created a series of possible variants on the uses of ESME in the Internet (cloud-based), in an extranet and in an intranet. I’ve also looked at different configurations for ESME’s database as well as its user managment functionality (”Corporate LDAP”).

The variants are currently only depicted graphically.  A more detailed description (for example,  to determine advantages and disadvantages, the situations in which a particular variant should be used, etc.)  is still missing.

My main intention is initiate a discussion of this topic.

I’ve created a PDF file with the variants here.