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.
Originally it was felt that object oriented databases would overcome these problems for new applications. However, many applications are developed independently, and the problem of duplicate entities persists. The solution would be to have one database, with all applications making use of it, especially for common data.
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 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.
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.
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.
Originally it was felt that object oriented databases would overcome these problems for new applications. However, many applications are developed independently, and the problem of duplicate entities persists. The solution would be to have one database, with all applications making use of it, especially for common data.
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 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.
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 solutions? If so the author recommends you visit www.liaison.com.
0 comments:
Post a Comment