VCOS

 
 
 
What are the real challenges in application integration?
 
 
 
Challenges in Application Integration Today – This illustration depicts the complexity and the number of domains involved in application integration within a typical bank.
 
The obvious challenge is getting the independently designed systems and various disparate technologies to work together. The real challenge is getting all the people who represent the wide and varied parts of the enterprise to work together. A typical bank has a least 6 main business areas, 8 delivery channels, 4 different computing platforms, 4 service providers, a few software environments, some recent technologies and a network / communications group. Added together, this makes at least 24 different domains. Together with the types of people active in projects, maintenance, and support, who vary from full time staff, contractors, software suppliers and consultants, this is a highly complex situation - and it is the normal state of a typical bank today, and not an exception.Today, we attempt to manage and execute multiple projects, enhance and support the entire IT facility in the same manner as we have been doing it for the last 2 decades.
 
People are expected to work together in an integration project. We tend to think they work well together. However they are constrained by the current process of integration methodology. The problem is not obvious, in individual parts of the integration work. Individual parts, typically does not present themselves as a problem.However when two or more of these parts, are integrated together, the disparity between the parts (unknowingly or otherwise) contributes to issues that have the propensity of permeating the whole. In integration projects, this is a problem of the collective, and is a management issue. This collective problem in a typical enterprise, however manifest itself in different forms like: escalating costs, shortage of skilled resources, long product development cycle etc.
 
A computerized system to create, host, manage and administer Integrated Applications throughout its life cycle (as opposed to a set of tools middleware/EAI).
 
 
A Virtual Operating Environment – This illustration depicts VCOS running in a virtual operating environment spanning across different underlying native environments like MVS, OS400, Sun Solaris, HP-UX, Windows NT and Windows 2000.