Page History

...

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 ESME's APIs) and server URL. Initially, this could probably use existing HTTP Services to make a HTTP Post call to the 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.

Iteration Sugestions

1. Iteration 1: SendESMEMessage is called directly from the ECA. SendESME 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 to send as a parameter
4. Iteration 4:  The details for the ESME Call (Server URL, Token, etc) are made configurable via a UI.