System and Application Integration e-service providers

DELAROSE PRATESIA SUNDJOKO – 2301906911

System and Application Integration e-service providers

Enterprise application integration (EAI) is an emerging approach to architectural design that connects previously separate and isolated systems to give them greater benefits (Themistocleous, 2004). EAI is usually a backroom technology (Sharifet al., 2004). That is, it represents an architecture that supports business processes within an organization and is not directly visible to the general staff or its clients and stakeholders. EAI is not a specialized technology (Vinoski, 2002) and often requires a portfolio of different techniques (Themistocleous, 2004). Instead, THEAI is a framework for combining various integration technologies, such as message intermediaries, adapters, and application servers (Linthicum, 1999; Serian, 2002; Themistocleous, 2004).

Electronic commerce is radically changing the competitive landscape. More and more, companies need to have stronger ties with customers and suppliers. In this business scenario, it is important for the company to have an information system (SI) that encourages the flow of information without a hitch. The paradigm that addresses the needs of this company is known as Enterprise Application Integration (EAI). In this paper, we examine EAI in detail and develop EAI cases in today’s business environment. We discuss the different ways in which EAI can be realized and describe how companies can increase profits by implementing appropriate EAI solutions. It concludes with a discussion about the future direction the EAI might take.

Enterprise Application Integration is one of the interesting words recycled all the time in the software industry and provides a basic idea of its functionality. EAI is a general category of approaches that provide interoperability between several heterogeneous (different) systems that make up a typical enterprise infrastructure for communication. Basically, large organizations support hundreds of applications. Most of these applications are older systems such as SAP, mainframe computers and most are written in COBOL format. An organization can be used separately applications, with its different functions. This modularization is always suitable for large systems. It’s easier for implementations to modernize the task of running a business into a few small tasks. New technologies are developed at very high speeds by giving advantages to legacy systems. It is therefore natural for organizations to reduce legacy maintenance costs. The first approach is to replace the Legacy system with a new system, but it’s not a good option to replace legacy systems.

The second approach is instead of replacing legacy systems, build infrastructure between new systems and existing Legacy systems and we can do this using Enterprise Application Integration. However, to benefit from such a distributed and modular type of system an enterprise must implement technologies that address the following issues: Interoperability, Data Integration, Robustness, Scalability, and Interoperability Stability. Different components of the infrastructure can be used in different platforms, languages, data formats, and possibly different operating systems, so we have to deal with that interoperability. Data flow between applications may occur in different formats so it is necessary to integrate the data by converting it to the system’s destination format. Robustness, Stability, and Scalability Because they are the glue that brings together a modular infrastructure, integration solutions must be very robust, stable, and scalable.

Reference

Jitendra Joshi, Nisha Singh and Manjari Kumara. (2012). Web Service-oriented Architecture Modeling with Pattern for Electronic Business Organization. IJARCSSE Research Paper [Online]. 2(9), pp. 456-460. Available www.ijarcsse.com/ docs/ papers/9_ September2012/…/V2I900179. Pdf