Libra Framework

Libra applications are deployed and operated on central servers. The web technologies used in their development deliver the applications through a web browser to all workplaces of the enterprise, without any need of installation. The system is suited equally well to small work groups as well as large corporate environments with thousands of users, connected via the Intranet or the Internet.

The applications are not implemented in simple Java, but based on Java EE. So, in order to run them, a Java EE-compliant application server, that implements the complete Java EE stack, is required. In principle, the applications run on any certified Java EE server, for example JBoss (Open Source), IBM WebSphere, BEA Weblogic or SAP Netweaver (SAP Certified Integration since 2005).

The operation and licensing of the Java EE Servers lie in the responsibility of the customer. By default Libra ships its Java EE applications based on the open source Java EE servers JBoss and Tomcat, which may be operated without license costs. JBoss and Tomcat are suited for large-scale corporate deployments with thousands of users just as well as WebSphere or Weblogic.

Libra applications have a multi-layer architecture
All applications are executed using Session Beans on the central Java EE server. Database transactions in the application server are routed through Entity Beans. Session and Entity Beans use the same Java EE Server instance. The presentation layer is provided by the Libra Web Framework, which runs on a separate Tomcat web server instance.