Page History

Simple Description

John Smith, Sales Chief of ACME, changes the credit level of a customer "Big Pipe".  Once the change has been made in OFBiz, the ECA associated with this event sends a message to Apache ESME where other sales staff can see that the status for the customer has changed.

In this initial use case, there is no ESME client embedded in the OfBiz UI but rather the user UI is that of the Stax environment or other connected clients.

Technical Details

Overview

Required Environment

• Apache ESME Server (http://esmecloudserverapache.dickhirsch.staxapps.net/)
• OFBiz Server (https://demo.ofbiz.org)

...

• OFBiz
  • John Smith - Sales Chief
• Apache ESME (All members of Apache ESME Pool "BigPipe")
  • Ralph Butler - Sales Staff
  • Amy Davidson - Sales Staff
  • John Smith - Sales Chief
  • OFBiz Back-end

...

1. ECA that responds to changes on customer object
2. One generic service "sendEsmeMessage" that sends ESME messages. This service should be configurable with such things as token (needed to use Apache ESME's APIs) and server URL. Initially, this could probably use existing HTTP Services to make a HTTP Post call to the Apache ESME API method "send_msg" with the extra parameter "token". You could also hard-code the server name and token for an initial test.
3. One specific service that calls the generic service and formats the message.

...

1. Iteration 1: SendESMEMessage is called directly from the ECA. SendESME Send Apache ESME service has a hardcoded Stax URL with a hardcoded taken, server URL and message.
2. Iteration 2: A dynamic message that contains event details is sent to SendESMEMessage
3. Iteration 3: A specific service is created that calls with generic service with amessage a message to send as a parameter
4. Iteration 4:  The details for the Apache ESME Call (Server URL, Token, etc) are made configurable via a UI.

...