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.
TagEventor is a project to enable radically simple computer usage by creating physical-object-based user interfaces. It does this using commercially available (and relatively cheap), standardized RFID technology in the form of small, simple USB connected contacted card/tag readers and small, cheap tags. The project was started based on products available from the "touchatag" company, which has clients for Windows and Mac, and run their own Web service to enable many interesting Web-based applications. However, no simple, lightweight Linux client was available, and the Web focus meant that some client-focused functionality was not possible. The software is currently a daemon that monitors the presence of one or more RFID tags on a connected reader and generates "system events" when tags are placed on it or removed from it.
When a user inputs a hostname or an IP address, MQ Port Scan will scan a range of ports looking for a queue manager's MCA, using the standard (system default) channel names, in order to make a successful connection. It is very easy to use. It has the ability to search across a range of IP addresses and scan the port range for each IP address. Any time MQ Port Scan successfully connects to a queue manager, the information is written to a CSV file. The output will include the queue manager name, MQ version, channel name, hostname or an IP address, and port number.
Conary is a distributed software management system for Linux distributions. It replaces traditional package management solutions (such as RPM and dpkg) with one designed to enable loose collaboration across the Internet. It enables sets of distributed and loosely connected repositories to define the components which are installed on a Linux system. Rather than having a full distribution come from a single vendor, it allows administrators and developers to branch a distribution, keeping the pieces which fit their environment while grabbing components from other repositories across the Internet.
Associations Indexing Service (AIS) was originally done as an extension of human memory for tagging (storing under personal keywords and associations) resources, URIs, bookmarks, and memos (for fast access to the information in future) by using the same keywords or queries, similar to popular search engines. It can be seen as a local search engine, used as an automatic indexer of big file hierarchies (e.g. personal archives or files repositories). It is based on Lucene, so the application will remain very fast with any size index.
Butterfly Web UI is a component based Java Web application framework. Like the rest of the Butterfly Components, Butterfly Web UI is extremely small and very flexible. Butterfly Web UI uses Butterfly Container internally, a state of the art dependency injection container. Using Butterfly Web UI, it is easy both to generate HTML for a Web browser or XML or JSON for a RIA frontend (Flex, JavaFX, Silverlight) or AJAX frontend. You also can easily create HTML layout templates that are reused throughout your Web application, so you don't have the layout hardcoded into every page. You can easily mix RIA and non-RIA Web application technology in the same Web application.
jniThreadCPUUsage is a Java library to get the amount of user and system CPU time used per thread. This is done via JNI, which calls getrusage() on the system. getrusage() is only available on Linux 2.6.26 or later and Solaris. One useful application of this is measuring the amount of CPU time used for a servlet request. getrusage() CPU time reporting is better than using the real time clock because it measures actual CPU time used and disregards times when the thread is idle or waiting (such as when it is waiting for network I/O).