System Integration

One of the most important features in a corporate IT solution is the seamless management of information between the different applications. Functional integration is often a requirement for developing new, competitive services.

With the number of systems and services increasing, maintaining flexibility and controlling integration costs requires a comprehensive and competent approach. A controlled integration is not a technical product, but a way of thinking and operating that is supported by common technology choices encompassing the entire company.

The most important tasks in controlled integration are:

• Increasing the reliability of system
  interfaces and the reusability of integration work that result in lower IT costs
• Extending the lifetime of existing systems and their improved management
• Customizing information systems in a changing business environment

When planning integration strategy with our clients, we give an opinion on architectures, technology choices and solution models. We always use technologies and tools that best serve the client. We also pay careful attention to features that are important for the successful completion of the project, such as data security, system lifetimes and versioning, as well as the management, monitoring and testability of the system.

The Integration Solution is Selected According to the Client's Needs

Different solutions are selected to create a suitable entity for implementing the integration in the client's environment. Reaktor has plenty of experience in EAI projects where standard technologies and products from different manufacturers have been used. These include SOA technologies such as WebServices, Message-Oriented Middleware (MOM), as well as Enterprise Service Bus (ESB) and Message Broker solutions built on these.

Integration is always system development, regardless of the technical solution selected. Integration and ESB products are not in and of themselves standard service architecture solutions, but tools like those traditionally used in software development. The appropriate use of these tools demands deep expertise in both software development and the construction of integrated solutions.

Jari Mäkelä, Chief Architect

Jari Mäkelä is Reaktor's Chief Architect specializing in system integration. He has
over 10 years of experience with complex integration projects.