iTP Active Transaction Pages (iTP ATP) Programmer's Guide

ATP Web Page and Script Structure

iTP Active Transaction Pages (iTP ATP) Programmer’s Guide—522292-002

3-2

Web Page Processing

Server-side includes also follow Netscape conventions. For example:

*

Script is not permitted within a meta tag (such as <meta http-equiv=”content-

type” content=text/html>) or in an #include statement. Otherwise,

fragments of script can appear anywhere, for example to define a file extension

dynamically or to modify the behavior of a client-side script.

Recursive includes are not checked, but are not allowed. The system loops until it

runs out of resources.

Include file is the only include tag supported by ATP.

Web Page Processing

ATP processes a page as follows:

1. Saves meta-tags.

2. Expands server-side includes.

3. Distinguishes active content (server-side scripts) from passive content (to be passed

unaltered to the Web browser).

4. Executes server-side scripts. Script output appears in the location occupied by the

script in the original .atp page. The script is effectively replaced by its output,

which can consist of nothing or any number of lines of output data obtained from

application servers.

The browser parses and presents the resulting stream of HTML, text, and possibly

client-side JavaScript.

Meta Tag Used for MultiByte Support

A new meta tag is now available to override the value of the

ATP_DISABLE_BACKQUOTE variable (for the pages that contain this meta tag). Your

application may have multiple backquote meta tags to enable or disable backquotes on

different sections of the same page.

Note. ATP does not provide a way to change HTTP headers dynamically in a script. To

change a header, use an HTML meta tag. For example, to generate plain text output, you

could use the following statement: