Legacy application integration architecture

Information needs of modern businesses are constantly growing. Own development of a business information system is time consuming and expensive but, as an alternative, using smaller partial solutions doesn’t cover all user needs. Decision to buy a universal solution, often results in only part of it being actively and efficiently used. By application integration we manage to achieve efficient use of applications, since by linking them, we enable sharing of business logics among applications and eliminate redundant tasks. When the integration process is well planned and structured we also gain the possibility of faster implementation of changes to the system, and therefore improvements from the point of functionality as well as performance. My bachelor thesis presents and overview of different types of application integration architectures. Emphasis lays on architecture of legacy applications and different possibilities of integration realization. The term legacy application is used in accordance with its widest definition. The term covers all applications that weren’t designed for loosely coupled integration – aren’t service oriented. Service oriented architecture presents an example of application integration good practice that enables series of benefits. With described principles of integration we can also gradually transform legacy applications into service oriented. In the second part of my bachelors’ thesis I describe an integration solution that merges data gathered in Central population register (CRP) and in Register of spatial units (RPE) into a new register. Data in the register is refreshed daily by calling services CRP and RPE. These services are described in detail in this chapter. Refreshed data is available through services to other applications