Page History

General Use case

(Taken from comments from original page)

1.  a new user visits the ecommerce site
2. this new user enters a microblog message with a question to the administrator of the site.
3. One of the system administrators answers the microblog question as quick as possible
4. further conversation follows.

Technical Prerequisites

• You would need an ESME instance (either on a separate server or in the same container). 
• You would need at least two users (administrator, newuser) "newuser" would notbe associated with a particular user but would be more of an anonymous user.  If you had multiple unauthenticated users using the same  e-commerce site, then they would also see / join the same conversation. Depending on the question, they might be able to help the new user as well.

Technical Description

The basic idea is that an OFBiz UI will be created to capsule the ESME functionality

Architecture

ESME as separate component

ESME as OFBiz component

Making ESME an OFBiz component

Advantges

• let it use the OFBiz authentiation 3. and make a ofbiz userinterface.
• allows ESME to use essential system functions like system messages and ease of installation

Prototype

1. Deploy ESME in your existing tomcat
2. Create two users in ESME: newuser and administrator. 
3. Create a very rough OfBiz UI component to read and post ESME messages. This is the UI for new users. Use the token for the new users in this UI
4. The administrator could use the same OfBiz UI component but you have to set the token to the administrator user. 
5. If you don't want to deploy ESME locally, then you could use our test server in the cloud

Iterations

1. Use ESME as a seprate component
2. Make ESME an OFBiz component

Questions

1. User authentication: Currently, ESME has its own authentication and can't use container authentication :-<. We use tokens for our APIs and our support of the Twitter API is based on username / password.  There are ways to get around this limitation. I don't know OfBiz authentication well enough to know whether the user or an administrator could add - either manually or automatically - a token to the user object that is later used to ESME REST API calls.
2. What sort of back-end system are we talking about? Are you already using a system that we can re-use for initial tests?
3. We also have to agree on what sort of message contents (formats, etc.) will be used Are there special words (invoice, etc.) that are necessary. This is, of course, linked to what sort of back-end you guys are using.
4. What sort of rules are present in the DP? The obvious one would be to create an ESME message.
5. Regarding 10, we do respond with a XML response to those submitting messages via REST API
6. Do you want to use the old REST API or the new "Streaming API" (Ethan's baby :->)?
7. We just probably use a POST action as Ethan suggests as a first step
8. You are right about the messaging threads needing standardization (especially 2 and 9). Maybe you can look at my table in the wiki page and tell me about what the parameters mean and whether they are optional or not. We will have to map them to our fields.
9. We also have to think about user-ids. Do they need to be synchronized? Probably....