A Content Server Request Handler Example - Part 2 - The Architecture

Care for a practical example in Content Server applications? Here this is the ( The example) of a Categories Search, purely based on the database, not on the normal Content Server Search Server.

This is path 2 - the arcitectural diagram.

The Core: The Request Handler

To get the basic idea, refer my Article on LinkedIn WTF is a Request Handler in oScript?

The request handler is a pure construct of the Legacy GUI, it cannot be compared to the smartUI GUI constructs of REST/Javascript

To recap, the video for the example video is here in my LinkedIn Article A Content Server Request Handler Example - Part 1 - the Example

The Architecture

How is this thing constructed?

First, a new module is needed. Therefore, the Opentext development environment CSIDE must be installed and configured. See my LinkedIn Article The Basics - Installing CSIDE in the Content Server

Then a new module must be initialized and installed in the Content Server. See my LinkedIn Article OScript Modules on this topic.

And now: How dows it work?

We have two phases:

Data Aquisition Phase

The Data Aquition Phase collects all data for our search.

Here, we list all categories (readable for our id) and collect the seachphrase. With the weblingo file rm-search.html, all data is collected.

The categories are listed in a standard html selectbox to keep the example easy.

The searchphrase follows the Like-SQL syntax and covers date, text and number attributes.

The Execute and Display Phase

Here, we'll need a second Request Handler, fired from the First and executing the search.

Only Business Workspaces are here under the Category Event.

The weblingo file searchresults.html is used to display the search results and uses the browser to deliver the results as Print using the browsers print command and downloading the results as Excel comma separated spreadsheet.

The Module

This will be the final module