KeyBox is a Web-based SSH console for executing commands and managing multiple systems simultaneously. It allows you to share terminal commands and upload files to all your systems. Once the sessions have been opened you can select a single system or any combination on which to run your commands. Also, additional system administrators can be added and their terminal sessions and history can be audited.
Moqui Framework is a seamlessly integrated, enterprise-ready framework for building enterprise automation applications based on Java. It includes tools for database interaction (relational, graph, document), logic in local and Web services, Web and other UIs with screens and forms, security, file/resource access, scripts, templates, localization, caching, logging, searching, business rules, workflow, multi-tenancy, and integration.
The NABUCCO Framework is the foundation for the NABUCCO product line. A modern MDA approach provides a basis for qualitatively high value, stable software with multi-client capabilities. Components, which are fully reusable, are thereby developed through the original MDA approach. The development of customized applications is supported in the same way as the development of the company's own products, such as Skill Management. Customized solutions can benefit from NABUCCO on many levels; use of the MDA approach for a customized MDA process with separate DSL; use of the NABUCCO DSL / generator as a software factory; development of new components for specific industries or customers; customizing existing components without coding; and expanding existing components to create a customized solution.
The Imixs Workflow project offers a Java based BPM framework to build workflow management systems (WFMS) in a fast and easy way. The project provides different components and sub-projects that contribute to the development of workflow solutions in any kind of Java or Java EE application. The goal of this project is to offer an easy-to-use Java based technology with a focus on human based workflow. This means that the Imixs Workflow is typically applied to human-to-human workflow applications. But it can also be used for technical business process management solutions (BPM). The Imixs JEE Workflow is a full featured Workflow Management System (WFMS) based on the JEE specification. The project extends the Imixs Workflow API project to fulfill the requirements to a scalable, transactional, robust and simple deployable Java EE Workflow System. The Project provides different service components (EJBs) to be used in any kind of BPM application.
AppDynamics an application performance management solution for mission-critical Java applications. It can organize user requests and business transactions, monitor business transaction health, identify and diagnose slow requests, identify and diagnose errors, and drill down. It is built from the ground up for highly distributed service-oriented environments. It has fast root cause diagnostics at the method/class level, but creates no more than 2% overhead, even in high-volume production deployments. It can not only manage applications, but dynamically scale them in cloud and virtual environments.
Endeavour Agile ALM is a rich Web-based solution to manage the creation of large-scale enterprise systems in an iterative and incremental agile development process. It features support for Use Case management, iterations, project plan, change requests, defect tracking, test cases, tasks, document management, and many other process artifacts.
Spring ME is a version of ME that not only runs on your cell phone, but also on any other Java platform not supporting reflection. It is to Java ME what Spring is to Java SE and Java EE, which is indicated by the name. However, the "ME" (Micro Edition) suffix not only refers to the platform it supports. It also refers to the size of the runtime, which is pretty minimal. In fact, it's pretty much non-existent, and therefore ideal for situations in which you cannot afford the sheer size of the traditional Spring runtime.
The goal of dzo is to treat application database objects the same way the application's source code is treated, with respect to development, revision control, and deployment. Dzo uses a text file that contains native create statements for all database objects and compares them against the actual database-schema. As a result, dzo creates the SQL statements needed to update the database schema (or you can let dzo execute the SQL statements directly). If your application lives in a Tomcat or Java EE application server, dzo has a servlet that controls the deployment process, inspects and executes the necessary database changes, and finally deploys the application. Dzo currently works with HSQLDB, MySQL, Oracle, PostgreSQL, and SQL Server (more to come).