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,
MuleSoft will be at Oracle OpenWorld at booth #1833 (Moscone South) again this year. Come join us to experience firsthand the simplicity of Tcat Server and how it makes running Tomcat in production painless. We will also preview exciting new features of Tcat Server including dashboards, monitoring, alerting and fine-grained security permissions.
Tcat Server remains the most intuitive and easy to use product for enterprise Tomcat users. In the most recent release, we made Tcat Server even easier to try. Since we launched the product several months ago, downloads for Tcat Server have been increasing exponentially, but we wanted to find a way to reach yet more users that will benefit from using Tcat Server.
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.
We released Tcat Server 6 R3 today. This release packs features that were directly a result of customer feedback. Here are some of the highlights:
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.
Last week, we did a webinar with Terracotta on scaling and managing your web applications running on Tomcat. During the webinar, I did a short demo that showed a Terracotta profile, which makes it super easy to setup the environment required for web applications that use HTTP session clustering using Terracotta.
I previously blogged about how to create a server profile and apply it to servers here. In this case,
Linux has become the platform of choice for many enterprises and has led the move towards reducing costs and improving effectiveness by using Open Source solutions. Our friends at Canonical are leading the charge in providing easy to use, compelling solution in Ubuntu.
Apache Tomcat is the right sized application server for web applications. It does not have the bloat and complexity of Java EE application server and continues to be light weight and efficient.
While Tomcat provides basic deployment capabilities, configuring Apache Tomcat instance for applications is a manual, error prone and repetitive process. When we launched Tcat Server, our goal was to make it extremely easy to use Tomcat in enterprises.
