Java Business Integration: Difference between revisions

Content deleted Content added
Requestion (talk | contribs)
clean up external links, convert to internal links, rm link spam
m add a quotation mark for genetive, add BPEL wikilink
Line 6:
# '''Robust In-Only''': This pattern is for reliable one-way message exchanges. The consumer initiates with a message to which the provider responds with status. If the response is a status, the exchange is complete, but if the response is a fault, the consumer must respond with a status.
# '''In-Out''': A standard two-way message exchange where the consumer initiates with a message, the provider responds with a message or fault and the consumer responds with a status.
# '''In Optional-Out''': A standard two-way message exchange where the providersprovider's response is optional.
 
To handle functionality that deals with installation, deployment, monitoring and lifecycle concerns amongst BCs and SEs, [[Java Management Extensions]] (JMX) is used. JBI defines standardized packaging for BCs and SEs, allowing components to be portable to any JBI implementation without modification.
Line 24:
In addition, the Project [[GlassFish]] open-source Java EE application server comes with JBI runtime from [[Open-ESB]] project.
 
[[Java EE]] SDK also includes JBI runtime and a [[BPEL]] orchestration engine.
 
Oracle <!-- change this to a reference [http://www.oracle.com/corporate/press/2006_oct/openworldsf06-07.html?rssid=rss_ocom_pr claims] --> claims its Fusion Middleware comes with JBI implementation.