Analysis

Both runs were started by opening a url with the following format:

http://[machine]:[port]/itp/app/[application]/modelselect.aspx

(http://[machine]:[port]/itp/app/[application]/modelselect.jsp),

where [machine]:[port] refers to the web site where ITP/OnLine has been installed and [application] identifies the "Application" to be used. An application identifies a set of resources (such as configuration settings, web pages, cascading stylesheets) that are relevant to the configuration and customization of OnLine. Browsing to different applications results in the use of different resources and therefore in different look-and-feel and behavior.

Browsing to this url resulted in a list of models. Clicking on a model opened another url of the form:

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 model to be run. This initiated the actual model run, possibly after some additional pages. During the model run a number of forms were presented to the user, after which a url

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

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

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

This may be depicted as follows:

The modelselect, modelbegin and modelend pages are the specific "glue" between the generic ITP/OnLine Server functionality offered by listmodels and runmodel.

Modelselect, modelbegin and modelend are part of the resources which are part of an application. 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 may best be 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.