BibSonomy ::  tag ::

order by ( date | folkrank )

OpenLexicon is an open-source business rules and process management tool that rapidly develops applications for transaction and process-based applications. OpenLexicon is known for providing high performance solutions and has been used in a number of enterprise-level applications. You can read about these here . You can use either product separately or in concert. There are two main components of OpenLexicon: the metadata repository and the business rules engine. Major components of OpenLexicon are released as open source software under the OpenLexicon OpenSource License. A good overview of the business rules approach is available here .OpenLexicon has a Wizard that is a web-form based collaborative tool for building business rules and business use cases. For a brief overview of the wizard, look at this link . We have designed the Wizard for non-developers and analysts with light technical skills. It features a richer experience for the users on the web, traditionally only offered by thick-client UIs.  The collaboration team assembles groups of business rules into a business use case and published in a metadata file or the database. OpenLexicon provides solid support for web services. You can read about the OpenLexicon WSDL here . There is also an eclipse plug-in for web services here . You create complex application behavior with OpenLexicon’s process management. OpenLexicon can build an application reads data from a file, performs reference data lookups, validates the entire object, and then stores it in a database table. You can read about this here . Plus, you can build the application in the Wizard while writing no code! OpenLexicon also supports web services. A simple architecture diagram for OpenLexicon is included here .

A context adaptive system typically enables the user to maintain a certain application (in different forms) while roaming between different wireless access technologies, locations, devices and even simultaneously executing everyday tasks like meetings, driving a car etc. For example a context adaptive and hence ubiquitous navigation system would offer navigation support in the situations at home, indoor, outdoor, and in car. This involves making the navigation functionality available for different availability of output devices, input devices and location sensors as well as adapting the user interaction operability to the current speed, noise or operator handicaps while keeping in mind the overall applicability depending on the user preferences, his knowledge, current task etc.[1]

DRBD® refers to block devices designed as a building block to form high availability (HA) clusters. This is done by mirroring a whole block device via an assigned network. DRBD can be understood as network based raid-1. In the illustration above, the two orange boxes represent two servers that form an HA cluster. The boxes contain the usual components of a Linux™ kernel: file system, buffer cache, disk scheduler, disk drivers, TCP/IP stack and network interface card (NIC) driver. The black arrows illustrate the flow of data between these components. The orange arrows show the flow of data, as DRBD mirrors the data of a high availably service from the active node of the HA cluster to the standby node of the HA cluster.

The RNA project deals in a very practical way with methods, tools and techniques for building dynamic knowledge systems. In these systems a key role is played by reference networks, sets of reference structures (like thesauri, taxonomies, etc.) and related content metadata. The project is financed by the Dutch Ministry of Economic Affairs under the auspices of the Ministry of Education, Culture and Science. It is a combined effort of a group of innovative small companies, vanguard institutions in the cultural heritage field and outstanding, internationally acclaimed academics.

SwitchPipe is a proof of concept "Web application server" or, more accurately, a Web application process manager and request proxy. Backend Web applications are loaded into their own processes, making SwitchPipe language agnostic. HTTP requests are proxied at the TCP level using information extracted from the headers to establish which backend application is being demanded.