Processing Asynchronous REST Requests in Orchestration Designer Ross

Processing Asynchronous REST Requests in Orchestration Designer Ross Yakulis

Orchestration Designer 4 Web service call – Create a REST web service operation in OD. – The operation must pass the web service – session: sessionid – the MPP IP address, get from request. get. Remote. Addr(). Need to write Java to get the value and store into an OD variable. – a handler URL for the reply 4 Getting the reply – Need to add a catch for externammessage. <vxmlevent> – vxmlevent is the name the web service reply handler sends to the CCXML basic HTTP IO Proccessor – When the event is caught, use goto and a capture expression to get the result data. The expression is application. lastmessage$. content Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 2

Web Service 4 Web Service – Axis Limitations – Must return 200 Okay – Must return some data, even if it is dummy data ({"result": “okay"}) – After completing the request the results are posted to the handler URL with the CCXML session id and the MPP IP address. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 3

Web Service Reply Handler 4 Use the IP address and session id to send an event to CCXML. vxmlevent is the name of the event to be sent to the VXML application and message is the data 4 Note to invoke the CCXML HTTP IO Processor you have to have mutual authentication setup between the application server and the Experience Portal system 4 Send avaya. vxml. event with parameters vxmlevent and message as well as session id. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 4

Experience Portal 4 Default CCXML has a transition for the event avaya. vxml. event – Input vxmlevent, name of the event to send to vxml – Input message, the payload or reply from the web service. – This transition sends an event to the vxml application 4 Note, the data for the external event to VXML is limited to a single string currently. So the data may need to be parsed once the application receives it. – Could also send the data as a string delimited by | which OD would treat as a collection. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 5

Static Runtime Model OD Speech OD data Node WS Handler Request + Callback URL and CCXML Session Id Reply + CCXML Session Id Start Dialog HTTP Post to the basic httpioprocessor (avaya. vxml. event) with vxmlevent set to asyncwsreply Voice Browser CCXML Browser Event to VXML (externalmessage. asyncwsreply) Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. Asynchronous REST Web Service