How SOA-Enabled MOM Transforms Enterprise Business Process Integration

0 Introduction

Information system business integration is a key means for enterprises to improve system efficiency and management. The development of enterprise informationization can be divided into four stages: introduction, internal integration, process transformation, and strategic transformation.

In the introduction stage, enterprises automate certain internal functions. Most have completed this stage. In the integration stage, a unified data management system and internal system integration framework are established, giving rise to middleware technology. Message‑Oriented Middleware (MOM) offers cross‑platform, loosely‑coupled, scalable, and load‑balanced communication. A major trend is the convergence of MOM with Service‑Oriented Architecture (SOA) to enable timely business adjustments and process re‑engineering.

During the process transformation stage, information and network technologies allow data and resource sharing with partners. Many enterprises have reached or are in this stage, moving toward strategic transformation.

However, heterogeneous integration technologies increase development cost and system complexity. Traditional API‑based MOM is tightly coupled and inflexible, failing to meet rapid response demands. Existing research either focuses on data integration or requires XML‑compatible systems, limiting applicability. SOA, as a modern integration framework, offers standardization, flexibility, extensibility, and lower development cost.

This paper proposes combining SOA and MOM to achieve low‑reprogramming business process integration, designing an SOA‑based information system business integration MOM that enables cross‑platform data communication and workflow integration.

1 Message Middleware

MOM enables reliable, efficient, real‑time cross‑platform data transmission in distributed systems, shielding platform and protocol differences. Typical MOM components include a message server, data store, and naming/directory service, often using a two‑tier client/server architecture. Users invoke APIs to send and receive messages, facilitating data integration.

Since the 1990s, MOM has evolved, focusing on system architecture, load balancing, and clustering. Lack of standards hampers portability; the Java Message Service (JMS) was introduced in 1998 to unify interfaces.

2 Service‑Oriented Architecture

SOA, introduced by Gartner in 1996, defines a system architecture where services are linked via predefined interfaces and contracts, promoting reuse.

SOA consists of service providers, service consumers, and a service registry. Web Services, described by WSDL and invoked via SOAP, are the most common implementation, alongside other technologies such as CORBA, DCOM, and RMI.

3 SOA‑Based Message Middleware

Traditional MOM follows a client‑server model. This work designs a three‑tier “client‑message client‑message server” architecture. The message client, a web application, forwards messages directly when sender and receiver share the same client, reducing server load and improving efficiency. The SK)A middleware packages MOM functions as web services, publishing them according to SOA standards.

4 Business Integration Method Based on SOA MOM

The proposed method integrates MOM functions within an SOA framework, offering high efficiency, reusability, and cross‑platform capabilities.

4.1 Architecture

The integration adopts a three‑layer architecture: service layer, logical implementation layer, and resource manager (see Image 2).

The service layer provides send, receive, and forward services. Send service uses synchronous calls; receive service supports callback functions; forward service relays messages between clients and servers, avoiding unnecessary server processing.

The logical implementation layer comprises message clients, server clusters, naming/directory documents, and data stores. Load balancing is achieved via a minimum‑connection algorithm. The resource manager handles configuration, monitoring, and management of MOM components.

4.2 Integration Process

A custom message format is defined. Users register callback functions on receive services, send messages via the send service, and the system routes messages through clients and servers as illustrated in Image 3.

(1) Message Sending Users invoke receive services to register callbacks, then call the send service to issue a request.

(2) Message Forwarding The client’s send service determines the destination, forwards the message to the server, which then routes it to the target client. Direct client‑to‑client forwarding occurs when both users share the same client, reducing overhead.

(3) Message Receiving The target client’s receive service detects new messages, triggers the registered callback, and the receiving user processes the request.

4.3 Advantages

The method offers:

High efficiency: local message forwarding bypasses unnecessary server involvement.

High reusability: MOM services can be published as web services for broad consumption.

Cross‑platform support: Web Service implementation enables use across diverse hardware and software.

Flexible configuration: Users can modify configuration files or invoke services via browsers or programmatically.

5 Application Case

The approach was applied to integrate a Manufacturing Execution System (MES) with an Enterprise Resource Planning (ERP) system in a manufacturing enterprise. ERP’s planning module generates weekly production plans, which MES consumes to create daily work plans.

SOA MOM defines a standardized message format (see Table 1). Messages consist of a header (sender, receiver, queue), body (e.g., WeeklyProduct‑Plan with product model and quantity), and attributes (user‑defined fields).

In the deployment, ERP and MES each run MOM clients on separate machines; a server cluster handles forwarding. After registration of callback functions, ERP sends weekly plans to MES, which then schedules daily tasks. This demonstrates improved message efficiency, high reusability, and reduced development cost.

6 Conclusion

MOM is an effective integration technology, but traditional MOM struggles with the rapid, flexible business process integration required in the process‑transformation stage. SOA offers reusable services, lower costs, and flexible configuration. The proposed SOA‑based MOM method delivers high efficiency, reusability, and configurability, providing a modern solution for enterprise business process integration.

Source: http://www.uml.org.cn/soa/201205142.asp