EMC Consulting is hosting a customer facing webinar covering heavyweight to tcServer migration. The objective is to drive vFabric product and joint service revenue.
Migrating Java applications from Websphere or Weblogic to vFabric TC Server helps IT to reduce the cost and complexity of applications. Bruce Snyder will share best practices and use real life examples to explain how to transform your applications quickly and easily. Learn More/Register Now
I’ve been researching one of the most interesting trends in IT development and deployment architectures; the migration of development/deployment architectures from JEE Application Servers to light weight JAVA containers. Many IT organizations have been re-thinking their commitment to commercial JEE Application Servers, due to both challenging business environments that drive the need for more cost effective application architectures and, more importantly, the need to transition to more responsive/agile applications development. When we hear IT organizations talk about “migrating” their applications, they generally are focusing on one or more of three distinct situations. These are:
In the next few blogs, I'll be focusing on the migration of existing JEE applications to the most popular of the light weight containers, Apache Tomcat. There are many excellent reasons to consider moving applications off of commercial JEE servers sold by Oracle/BEA, IBM, etc. While we are concentrating on the JEE to Tomcat migration process, many of the business and technical decision factors apply equally well to the second and third situations and many IT organizations are doing some/all of them in parallel.
For development and operations teams, a presentation that covers how companies approach migrating high-cost Java Enterprise servers to a leaner solution.
The technological bloat, complexity and high cost of traditional Java Enterprise servers combined with the portability of Spring architected applications are driving businesses to consider a more lean approach to enterprise Java. Tomcat has become the most popular server for running enterprise solutions but how can you tell if your application is ready to make the switch and what is the best way to move to a lighter solution?
Understanding the role of the community, ASF, and Enterprise Tomcat vendors
Yes, bothTomcat 5.5.x and 6.0.x are thoroughly tested by the ASF community. Community testing is both ad hoc, that is, community users testing the new versions on their existing applications, as well as via the Java Community Process Technology Compatibility Kit (TCK) for the corresponding Servlet and JSP specifications. You can find high level information on the TCK program at:
Ensure Tomcat applications are managed properly from cycling updates to determining failures with SpringSource tcServer
Your business applications provide all the components that do the real work for your enterprise and use Tomcat as the engine to power that work. How can you ensure that your applications on Tomcat are managed properly? How do you cycle application updates over a group of more than twenty server instances? How do you determine the failure of application whether it is during start-up, execution or application shutdown?