This configuration uses the WebPublisher Studio server to deliver Active Web Pages to an Ultra Thin Client (in this case a web browser).
This allows the leveraging of data from the enterprise database to users on the internet.
You can think of this installation as doing .asp or .php for Omnis Studio.
We use the suffix convention ".wpm" for the URI (eg. my-page.wpm) but you can use any suffix you like for Macro URIs.
Active Web Page URLs are requested using standard HTTP CGI form handlers (Name Value Pair) and programmed using the Development Client.
GET and POST methods are supported using standard HTML forms
(eg. my-page.wpm?value1=value1&value2=value2 etc.).
Web-based login sessions are handled by the Session Management tools provided in the API.
Users can log into an account, submit forms, view and interact with web content, search database records etc.
In this case example the database is being managed using a WebPublisher Studio Thick Client application (see the Thick Client case study for more information) although data can be managed using any other database tools you want to use.