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.
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.
The ideal would seem to be to have common data such as customers, suppliers and anything else residing in a central database with standard data maintenance and query modules associated with it. Any new applications or packages should link to this, while any data used only within an application could be kept separate or integrated, as preferred.
Such a simplified view of company date is still completely futuristic. The power of computer hardware makes it possible for inefficient. Sub-optimal configurations to survive. Perhaps the IT professionals could learn from manufacturing, where the lesson was learned long ago that keeping older, inefficient, machinery because it had been paid for and was still work was an ineffective approach, which lowers quality and productivity.
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.
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.
The ideal would seem to be to have common data such as customers, suppliers and anything else residing in a central database with standard data maintenance and query modules associated with it. Any new applications or packages should link to this, while any data used only within an application could be kept separate or integrated, as preferred.
Such a simplified view of company date is still completely futuristic. The power of computer hardware makes it possible for inefficient. Sub-optimal configurations to survive. Perhaps the IT professionals could learn from manufacturing, where the lesson was learned long ago that keeping older, inefficient, machinery because it had been paid for and was still work was an ineffective approach, which lowers quality and productivity.
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 to application integration? If so the author recommends you visit www.liaison.com.
1 komentar:
Hi there, each there, I am using HP LaserJet 1500 color printer on Mac how can easily I take prints of multiple pages in Mac.
I tried all the alternatives and I did not succeeded in taking multiple pages print.
There is now concern with Hp 1500 Drivers and Hp 1500 printer software, all are working fine.
Visit my website Xerox Phaser 8560Mfp *Celiker.Blogspot.Co.Uk*
Post a Comment