ill master specific functions and data, the IIC must work out the semantics of how the applications will communicate and exchange data. To do SO requires skilled implementers experienced with the specific applications in question. Such people will understand how the applications are likely to behave and interact, thereby minimizing "trial and error" tactics and helping to overcome irritating hurdles such as poor documentation or confusing data models. As in any endeavor, it is critical to have people with enough experience who understand the tricks of the trade to overcome common problems rapidly and adapt to new, unique problems that arise. Keep in mind that an EAI implementation should not require as many developers as it does analysts. Most EAI packages, as we have mentioned, are equipped with many tools to allow developers to configure and manage them. As we have also seen, EAI sometimes takes on application functions and other roles that are not necessarily "built in." The kinds of development necessary for the EAI enhancements we discussed in our case studies require a small number of highly skilled developers with knowledge of the EAI technologies at hand. As we will see in the next chapter, once an EAI implementation is up and running, it requires on-going maintenance and support. Experts skilled in systems and database administration are absolutely necessary to the daily operation of an EAI environment. Developers may need to remain on staff to Chapter 6 - Integrating the OSS Platform maintain any special enhancements or logic added to the integration layer or various applications. One of the handicaps these people will face is a general lack of tools for monitoring an OSS platform. Thus, those responsible for its maintenance must be skilled at diagnosing the often-cryptic problems that are bound to occur. 15.4 Is Enterprise Application Integration Possible? Before answering whether achieving EAI, a seemingly daunting task, is possible, it is worth reiterating some of the major challenges that EAI presen