Getting different applications to talk to each other is a problem faced by many companies. Application integration is particularly troublesome when legacy systems are involved, and transferring data between old mainframe systems and more modern applications can be cumbersome and time-consuming. A good deal of time is spent on ensuring this happens, and software is often available to help with the process.
A lot of useful middleware exists to handle these problems, but there are so many different languages, operating system and databases around, that it is impossible to handle every combination perfectly, which still leaves a place for in-house bridges. These application bridges are often particularly maintenance intensive.
It was hoped that object oriented applications would overcome these problems in newer systems. But this is only true if an enterprise database is created, and all applications are based on it. With many applications having their own databases, the problem is still around to haunt IT departments.
Because proprietary application packages are popular, it is still possible to have a variety of object-oriented databases used by different applications where entities common to several applications are duplicated. With this situation the problem simply continues in an up-to-date guise. Because these packages are common solutions to requirements, the situation really has not changed much.
What is needed to resolve the situation today is a situation where an enterprise database with standard modules to update, maintain, and query the common data is created. Any new applications would then simply interface with that central database. Application specific data could be integrated with the enterprise database or kept separate, as appropriate.
Unfortunately this scenario is very much one for the future. At the moment the world of application systems is very imperfect, as companies still struggle to come to terms with their model T applications. What is needed is the same sort of attitude as with machinery, where equipment that still works is quickly replaced by more efficient machines: an approach that drove America to the forefront among manufacturing nations.
As it is, the productivity of many IT departments is abysmal, despite the many dedicated, intelligent, hard-working professionals they employ, many involve in application integration. In fact, smaller companies usually just live with the various versions of the same data, and simply capture it several times. With so much to be done, it is easy to imagine that the present situation will be viewed with incredulity by future generations of IT professionals, once a rationalized approach has been developed.
A lot of useful middleware exists to handle these problems, but there are so many different languages, operating system and databases around, that it is impossible to handle every combination perfectly, which still leaves a place for in-house bridges. These application bridges are often particularly maintenance intensive.
It was hoped that object oriented applications would overcome these problems in newer systems. But this is only true if an enterprise database is created, and all applications are based on it. With many applications having their own databases, the problem is still around to haunt IT departments.
Because proprietary application packages are popular, it is still possible to have a variety of object-oriented databases used by different applications where entities common to several applications are duplicated. With this situation the problem simply continues in an up-to-date guise. Because these packages are common solutions to requirements, the situation really has not changed much.
What is needed to resolve the situation today is a situation where an enterprise database with standard modules to update, maintain, and query the common data is created. Any new applications would then simply interface with that central database. Application specific data could be integrated with the enterprise database or kept separate, as appropriate.
Unfortunately this scenario is very much one for the future. At the moment the world of application systems is very imperfect, as companies still struggle to come to terms with their model T applications. What is needed is the same sort of attitude as with machinery, where equipment that still works is quickly replaced by more efficient machines: an approach that drove America to the forefront among manufacturing nations.
As it is, the productivity of many IT departments is abysmal, despite the many dedicated, intelligent, hard-working professionals they employ, many involve in application integration. In fact, smaller companies usually just live with the various versions of the same data, and simply capture it several times. With so much to be done, it is easy to imagine that the present situation will be viewed with incredulity by future generations of IT professionals, once a rationalized approach has been developed.
About the Author:
Peggie K. Lambert is an expert in data management and integration. Need to learn more about application integration? If so the author recommends you visit www.liaison.com.
