rolandhuss

Pop	207.18
Vit	32.88

Jmx4Perl provides an alternate way of accessing Java JEE Server management interfaces that are based on JMX (Java Management Extensions). It is an agent-based approach where a small Web application deployed on the application server provides HTTP/JSON-based access to JMX MBeans registered within the application server. It is set up from a handful of Perl modules, which can be integrated seamlessly in your own programs. It also includes a Nagios plugin, check_jmx4perl, a jmx4perl command line tool for remote JMX queries and operations, and a readline-based JMX shell j4psh, with context sensitive command completion and syntax highlighting.

Pop	223.86
Vit	16.41

Jolokia is a fresh way of accessing JMX MBeans remotely. It is different from JSR-160 connectors, as it is an agent based approach that uses JSON over HTTP for its communication. It provides new features for JMX remoting: bulk requests allow for multiple JMX operations with a single remote server roundtrip, there is a fine-grained security mechanism for restricting JMX access on specific JMX operations, JSR-160 proxy mode, and history tracking, to name a few. Jolokia's origins are in jmx4perl. Client bindings in addition to Perl have already been added, and more are planned.

Pop	43.03
Vit	1.69

Osgish is a command line shell for OSGi. It is based on the Readline Library, Jmx4Perl, as the OSGi backend, and Aries JMX as the OSGi Management layer. It is different than other OSGi shells, as it is implemented in pure Perl and provides unique features like wildcard support, context-sensitive command line completion, syntax highlighting, bulk lifecycle operations, advanced query facilities, and remoting via HTTP. It uses jmx4perl and Aries JMX OSGi bundles for accessing the OSGi container remotely.

Pop	49.40
Vit	2.38

Schedule::Cron is a Perl module that provides a simple but complete cron-like scheduler. It can be used for periodically executing Perl subroutines. The philosophy behind Schedule::Cron is to call subroutines periodically from within one single Perl program instead of letting cron trigger several (possibly different) Perl scripts. Everything under one roof. Furthermore, Schedule::Cron provides a mechanism to create crontab entries dynamically, which isn't that easy with cron. It knows about all extensions (at least all extensions the author is aware of, i.e those of "Vixie" cron) for crontab entries like ranges including 'steps', specification of month and days of the week by name, or coexistence of lists and ranges in the same field. It even supports a bit more (like lists and ranges with symbolic names). It has existed since 1999 on CPAN and is successfully used in many projects.