SOA is an architectural concept or idea. It is an open architecture that creates business processes and the IT infrastructure that supports them in a secure and standardized way. To satisfy the various ideas and functions of SOA, a standard called JBI is created, and ESB is an implementation of the JBI specification. 

EAI is data-centric integration, Web Service is API-centric integration, and ESB is service-centric integration. EAI is a technology created for the purpose of data integration between heterogeneous devices, and uses a vendor-dependent API. ESB is a technology that implements the JBI standard specification and provides an infrastructure for integrating legacy/new services (processes) and data between heterogeneous types in a standard way. 

ESB embraces 100% of the EAI function as an advanced technology by absorbing it as part of the EAI function. 

Improves development productivity by providing optimized libraries and templates for integration with various services. Built-in system remote control, intelligent error tracking, and real-time message tracking management system enable quick response in case of failure. By applying various international standards, it can be linked with any system that complies with the standards. It is a product that applies the domestic system-optimized process by applying the know-how experienced in various linked integration projects. It is a product that has been applied to a number of large sites and has proven stable mass data processing. 

It consists of ESB engine, service adapter, management console, and development tools. 

(ESB Engine): Essential functions such as message routing, service combination, intelligent routing, etc. 

(Service adapter) : Function to send/receive data in various protocols 

(Management console) : User interface for ESB engine/adapter management and control. 

(Development tool): GUI tool for service development​ 

We provide linkage frameworks, frequently used linkage templates, modelers for process design, and linkage libraries. Also, we provide a modeler/message conversion tool based on HTML5. 

The MESIM ESB operates in standalone mode and does not require a separate WAS. 

Basically, the link section is linked with ARIA/SEED encryption. It provides a separate 3rd product (PKI) interworking interface. 

Depending on the content of the message, it provides intelligent dynamic routing capabilities for branching (Pipe & Filter, Splitter, Aggregator, Multicast, Recipient List, Dynamic Router, Contentets-Base Router, Routing-slip, Sequencer, MessageFilter). 

It supports synchronous/asynchronous support and various topic (pub/sub) message transmission methods.