- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Josh Durbin
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
All Blogs
CITYTECH Blogroll:
Adobe CQ 5.5 & JMX
Friday, March 16, 2012
Starting with CQ5.5, Adobe (Day) integrated one sorely missed functionality to the product, JMX. As with any J2EE server, JMX makes it easy to manage and monitor an application and services in real time. JMX allows for central management of managed beans or MBeans which act as wrapper for applications, components and resources. A standard MBean exposes attributes, properties and operations, which can be accessed for monitoring and invoked for certain conditions depending on underlying logic. It also helps when you don't need to restart the server to make a quick and essential change. With CQ taking prominence in today's digital media centric world, custom components are being built at a rapid pace to support and integrate several software products. Managing these custom components will become easy with JMX framework.
Puru Hemnani
Puru Hemnani has more than 10 years of experience in the IT industry....
Recent Posts
- Descriptive JMX Beans in AEM/CQ
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Javascript, This, and You.
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Google Analytics and AEM: No JavaScript? No Problem.
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6