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.
XINS is a technology used to define, create, and invoke remote APIs. XINS is specification-oriented. When API specifications are written (in XML), XINS will transform them to HTML-based documentation and Java code for both the client-side and the server-side. The communication is based on HTTP. XINS competes with the complex SOAP technology. Main design goals include simplicity, scalability, and testability. XINS is not only a specification technology, but also an application development framework. It offers transaction logging, unique log documentation, and active code generation.
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.
CI-Eye is a powerful continuous integration build radiator requiring no installation and almost no set-up. CI-Eye talks to many different CI servers through their REST APIs (so no plug-ins are required). Currently, support is offered for Hudson, Jenkins, and TeamCity. CI-Eye runs as a standalone Web application.
Orient Key/Value Server is based on the Document Database technology and is accessible as an embedded repository via Java APIs or via HTTP using a RESTful API. It uses a new algorithm called RB+Tree, derived from the Red-Black Tree to maintain tree balance, and from the B+Tree storing the links to records in pages to optimize memory consumption and loading time. Orient Key/Value Server scales out very well in a cluster with thousands of running machines: Orient will divide the load among all the nodes. Clustering, by default, works in auto-discovery mode: when a node starts, it attaches itself to the cluster if one is available. When a node goes down, the cluster automatically rebalances itself.
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.
jmxtrans is effectively the missing connector between JMX and whatever logging or graphing package that you can dream up. jmxtrans is very powerful tool that reads JSON configuration files specifying servers/ports and JMX domains/attributes and then outputs the data in whatever format you want via special "Writer" objects that you can code up yourself. It does this with a very efficient engine design that will scale to querying literally thousands of machines. The core engine is pretty solid and writers are included for cacti/rrdtool, graphite, and stdout.