Top Stories by Graham P. Harrison
AJAX and JMX are at opposite ends of the Systems Management stack. However,
the emerging ubiquity of the AJAX model for rich browser clients has obscured
the benefits the model provides in the architectural space for enhancing
support patterns within the problem resolution pipeline.
This article elaborates on an architectural benefit of AJAX that lets the
management state be 'broadcast' to a browser-enabled user base without
waiting for a page refresh.
This architecture is an extension of a general pattern for logging JMX events
and properties to a server-side log file; this variation logs or 'broadcasts'
management information to the (AJAX-enabled) user base.
Emphasis is placed on the AJAX request/response model and the painting of
management data to the page, together with the beautiful JMX notification
framework, all neatly integrated in the middle with an instrum... (more)
AJAX and JMX are at opposite ends of the Systems Management stack. However,
the emerging ubiquity of the AJAX model for rich browser clients has obscured
the benefits the model provides in the architectural space for enhancing
support patterns within the problem resolution pipeline.
This article elaborates on an architectural benefit of AJAX that lets the
management state be 'broadcast' to a browser-enabled user base without
waiting for a page refresh.
This architecture is an extension of a general pattern for logging JMX events
and properties to a server-side log file; this vari... (more)
It is possible to create a very attractive look-and-feel prototype of a
Calendar-based browser application in JavaScript, but to compete with
tough-minded mainframe legacy systems such as MEMO requires a highly
functional and scalable working prototype to justify the continued investment
and potential encapsulation of a large mainframe system.
After it was suggested that an existing MEMO-based system was to be
superceded, an opportunity arose to port some of the legacy application
functionality to the new Intranet and browser medium, hopefully gaining a
more attractive interface... (more)
It is not easy to query the contents of a database without proprietary front
end tools or a database-aware IDE. A database-aware toolkit should be able to
connect to and work with a variety of databases (local and remote,
application and corporate) without a shift in how we view the contents of
different databases.
Java and JDBC allow the builder to abstract the viewing of the data from the
implementation of the database and database queries that yield the data for
viewing. A number of IDEs allow the builder to query the contents of a
database as part of the database component i... (more)