It's likely you've been working with WebSphere MQ (WMQ) for years developing,
deploying, monitoring, or all of the above. It's also likely that by now you
have assembled a tool bag full of items to support your implementations and
ongoing operations. And you've no doubt become accustomed to dealing with
problems within the MQ domain. But what if you could see more of the
transactional journey on either side of MQ? Organizations doing this are
finding new ways to improve levels of service and avoid costly upgrades.
Initially, just seeing the touch points, you know - the "puts" and the "gets"
along with MQ administration probably seemed entirely sufficient in order
to manage WMQ. A common assumption was that as long as we saw messages coming
and going, things were okay. Analogous to Archimedes' principle of water
displacement, the health of MQ or any other middleware... (more)
Ultimately, CIOs decide how best to manage their IT infrastructures to
guarantee a quality of service to end users while staying within the
allocated budget. Using a shared services approach for APM fits best in line
with these goals. This approach can provide quality of service to all of the
application owners and drastically reduce the cost.
As a general rule, corporations have multiple groups of application owners.
The common practice is for each application owner to decide the APM solution
required for their particular need at the time. To research the solution, one
or more ... (more)