EAI — There is no concept of "Management" within the specification

2) There is no concept of "Management" within the specification. Integrations need to be managed, and there is no protocol that is established for managing the state of the integration, which could bind to a transaction service (since a message could prescribe a transaction that could span multiple systems), or a middleware management service that is interested in the "heartbeat" of the system. These concepts borrow heavy from the OSI Protocol Engine, which is the origin of the adapter concept (other than SADT / IDEF0 modeling techniques). Sorry to bring up stuff dated 20+ years. A managed adapter is a thicker adapter that provides middleware services or can access middleware services, plus report out to a middleware management service to tell the MMS how its doing. Most application servers today can be utilized as a managed adapter, but no one is really formalizing the protocol (I know webMethods was promoting something they called OMI, but its been about a year now with no published specs).