If the selected application module type is a page module, you can associate a name with the page by entering a name in the Page Name field in the New WebSnap Application dialog box. At runtime, the instance of this module can be either kept in cache or removed from memory when the request has been serviced. Select either of the options from the Caching field. You can select more page module options by choosing the Page Options button.  

For information on adding application module components, see Specifying Application Module Components. 

The Application Module Page Options dialog is displayed and provides the following categories:

• Producer: The producer type for the page can be set to one of AdapterPageProducer, DataSetPageProducer, InetXPageProducer, PageProducer, or XSLPageProducer. If the selected page producer supports scripting, then use the Script Engine drop-down list to select the language used to script the page.
• HTML: When the selected producer uses an HTML template this group will be visible.
• XSL: When the selected producer uses an XSL template, such as TXSLPageProducer, this group will be visible.
• New File: Check New File if you want a template file to be created and managed as part of the unit. A managed template file appears in the Project Manager and has the same file name and location as the unit source file. Uncheck New File if you want to use the properties of the producer component (typically the HTMLDoc or HTMLFile property).
• Template: When New File is checked, choose the default content for the template file from the Template drop-down. The standard template displays the title of the application, the title of the page, and hyperlinks to published pages. The blank template creates a blank page.
• Page: Enter a page name and title for the page module. The page name is used to reference the page in an HTTP request or within the application's logic, whereas the title is the name that the end user will see when the page is displayed in a browser.
• Published: Check Published to allow the page to automatically respond to HTTP requests where the page name matches the pathinfo in the request message.
• Login Required: Check Login Required to require the user to log on before the page can be accessed.