How do I add Camel Support to an existing application -


i want "open" application based product enterprise integration camel. is, want customers buy app able provide information app via camel, without having create full public api on app.

i've read lot of camel documentation, examples, book, i'm still having trouble getting started conceptually. first, can camel running: app has spring support, don't know how "deploy" it.

let me set huge oversimplification of use case:

  • let's want app pop dialog message in it. web app controls when dialog pops up.
  • i want message come other software system customer owns - , want via camel. (could activemq, email, file deposited somewhere, stuff camel supports)
  • the customer has configured message in app @ earlier point, key message get. it's inout exchange (in camel terms). in other words:
    • at configuration time, customer says: "i have 'foo' messages need shown when dialog pops".
    • at runtime app says: "hey camel, i'm show dialog, have 'foo' message me show in it?"

that's it. pretty simple, , should able solve based on i've read, can't quite grasp case falls in examples , tutorials. think disconnect of solving specific integrations problems in specific solution. whereas i'm opening app sort of general integration - don’t have details on cusomer side of camel.

so specific questions:

  1. i'm assuming app needs camel endpoint, correct? e.g. customer sets route dialog-popping feature in app.

  2. who should run camel in case, customer, app, or both? (i think "run" camel means starting camelcontext right? can in app, no problem, want?)

  3. what specifics: create consumer or producer?

  4. what customer perpsective? how send message endpoint? how request? customer need access api, or camel need? need start camelcontext?

q1. i'm assuming app needs camel endpoint, correct? e.g. customer sets route dialog-popping feature in app.

a1. 1 option, in camel terms application camel component. think bad decision. tying application dependant on camel.

what should have interface application, web-service, active-mq, etc. camel communicate application.

q2. should run camel in case, customer, app, or both? (i think "run" camel means starting camelcontext right? can in app, no problem, want?)

a1. should develop camel service separately application. integration framework. should decoupled each other. started separate service application, listening on different endpoints (email, a-mq, file drop) , routing information application exposed interface.

q3. specifics: create consumer or producer?

you create consumers consume requests sent application customer (email, a-mq, file drop). producer used send these messages applications interface.

q4. customer perspective? how send message endpoint? how request? customer need access api, or camel need? need start camelcontext?

camel has lots of different consumers customer use, listen emails, expose web services, wait file drops. customer need access these endpoints can communicate system. wont need start camel context, camel sits behind interfaces expose , routes messages endpoints have defined.

however, need these endpoints? not more sensible have 1 interface application customer use?


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -