JMS, Message Queing Service, ESB related question -


assume there 2 web services , b setup in soa infrastructure.

web services depends on information available locally installed desktop application (its legacy application based on c++ programming , provides c++ api give information needed web service a).

the scenario this: human actor (which can considered consumer of web service b)logs website , clicks button requests service provided web service b. part of request, id sent. web service b sends request web service id. web service uses id somehow determine way talk locally installed desktop application of human actor originated request.

the main problem how can web service connect desktop application , information in reliable way using soa infrastructure.

assume in soa java based except desktop application.

the desktop application crm application own internal database , not traditional database mysql. provides basic textual information human actor , customer(s) of human actor in installed crm desktop application.

i want use soa related technologies though may more complicated.

given above details:

how can use jms solve problem?

if jms not right solution, esb , how can use esb solve problem?

the communication desktop application determined different methods application capable of performing. if application has database backend, esb can facilitate communication predefined adapters specific database being used. if application has api can tapped programmatically, method well. not sure jms appropriate solution since given use case want synchronous reply. putting jms in middle (somehow) break reply , rather return asynchronous response.

i recommend looking more functionality available in desktop application , findings start evaluating esb functionality. esb may overkill use case if plan more operations may become valuable.


Comments

Popular posts from this blog

c# - how to write client side events functions for the combobox items -

exception - Python, pyPdf OCR error: pyPdf.utils.PdfReadError: EOF marker not found -