Most white papers and webinars available on the Internet about choosing enterprise middleware focus the selection process around criteria such as licensing costs, technical coverage of long lists of specified functionalities, and vendor viability. While these criteria may have been suitable in the past, the experience of many enterprise architects leading J2EE projects over the past few years suggest that they are not enough. What’s missing? People costs.