Architectural Pattern for Inter-Organizational Middleware Systems

Effective Business-to-Business (B2B) relationships typically rely on seamless integration of partner's processes. Inter-Organizational Information Systems (IOIS) have largely been endorsed as B2B enablers. They are defined as automated Information Systems crossing organizational frontiers and aiming to synergize partners' efforts in increasing competitiveness and cost management (Eom 2005). The components in IOIS responsible for the actual bridging between partners' heterogonous systems are referred to as Inter-Organizational Middleware Systems (IOMS). While IOMS critically hold business information, they lack both research and standardization. Instead, chaotic and costly efforts to architect and manage IOMS have dominated the market. As a remedy, we propose an IOMS-specific architectural pattern that could be used to develop its architecture(s). First, the notions of frameworks and architectures are presented. Then, approaches to IOIS architecture and process management are discussed, before IOMS's need for its specific architectures is presented. The MAPIS architectural design is then proposed and its merits and limitations are discussed.