Revision as of 13:24, 20 September 2021 edit Viewmont Viking (talk \| contribs) Extended confirmed users 57,953 edits Undid revision 1045413640 by Dipak4321 (talk) unexplained change of external link Tag: Undo ← Previous edit		Revision as of 14:12, 23 October 2021 edit undo 81.253.247.15 (talk) No edit summary Next edit →
Line 9: 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. JBI defines standard packaging for composite applications: applications that are composed of service consumers and providers. Individual service units are deployable to components; groups of service units are gathered together into a service assembly. The service assembly includes metadata for "wiring" the service units together (associating service providers and consumers), as well as wiring service units to external services. This provides a simple mechanism for performing composite application assembly using services.<ref>[https://coresumo.com/difference-between-c-vs-c-vs-python-vs-java/ Difference Between C vs C++ vs Python vs Java]</ref> ==JBI implementations==

Java Business Integration: Difference between revisions