CloverETL is Java-based tool/framework for data integration and creation of data transformations. It is component based and follows the concept of transformation graphs which consist of individual nodes/components performing simple (or complex) operations on data. Any transformation can be defined as a set of interconnected nodes through which data flows. CloverETL can be used as a standalone application or be embedded into a larger project.
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.
Ruote is a workflow engine. It's a runtime for long running business processes. Processes are explicitly defined and may be explicitly handled (start, pause, cancel, update). A process is started by handing a business process definition to the engine. A process definition is expressed in ruote’s own process definition language, which comes in three flavours: XML, a Ruby DSL, and Radial. A process definition describes the flow of work among participants. A ruote engine can simultaneously handle multiple process instances, created from one or more different process definitions. A process instance can be modified on the fly.
Dapper, or "Distributed and Parallel Program Execution Runtime", is a tool for taming the complexities of developing for large-scale cloud and grid computing, enabling the user to create distributed computations from the essentials: the code that will execute, along with a dataflow graph description. It supports rich execution semantics, carefree deployment, a robust control protocol, modification of the dataflow graph at runtime, and an intuitive user interface.
Sluice is a workflow engine Jabber component. Its goal is to allow users to create and configure an automated workflow or business process with ease. The clients should be very simple with all the work being done on the server/component end. The main component and modules are done in Perl. The Web client is done in PHP.
TaskForest is a simple but expressive job scheduler that allows you to chain jobs and tasks and to create time dependencies. It uses plain-text configuration files to specify task dependencies. It comes with a built-in RESTful Web service. It was originally designed for a single machine, but support for multiple machines is planned.
Jitterbit is an integration tool for designing, configuring, testing, and deploying integration solutions. It supports many document types and most standards-based protocols, including XML, Web Services, popular databases, text files, FTP, HTTP, and others. The integration server runs on both Windows and Linux and is configured using a Java-based user interface that is designed to make integration quick, easy, and intuitive to complete. With the UI, users can define their integration operations from start to finish: adding source and target systems, using drag-and-drop mapping to transform data, setting schedules, creating success/failure events, and tracking all of their deployed integration operations.
Releaser is a set of scripts to automate and manage the tasks related to software package releases. It is designed to be modular and to make it easy to both select a particular set of actions associated with releases of a particular project (such as changelog generation, uploading of tarballs, posting announcements to mailing lists), and create new actions that integrate seamlessly into the process. Its status is still somewhat experimental, but the most basic functionality is there.