Analysis

Both runs were started by opening a URL in a following format:

http://[machine]:[port]/itp/app/[application]/modelselect.aspx or http://[machine]:[port]/itp/app/[application]/modelselect.aspx?letterbook=[letterbook] or (http://[machine]:[port]/itp/app/[application]/modelselect.jsp or http://[machine]:[port]/itp/app/[application]/modelselect.jsp?letterbook=[letterbook]),

where:

• [machine]:[port] refers to the web site with installed KCM ComposerUI

• [application] identifies the usage of "Application"

• [letterbook] indicates the usage of the Letterbook entry point

An application identifies a set of resources, that are relevant to the configuration and customization of OnLine, such as configuration settings, web pages and cascading stylesheets. Browsing to different applications results in the use of different resources. Therefore, in different appearance and behavior.

Browsing to this URL resulted in a list of Master Templates. When the user clicked any Master Template another URL of the form was opened:

http://[machine]:[port]/itp/app/[application]/modelbegin.aspx?[querystring]

(http://[machine]:[port]/itp/app/[application]/modelbegin.jsp?[querystring]),

where [querystring] contained some information about the Master Template to be run. This initiated the actual Master Template run, possibly after some additional pages. During the Master Template run a number of forms were presented to the user, after which a URL was opened

http://[machine]:[port]/itp/app/[application]/modelend.aspx?[querystring]

(http://[machine]:[port]/itp/app/[application]/modelend.jsp?[querystring])

The [querystring] contained some additional information about the document that was produced, allowing the modelend page to open the result document.

The process flow described in the previous paragraphs is described here:

The modelselect, modelbegin and modelend pages are the specific component between the generic KCM ComposerUI functionality offered by listmodels and runmodel.

Modelselect, modelbegin and modelend are part of the application resources. Typically, they build up framesets, show additional pages (like the page in sample, asking for document format and preview), open result documents (modelend) and support application integration.

Both listmodels and runmodel are considered as separate generic "calls" embedded in a specific preceding and succeeding page. In many cases the runmodel functionality will be used by directly opening the modelbegin page with a number of query string parameters.