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.
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.
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.
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.
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.
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.
No comments:
Post a Comment