Introducing Tcat Server 6 R4

Reading Time: 6 minutes

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, which represents the result of this feedback and is the most comprehensive product in the market for organizations using Tomcat in production.

This release includes:

  • Global dashboards: Our customers have been telling us that while Tcat Server provides a single pane of glass for managing their Tomcat instances, they wanted to see a summary of all of their instances, the status of their applications as well as actionable information, all without drilling into each server instance. Global dashboards address this by providing a view of your entire Tomcat environment, web applications, status of current deployments and potential issues on one single screen. Similarly, the ability to view important metrics on a per-server basis is now also possible via server dashboards. Many of our customers’ applications expose data via JMX metrics, and being able to graph them to see the trends is now possible via these server dashboards.
Continue reading

Mule Speaks Java: Towards a programmatic configuration of Mule

Reading Time: 3 minutes

True to our goal of simplifying the configuration of Mule, we will be adding the capacity to programmatically configure Mule 3 in the coming releases.

With configuration patterns aiming at reducing the amount of XML configuration and a new IDE in the works for graphically configuring Mule, the third angle we wanted to take on simplification was the creation of an API fluent enough that it becomes possible to configure Mule with your favorite JVM language.

If you’ve peeked into Mule 3’s source code, you may have noticed that this effort is already on-going. Indeed, each of the newly introduced configuration patterns is backed by a builder class that is used to instantiate it. Read on for a quick demonstration of how this can be used…

Continue reading

Pattern-Based Configuration: Hello Validator!

Reading Time: 6 minutes

The pattern-based configuration series continues! After a first set of fairly generic patterns, this new addition will demonstrate how highly specialized patterns can provide value too.

When processing messages, a certain format is always assumed to have been respected so that the required data can be retrieved. It is possible and oftentimes desirable to be very liberal with the data representation used by incoming messages: as long as you can find the needed pieces of information, the rest doesn’t matter.

But sometimes, a strict up-front validation of incoming messages is needed. This is that kind of scenarios that the Validator configuration pattern addresses.

Continue reading

Pattern-Based Configuration: Hello Bridge!

Reading Time: 7 minutes

Web Service Proxy was the last configuration pattern presented in this blog. Time for a new one!

Connecting systems together is one of the most essential task of integration. Mule ESB offers the necessary building blocks for achieving such connections. One of these building blocks allows establishing bridges between message sources and destinations. Known as the messaging bridge pattern, this building block is available in Mule 3 as the newly introduced Bridge configuration element.

So we’ve built a bridge: it’s time we get over it!

Continue reading