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.
There is a lot of middleware around designed to help overcome these problems, and this is often very helpful. Failing this, a procedure to download, from one database, convert the data, then upload to another database might be necessary. Such procedures are often unstable and demand the attention of highly skilled people.
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.
However, packaged solutions would still depend on their unique databases. This means so there will still be considerable redundancy, necessitating communication via some form of middleware. With packages often being preferred, there is really no solution in sight for this dilemma.
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.
There is a lot of middleware around designed to help overcome these problems, and this is often very helpful. Failing this, a procedure to download, from one database, convert the data, then upload to another database might be necessary. Such procedures are often unstable and demand the attention of highly skilled people.
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.
However, packaged solutions would still depend on their unique databases. This means so there will still be considerable redundancy, necessitating communication via some form of middleware. With packages often being preferred, there is really no solution in sight for this dilemma.
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.
Tidak ada komentar:
Posting Komentar