Evaluation of EAI Monitoring
EAI (enterprise application integration) is an interesting leg in today's IT landscape. I remember the days when started my carrier 13 years back when we all wandered between mainframes, AS400, database and new age object oriented java. With the passage of time I focused my area to be more specialized as the demand of market was to identify from the lot.
Java specialization was becoming readily available as most of the application started becoming loosely coupled. With this said tier based application was the faces of IT in late 90's and start of 2000. With this distributed architecture EAI found its place. I decided to focus myself in EAI technology after putting my fingers in AS400, Java and database technology.
Since then I have been following EAI and its progression. EAI vendors have increased over the period and the stack based companies like SAP, IBM, and Oracle have come up with their own middleware. The top notch players were Tibco, BEA, Seebeyond, webMenthods, Vitria etc. Along with the same group IBM had is Websphere in the market. Enterprise offering company joined in the game late and most of them tried acquiring the independent vendors.
Middleware originally structured itself by hub and spoke or bus modal. With the new age offering SOA, shock wave transmitted within the EAI space. The maturity of SOA was highly dependent on the EAI. The reason being was it actually in true sense de-coupled the application. It was already playing an orchestration role. The only thing needed was the face lift of middleware to SOA suite. It was not easy as said to change the face. It came with its own challenges.
Traditional EAI was even though decoupled the system but the internal offering was vendor dependent. Each vendor interpreted the transmission in its own ways. This led the dependency heavily on the tool. The challenges started visible when transformation business started within the organization. Industry started means of saving cost, improving efficiency and reducing redundancies by consolidating into ERP packaged implementation. During this this time the need of standardization was realized. Where ever the ERP packaged solution was implemented its native EAI came by with cost saving measure. The architecture community was put in spot once again to re-define the co-existence of dual middleware strategy. Lot of company decided to migrate to single EAI this became the revenue for the consulting companies. Even though the data transmission was standardize to an extent but the transformation, orchestration was native to the EAI vendor.
SOA guiding principle made an impact on the middleware strategy. The aspect of re-usability, standardization and discoverability was re-invented for middleware. There was a push within the community to standardize the transformation and orchestration code. Evolution of Standard Integrated Development Environment (IDE) came in place. Eclipse (IDE) for example widely accepted with major IT vendors. Most of the product vendors shipped their software with standard IDE environment with product specific wrappers. This internally became standardization of code.
The future of EAI is now redefined as SOA middleware. The development process is standardizing within the SOA Middleware. The output code (like BPEL) can be ported within any SOA Middleware. The discoverability, standardization and re-usability indeed changed the course of traditional middleware. The openness now largely welcomed by the architect group. Business is now getting more agreed upon technology changes.
Written by and submitted on behalf of Mukundan Iyengar


From the key numbers from the chart, collaboration impacts:
The challenge that I believe we are seeing today in Enterprise 2.0 is a very strong focus and push around tools instead of strategy. Collaboration is nothing new and goes back to caveman days where teams had to work together to hunt animals. Cavemen didn't have an enterprise social software platform to discuss ideas around where and how to hunt, yet they still managed to do a fantastic job of hunting. Why then today are we so focused on platforms and tools when the real issue is around culture and people? I'll talk more about some of the potential hurdles (as well as other topics) in the near future, but for now read and digest the report so we can discuss it.
