In addition to changing styles, you can also change the behavior of an application. This customization is based on defining .aspx (.jsp) pages that precede or succeed the basic listmodels and runmodel functionality (see chapter A typical run). These pages could also define frames in which particular information is shown.
As was discussed in chapter A typical run, there are three such "exit point" pages. If you place the following files in the root of the application-directory, they will override standard variants of ITP/OnLine.
You can use the exit points not only to define behavior, but also to define framesets. In the application configuration page you can then specify in what frame certain interaction should occur. For example, to have the folder and models opened in two frames in the same window, you could have the following modelselect.aspx (modelselect.jsp):
<HTML>
<HEAD>
<TITLE>ITP/OnLine Server Sample Application</TITLE>
</HEAD>
<FRAMESET cols="250,500" framespacing="0" scrolling="no">
<frame src="openfolders.jsp" name="folders" />
<frame src="empty.jsp" name="models"/>
</FRAMESET>
</HTML>
If the value "models" is configured as Model List Frame on the configuration page of the application, the list of models will now be shown in the right frame. The page openfolders.jsp will be discussed below.
The default exit point implementations use a number of predefined pages that you can call in your own exit points as well. You can also override these pages so that the default exit points use them instead. The predefined pages are:
The defaults for these pages can be found in the jsp subdirectory of the ITP/OnLine installation. When overriding them, they should be placed at the top level of the application directory.
In the aspx or jsp pages that you implement, it is possible to use various bits of functionality offered by ITP/OnLine. The APIs that are available to the customized pages are described in The ITP/OnLine Server customization APIs.