Want to improve your Kafka distribution's cost and performance? Download our free eBook
White Paper

End-to-End Observability of Middleware-Centric Applications Including IBM, Solace, and TIBCO

Background

In the beginning, there was darkness…

Ok, I’m being a bit overly dramatic. What was happening at a really big global bank in New York with almost U.S. $2 trillion in total assets — let’s call it MegaBank — was a serious lack of control.

Let me paint the scene. The IT team was getting along pretty well. Among other development and operations activities, they were successfully monitoring and managing their IBM MQ middleware family of products as well as a homegrown messaging solution. All was well with bank applications utilizing IBM MQ and its associated tools.

End-to-End Observability of Middleware-Centric Applications Including IBM, Solace, and TIBCO

Table of Contents

Introduction:

Background

Rationale for choosing Nastel to make their business lives simpler, restore control over a complex IT environment, and help safeguard the bank’s reputation with its customers.

Why a unified monitoring and control facility was so important to the IT team, and the role DataPower and Solace messaging appliances would play in helping integrate two different infrastructures
Taking the Pulse of Solace
Measuring DataPower

Capabilities that help achieve a unified middleware monitoring capability in the wake of a bank acquisition
The Backstory on MegaBank’s TIBCO EMS Monitoring Solution
Lifting the Hood on MegaBank’s TIBCO Rendezvous Monitoring Solution

Messaging Middleware and the Importance of Message Tracking
Benefits from Message Tracking Capability

Performance and scaling for the largest and most demanding of environments
Horizontal Scalability
Vertical Scalability
Transactional Metrics
Input Speed
Rules Processing Speed
High Availability

Conclusion: The Nastel Integration Infrastructure Management Platform Is a Powerful Monitoring Solution for Large Enterprises

Mega-Banks

“Unfortunately, MegaBank’s home-grown tools couldn’t handle the complexity of the new technology environment. Something better was needed to help maintain improved productivity, reduce MTTR (mean time to repair) for problems, and keep costs associated with problem resolution at acceptable levels.”