Change is constant and this saying becomes even more meaningful in the IT arena. Information Technology is entirely dependent on the needs of the end customers. Needless to say business processes, business logic and business requirements change constantly. There is always scope for new methodologies, innovations and new thought processes. New acquisitions, collaborations and business partnerships have become the face of world trade. Moreover everyday some new striking technology is coming at our doorstep keeping the IT techies on their toes. So to keep the old systems in sync with the new technologies INTEGRATION is required.
Why Integration.
The processes in IT industries are very rigid; they are locked in source code, difficult to change or modify once in production and comply with the specific end user requirements. Customization becomes very expensive sometimes. Adding a separate layer in the architecture for integration and business process change and coordination can solve some of these issues.
Often to incorporate flexibility within a software architecture, integration layer is included at different levels. Let us say in an organization, mainframe systems act as a source system for employee information and a compatible payroll system is used to generate the pay slips of its employee. Also the organization is having several applications on different technologies (let us say on Microsoft platforms). After the advent of SAP technologies, the organization wants to have SAP based payroll system. Also they want this application to communicate with other applications which are running on Microsoft Platforms. What could be the approaches???
One possible solution is to replace the legacy payroll structure with SAP. But this is going to be very costly. It will also need to disrupt the running application on the present legacy system. Also there is no guarantee that in future a better technology will not make this approach unviable. Moreover, it would not be able to communicate with other applications. INTEGRATION is the key here.
Integration is a powerful mechanism which can integrate two different sets of applications of two companies if merger happens. In case of business-to-business partnership scenarios, Service Oriented Architectures and Web Service Technologies plays an important role in re-using each others core operational functionalities, though on different platforms.
Types of Integration
1. Data level Integration.
This kind of integration happens when transformation of data happens between systems in an enterprise. Drivers and adapters are used as port entry for retrieving and pushing information.
2. Presentation level Integration.
This kind of integration happens when the integration is needed at GUI level where the web portals need to communicate with each other though on different platforms. It is quite evident in the case of collaborations between the two enterprises.
3. Application level Integration.
In an enterprise the different applications though on different technologies must communicate with each other. To enable this many interfaces are bundled together in one package.
4. Process Integration
In this kind of integration two or more processes of two or more enterprises are integrated seamlessly to operate them as one.
Major Players in the Market
All the product based companies have understood the power of integration and developed the integration tools to integrate the IT applications to speak in the same language seamlessly. Now the business processes can access data stored in wide range of systems and share seamlessly to streamline the work flow. The major players providing integration tools are:
1. Microsoft.
With tools like BizTalk, it has enabled all the business processes talking to each other simultaneously. Features like RFID and ESB powered with SOA and WCF capabilities make this tool a leader in the market.
2. Tibco.
Tibco has made business and process management even simpler. It not only covers all the key aspects of Enterprise Application Integration but also provides a robust scalable and reliable framework for large scale projects.
3. Web Methods.
Being a key player in integration domain, Web Methods utilize the key principle of message broker and hub and spoke messaging. It is based on Java and supports multi platform diverse services, transformations between one format to other and communication between different systems.
4. Siebel.
Siebel EAI has a suite of protocols to exchange the information bi-directionally with other applications and technologies. The architecture majorly contains connectors like SAP, PSTF and workflow mechanism, adapters, transformers, converters and object managers. It also supports Web Services.
5. PeopleSoft.
It provides the integration solutions for PeopleSoft applications and third party systems. This also completely relies on messaging and message broker mechanism, both synchronous as well non -synchronous.
As long as advancements will happen in technologies, need of integration tools will continue to enable the transition and evolution of enterprise systems. If I call the old legacy systems as the First World and the new technological advancements as the Second World then I must say the integration domain represents the Third World.{t}

An energetic chatterbox, Vikash loves to blog and maintains his own fundae towards life. An Electronics engineer by qualification and a software geek by profession, this fellow is a maverick of sorts. Hardly one to sit around, he is full of plans – whether it is for outings or simply debating indoors. He is also known for his unique hairstyle and irrepressible laughter, both of which he has no control over. Born and brought up in Bokaro, he has been living quite a nomadic life by constantly moving around to places ranging from Hyderabad, Pune, Bangalore and most recently Hawai.