Perfmon4j is a suite of performance monitoring tools that are intended to be used to diagnose performance bottlenecks and monitor throughput and response time in production Java applications. Its main features include servlet response time monitoring, detailed thread trace sampling, Java instrumentation that enables Package, Class, and Method monitoring without code modification, snapshot monitoring of system metrics including Garbage Collection, Memory Pools, etc., an API for applying additional monitoring points via method annotations or in-line timers, and support for dynamically enabling monitors in running applications.
SlimWeb aims to replace Struts or JSF in your J2EE application, but is closer to Rails or TurboGears in its heavy use of convention-over-configuration, simplicity, and power. It aims to reduce (and most of the time completely eliminate) all boilerplate code, XML configuration files, and even deployment times.
iLAP (Laboratory data management, Analysis, and Protocol development) is a workflow-driven information management system specifically designed to create and manage experimental protocols and to analyze and share laboratory data. The system combines experimental protocol development, wizard-based data acquisition, and high-throughput data analysis into a single, integrated system.
With the Cibet framework, it is very easy to add various control mechanisms into a JPA and/or EJB-based Java application. The actual version includes control schemes like Archiving (manipulation of domain objects; data and execution of business processes are archived). From the archived state, domain objects can be reconstructed and business processes can be re-invoked with the same parameters at any time. The archive entries are secured against manipulation to make them audit-proof and revision safe. Four-eyes principle: this scheme is an example of a dual control mechanism: A user wants to perform some critical data manipulation or business process. With an applied dual control mechanism, the action is not executed in the production system directly, but stored and postponed. A second user must check the data and the action and can approve or decline. Only when the second user approves, the data manipulation or business process is executed in the production system; otherwise it is discarded. An even stricter example for a dual control mechanism is the six-eyes principle. In this case, a third user must approve a data manipulation or business process before it will become productive.