ASP Design Thin Client Thick Client Peer to Peer Multi-Instance
Steps involved in developing WebPublisher Studio Active Server Pages

All WebPublisher Studio content is stored in the Plugin folder within the server cluster. Plugins contain a library used for writing Omnis code and a data file used to store all resources. Database content can be stored in an Omnis Data File located in the WebPublisher Studio Data folder, or in any other database repository that can be accessed using Omnis Studio middleware (eg. SQL Server, DB2 etc.). The steps in developing a thin application, such as a dynamic website, are as follows:

Step 1:
Decompose pages into Static and Dynamic content.

We recommend using a wireframe to design forms and page elements during the specification phase.

Step 2:
Declare variables for use when processing forms and returning active server pages from Macros.

The wireframe allows field lengths, formats and typical data to be modelled so you can specify static and dynamic content.

Step 3:
Create Macro Code Resources to manage business logic and populate server page response forms.

Each Macro is published as a URI and processes client requests by executing the Code Resources sequentially in the order assigned. A Code Resource is a mixture of HTML formatting and executable Omnis Studio methods delimited using the <%>...</%> tags.

WebPublisher Studio - Configuration Options

Step 4:
Add any final graphical elements and static content then publish active server pages using WebPublisher Studio Server.
You can test your application in the staging area you have created on your machine or network then move it to the production server when you're satisfied it's all working properly.

Check out some interactive examples of WebPublisher Studio Macros delivering active server pages on our Examples page.
To fully test the features of WebPublisher Studio you can download a free evaluation version from our Purchasing page.