Open 4GL WebServices is a wizard/procedure and a framework that makes it easy to publish PROGRESS procedures as Web services by generating the WSDL and WS code. It does not require the developer to learn XML or the framework itself and provides many choices for deploying the code.
The DBacesslayer (or DBSlayer for short) is a lightweight database abstraction layer suitable for high-load Web sites where you need the scalable advantages of connection pooling. DBSlayer talks to clients via JSON over HTTP, meaning it's simple to monitor and can swiftly interoperate with any Web framework you choose.
JCR Shell is a shell interface to manage JCR repositories like Apache Jackrabbit, Hippo CMS 7, and other JCR 1.0 (JSR 170) capable repositories. It uses RMI to communicate with the server. It features tab completion on names, types, and properties, the ability to import and export XML, a JCR diff tool, queries, reference lookups, and namespace management.
WaldScan is a PHP class which recursively scans a given directory for a list of selected file types. It has many uses for any Web page which serves files over HTTP/HTTPS, for a CLI program which does batch processing of files, or in cron jobs for caching file data for faster access.
Elvyx is a tool designed to monitor and profile JDBC activity. This JDBC profiler has a wrapper that intercepts access to the database and sends this information to the elvyx server. The server receives the information, stores the data into a database, and serves this information to the client. The client shows SQL statements, bound SQL statements, elapsed time, elapsed time preparing the statements, and more.
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.