There is no shortage of well-known reasons for wanting to migrate your Java EE web application to open source Tomcat. But without development experience with both your current Java EE application server as well as with Tomcat, it isn’t clear what you must change in your Java EE application to get it to run properly on Tomcat. The benefits of being able to run it on Tomcat are significant — for example, Tomcat is free to run in production,
Tomcat 7.0.6 has just been voted the first Tomcat 7 stable release! This makes Tomcat 6.0.x only a supported stable release, not the latest stable as it had been for several years. A little more than a half a year ago we saw the first 7.0.0 beta release, which was exciting, but now the first stable release is ready to use.
A major branch stable Tomcat release is an infrequent event —
With a focus on production ready features, Tcat Server has become the leading enterprise Apache Tomcat in the world. As more and more leading organizations are adopting Tcat Server and using it to run their most demanding applications, we have been hearing from them about the features they need for gaining better visibility and for managing their applications in production.
We are pleased to announce General Availability of Tcat Server 6 R4,
Do you ever ask yourself these questions: “Can I eliminate the redeploy phase from Tomcat’s development cycle? How can I more efficiently diagnose performance bottlenecks in my Tomcat application? How can I simplify configuring Tomcat for my application?”
Apache Tomcat users spend 160 hours per year waiting for redeploys, not to mention the time getting back into the flow of coding. They also spend quite a bit of time configuring Tomcat for deployment to production,
Organizations running Apache Tomcat in production on Windows often want to run Tomcat as a Windows service. This removes the need for someone to be actively logged into the server and provides an easy way to integrate with Windows management tools. In this blog, I will explain the easiest way to run Tomcat as a Windows service and how you can do this for multiple instances as well.
Running an instance of Apache Tomcat as a Windows service is not complicated,
“Having Trouble With Multiple Instances” is one of those famous Tomcat users list topics that never goes away. In fact, the question has been asked so many times that at this point, the people asking it are lucky if they get a response that’s more helpful than RTFM.
These errors are almost always caused by port conflicts. When running multiple instances of Tomcat on a single machine, each instance must be configured with a unique set of port numbers.
Recently I was hiking with couple of friends – one of them runs IT operations for a large consumer company. He was on call that weekend, so, sure enough, his phone rang: it was the customer service coordinator who was saying that her team was not able to access the application. My friend had to run back to the car to power up his laptop, connect to the VPN using his wireless card, check status of his Tomcat servers and jump on a bridge call.
Most of our customers are using Tcat to build APIs. Anypoint Platform combines Tcat’s ease of use with built-in management and support. Whatever you’re building and deploying on Tcat, Anypoint Platform gives you agility, reusability, and transparency. Give Anypoint Platform a try for 30 days and see what you think.
Once in a while I get questions about whether Apache Tomcat implements a way to include other files in server.xml, Tomcat’s main configuration file. The answer is that there is a way to do it, and that Tomcat didn’t have to implement a new feature for it to work. The way to do it is: XML entity includes.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.