Enabling the communication of the vast array of different applications normally found in larger companies is a huge problem. When old mainframe legacy systems are part of the equation, data transfers between applications can become extremely complex and require expert support. In fact, large amounts of Of the efforts and and expenses of modern Information Systems departments are swallowed by the bottomless pit of application integration.
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.
The advent of the concept of object orientation seemed to promise some relief. Unfortunately this did not address the problem. Only if there is only one occurrence of any data, with all applications accessing it directly would the problem be obviated. As long as there are Application specific databases, the problem will persist.
Different application packages will still have their own databases, and this could easily lead to duplication of entities and redundancy. The need for middleware to capture or transfer common data is once more created. As it often happens that packages are acquired, this scenario is an ongoing problem for most organizations.
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.
In any company, a lot of effort goes int application integration. Because the complexities may be too much to handle, many organizations simply accept the situation and live with the multiple capturing of data. It is to be hoped that some rationalization will occur as the Computer software industry matures. Perhaps future Information Professional will be amazed and the current haphazard approach to such an important business function.
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.
The advent of the concept of object orientation seemed to promise some relief. Unfortunately this did not address the problem. Only if there is only one occurrence of any data, with all applications accessing it directly would the problem be obviated. As long as there are Application specific databases, the problem will persist.
Different application packages will still have their own databases, and this could easily lead to duplication of entities and redundancy. The need for middleware to capture or transfer common data is once more created. As it often happens that packages are acquired, this scenario is an ongoing problem for most organizations.
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.
In any company, a lot of effort goes int application integration. Because the complexities may be too much to handle, many organizations simply accept the situation and live with the multiple capturing of data. It is to be hoped that some rationalization will occur as the Computer software industry matures. Perhaps future Information Professional will be amazed and the current haphazard approach to such an important business function.
About the Author:
Peggie K. Lambert is an expert in data management and integration. Need to learn more about application integration services? If so the author recommends you visit www.liaison.com.
No comments:
Post a Comment