This configuration uses the WebPublisher Studio Thick Client API to web-enable some or all functionality of a LAN based Omnis Studio enterprise application.
The application is written using Omnis Studio but is not delivered within a web browser - it is a complete desktop application with client side and server side business logic, multiple windowing, comprehensive data validation and all of the rich features you'd expect in a custom database application. Because it isn't browser based, the performance can be finely tuned so that transactions only return a small number of bytes - the content in the HTML interface is completely eliminated.
- This system allows staff to remotely process data directly into the backend system from any suitable web portal.
- Data security can be strictly enforced because WebPublisher Studio lets you encrypt transmissions between the Thick Client and the WebPublisher server.
- This makes it suitable for organisations sharing sensitive data between remote sites.
How it works
The existing Omnis Studio application operates on the LAN using the current multi-user business logic to arbitrate data entry on the enterprise network. WebPublisher Studio server operates as as a single multi-user instance and the web enabled application uses the Thick Client API (.wpx) to transact with the LAN database via the WebPublisher Studio Server.
Remote users now have access to the live database with the same privileges for modifying content as their LAN based counterparts.
Additionally all of the user interface for the LAN application can be preserved without having to write a remote interface using foreign tools.
And... it's all written in Omnis Studio.
We've implemented systems that allow users in different offices, cities and countries to share data with real-time performance, similar to working on a local area network.