Publishing Pages, Page Sets, or the Application

See Also

When you publish a page, this results in a (new version of the) runtime XML file for this page, and in an ASP or JSP server page that is used runtime to have the USoft Page Engine call this XML file. The extension of the server page depends on the Server Page Type of the publication configuration against which the publication is done.

You can also publish a page set, or publish the entire application. This is equivalent, in terms of output, to publishing each individual page within the page set or application.

In the output environment (the runtime environment), page sets or the application cannot be recognized, only individual Pages. End users of Web Designer applications will typically be unaware of this type of application boundaries. Their view of what constitutes the application will most likely be determined by the URL used to access the runtime application, together with the functionality to which their First Menu Page Web gives them access.

If a development team makes use of more than one Web Designer application on top of the same USoft Definer data model, then it is advisable to have applications publish to distinct web server directories. This is achieved by making sure that Publication Configuration definitions within one application do not point to the same directory (directories) as Publication Configuration definitions within another application.