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.
While middle ware exists to help overcome these issues, the permutations of languages, equipment, databases, and operating system are never ending, so it is impossible to cater for every eventuality. If proprietary tools are not available, the the solution is a home-grown procedure to do the job of communicating between systems. Here the skills shortage may affect the maintainability of such software bridges.
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.
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.
The best solution would seem to be a central repository database which houses all data common to several applications and provides the functionality to maintain and inquire on the data. New applications or packages would interface to that master database. Data used by only one system could be handled as appropriate.
At the moment this would seem a dream. The Information systems world is sitting with Lamborghini computing power and Model T applications concepts. Perhaps IT should adopt the same approach as manufacturing, where older, less efficient machines are quickly replaced: not to do so makes a company uncompetitive, and saving money by using old equipment is known to be a wasteful chimera, resorted to by unaware managements.
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.
While middle ware exists to help overcome these issues, the permutations of languages, equipment, databases, and operating system are never ending, so it is impossible to cater for every eventuality. If proprietary tools are not available, the the solution is a home-grown procedure to do the job of communicating between systems. Here the skills shortage may affect the maintainability of such software bridges.
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.
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.
The best solution would seem to be a central repository database which houses all data common to several applications and provides the functionality to maintain and inquire on the data. New applications or packages would interface to that master database. Data used by only one system could be handled as appropriate.
At the moment this would seem a dream. The Information systems world is sitting with Lamborghini computing power and Model T applications concepts. Perhaps IT should adopt the same approach as manufacturing, where older, less efficient machines are quickly replaced: not to do so makes a company uncompetitive, and saving money by using old equipment is known to be a wasteful chimera, resorted to by unaware managements.
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.
0 التعليقات:
إرسال تعليق