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.
Icwri is a lightweight, very simple, service-oriented Java built-in script. It can help Java developers build some application interfaces in a service-oriented style. It can also help non-technical people join the development team to write their own application scripts to enforce business rules and decisions. Icwri service providers and consumers can be either Icwri scripts or Java classes. An Icwri script can run all alone, but the primary purpose of Icwri script is to have an assistant language of Java. It can run on any system with JDK/JRE 1.5 or above installed. It does not support Java SE 6 Script Engine because of the service-oriented design and the requirement to support Java SE 1.5 users.