javabeans - How do I use a MessageEndPoint in JCA in a Java EE compliant server? -

javabeans - How do I use a MessageEndPoint in JCA in a Java EE compliant server? -

i'm new java connector architecture (jca) , java enterprise edition (java ee) in general. have been reading through jca 1.6 specifications, i'm not 100% getting everything.

so here questions have:

is messageendpoint referring enterprise info scheme (eis)? or application on server trying utilize message obtained eis? does messageendpoint need bean? what mean activating messageendpoint?

can show simple illustration on working/deploying messageendpoint? i'm testing on websphere application server - liberty profile

let's clarify terminologies first:

outbound messaging message starts server (to more accurate it's initiated app have on server, websphere liberty in case) , end @ eis. inbound messaging message starts eis , end @ server. message endpoint in general place message end sitting/getting received @ specific stage of life cycle.

so outbound connectivity, referring situation application obtains connection external eis , reads or writes info it. inbound connectivity referring situation resource adapter (ra) listens events external eis , calls application when such event occurs.

illustration of outbound ra

illustration of inbound ra

what messageendpoint mean in jca?

the application server (ex: websphere liberty) provides message endpoint mbeans assist in managing delivery of message message-driven beans acting listeners on specific endpoints, destinations, , in managing eis resources utilized these message-driven beans. message-driven beans deployed message endpoints not same message-driven beans configured against listener port. message-driven beans used message endpoints must deployed using activationspecification defined within ra configuration jca (found in ra.xml file) .

what mean activating messageendpoint?

with message endpoint mbeans, can activate , deactivate specific endpoints within applications ensure messages delivered listening message-driven beans interacting healthy eis resources. capability allows optimize performance of jms applications in situations eis resource not behaving expected. message delivery endpoint typically fails when message driven bean listening invokes operation against resource not healthy. example, messaging provider, inbound resource adapter jca compliant, might fail deliver messages endpoint when underlying message-driven bean attempts commit transactions against database server not responding.

does messageendpoint need bean?

it should. otherwise end in big mess creating own unconventional way of doing stuff beat purpose of next java ee specification in first place. design message-driven beans delegate business processing other enterprise beans. not access eis resources straight in message-driven bean, indirectly through delegate bean.

can show simple illustration on working/deploying messageendpoint?

check sec resource i'm mentioning below helpful example.

useful learning resources:

managing messages message endpoints develop inbound connectors

java-ee javabeans websphere-liberty jca