Business Case - Thick Client
This configuration is ideal for any organisation that needs to support remote users with real-time access to perform data entry.

Typical examples include Sales Representatives, Regional Branch Offices, Remote Point of Sale (POS) Outlets, Out Workers and Telecommuters. The entire application environment (ie. WebPublisher Studio Thick Client and the Omnis Studio Runtime) can be run from a memory stick providing maximum portability.

Description
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 objective of this system is to allow staff to remotely process data directly into the LAN system from any suitable web portal. Data security can be enforced because WebPublisher Studio lets you encrypt transmissions between the Thick Client and the WebPublisher Studio 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. It's all written in Omnis Studio. You can download an example of a Thick Client API from the Examples page.