Instant ASP Logo


The Remote Console Applet: Application Settings

You can accomplish the following tasks using the Remote Console Applet Application Settings:

Accessing Application Settings

  1. To access Instant ASP Application Settings, click the Application Settings button in the Remote Console Applet.
  2. Application Root is selected by default in the left-hand pane (figure 1):

    figure 1
    app.gif (4111 bytes)
Creating a New Application
  1. Right-click the Application Root branch in the left-hand pane of the Remote Console Applet.
  2. From the pop-up menu, choose New|Application (figure 2):

    figure 2
    app1.gif (4894 bytes)


  3. The Welcome to the New Application Wizard launches and here you can enter the name and the fully qualified path to the new application (figure3):

    figure 3
    app4.gif (3489 bytes)
  4. After the application is created, the global server variables in the global.asa under that directory (Path to the application) will be loaded alone with the application.

Configuring the Properties of a Single Application

  1. To configure a single application, first click the + adjacent Application Root. A list of existing applications is displayed. Right-click on the application you would like to configure (figure 4):

    figure 4
    app6.gif (6467 bytes)

  2. Choose the Delete command to delete the selected application from the Application Root.
  3. Choose the Refresh command to reload the application list.
  4. Choose the Properties command to open the Application Setting window (figure 5):
     
    figure 5
    app5.gif (2333 bytes)


  5. Click the Configuration button to open the Application Configuration window (refer to Configuring Application Root Properties for specific details on setting the options in the Application Configuration window).

Configuring Application Root Properties

To make global changes to the configurations for all of your ASP applications, you can modify the properties of the Application Root.

NOTE: If you change a property of a single application and then change the same property from the Application Root, the Inheritance Overrides dialog pops up and asks you for which applications you wish to make the change. You can click Select All to select all of the available applications or you can select individual applications. Click the OK button to apply the changes or the Cancel button to return to the Application Configuration window (figure 6).

figure 6
app7.gif (3825 bytes)

  1. Right-click the Application Root branch in the left-hand panel of the Remote Console Applet.

Note: By default, the Application Root's name is "root" and its local path is mapped to your web server's documentation root path.

  1. From the pop-up menu, choose Properties (figure 7):

    figure 7


  2. A dialog box is displayed which contains 5 tabs: App Options, App Debugging, App Security, App Tuning, and App Mapping (figure 8):

    figure 8
    app3.gif (3155 bytes)

    The App Options tab lets you specify application options described in the following table:

    Control

    Description

    Enable Session State When this check box is selected, session state is enabled. When session state is enabled, the Session timeout and the Maximum sessions edit boxes are enabled and you can specify numeric values for both.
    Enable Buffering When Enable Buffering is enabled, output to the browser is buffered. When this option is enabled, all output generated by an ASP program is collected before it is sent to the browser. When this check box is cleared, output is returned to the browser as the page is processed. Buffering output enables you to set HTTP headers from anywhere in an ASP script.
    Enable Parent Paths When Enable Parent Paths is enabled, ASP scripts can use relative paths to the parent directory of the current directory (i.e. paths using the .. syntax). If you enable this option, do not allow execute access to the parent directories, otherwise a script could attempt to run an unauthorized program in a parent directory.
    Default ASP Language You can choose the primary script language used in your Active Server pages from this drop down list box. Instant ASP comes with two ActiveX script engines: Microsoft Visual Basic Scripting Edition (VBScript) and Microsoft JScript (jscript). The initial default is vbscript.
    ASP Script Timeout Specifies the length of time Instant ASP will allow a script to run. If the script does not finish running by the end of the timeout period, Instant ASP stops the script and writes an event to the event log. You can set the timeout period to a value between 1 and 2147483647.
    Pooling Size

    This control specifies the number of ASP applications which will be stored on server after finishing execution. The maximum is 50.

     

  3. When you have finished, click the Apply button to make your changes take effect.

  4. The App Engine tab lets you set the method of executing asp files on your server. The default method is Interpreter (Figure 9).

    Figure 9

    Note: App Engine setting is for Instant ASP Enterprise version ONLY!

    When you enable the Interpreter option, the code contained in asp file is compiled and executed each time the page is requested. This is the normal way. Depending on the tasks being performed by the code, the amount of code being executed and the number of current users on the server, the performance of this interpreted code can be significantly impacted. 

    The Pre-Compiler makes iASP engine run on the server side and compile your asp file to Java Servlet class file before execution. When this process is done, you can run Java Servlet class directly on your server instead of compiling and executing the asp file. It is a efficient and fast way of executing asp files, the same asp file that is requested frequently doesn't need to be compiled and executed each time the page is requested. 

    When you enable the Pre-Compiler Option, its settings panel will be shown below the options (figure 10):

    Figure 10

    In Update Settings, there are 2 options: Dynamic Update and Static Update. The difference is Dynamic Update checks the asp file to see if there is any change each time you make a request while Static Update does not check at all. If it does not stay the same, Pre-Compiler will re-do the compiling process.

    In ASP Settings, there are 2 options: ASP to Java and ASP to JSP. If you choose ASP to Java, it will compile your asp file to Java Servlet class file. And if you choose ASP to JSP, it will compile your asp file to JSP(Java Server Page) class file. 

    Before you save the changes, choose a path name to save the Java Servlet or JSP class file generated by Pre-Compiler. By default, the path is \[iasp home]\servlets\. You can also specify one yourself. Note: This path needs to be included into your classpath environment variables, and should be writable to save those class files generated by Pre-Compiler. Save the changes and restart the Proxy Server to take effect.

    There is another way you can make the changes. Set the rules.properties file (under the path \[iasp home]\properties\) to:
    *.asp=IspServlet
    *.ASP=IspServlet
    *.iasp=IspServlet

    Note: These settings at Application level overrides the settings of Application Root level. Scripts which do not belong to any application have these settings of Application Root level.

  5. When you have finished, click the Apply button to make your changes take effect.

  6. Next, click the App Security tab to display the application security options (figure 11):

    figure 11

    The App Security tab lets you specify application options described in the following table:

    Control

    Description

    Unrestricted Access When the Unrestricted Access Check Box is enabled, it allows all ASP pages and applications to have all accesses/permissions.  
    Allow execution to all scripts When the Allow execution to all scripts Check box is enabled, it grants execution to unregistered scripts. Otherwise, it denies.
    Execution of Subprocess Allows executing sub-process. Apply permission check for Execution in a script method if this method launches a sub-process.
    Database Access Allows access to database.
    File Write Allows writing any file in the local file system at specified directories.
    List of directories (File Write) List all directories that allow to write any file.
    File Read Allows reading any file in the local file system at specified directories.
    List of directories (File Read) List all directories that allow to read any file.
    Network Access Allows establishing network connection.
    Access to External Java Class Allows dynamically accessing to Java classes at run-time.

     

  7. For the configuration to take effect, you are required to save your changes. There is a default path and file name displayed in the text box down close to the bottom of the figure. If you want to save the security properties to the default path and file, click OK to save. Otherwise, specify your own path and file name to save the security properties to. You can later change the setting by either modifying this file or changing it in the figure above.
    Note 1:
    You can set different security properties for the root and registered applications. They do not affect one another. If you do not specify any security properties for a registered application, by default, the properties will be set as Unrestricted Access Checked. 
    Note 2: ASP scripts that do not belong to any registered applications can be executed only if  the Unrestricted Access or Allow execution to all scripts Check Box is checked.
    Note 3: Related ASP applications have read/write access only in directories that you have specified in the List of directories allowed to read/write. Directories are required to be full paths. When there are more than one directory to be listed, separate them with OS path separator(;). By default, these lists contain only the full path to the root of the related application.

  8. Next, click the App Tuning tab to display the application tuning options (figure 12):

    figure 12
       

    The App Tuning tab lets you specify application options described in the following table:

    Control

    Description

    Application number limited When this check box is enabled, the number of ASP applications that can be run is limited to the number specified in the Maximum number application edit box.
    Maximum number application When the Application number limited check box is enabled, you can enter the maximum number of applications in this edit box.


  9. When you have finished, click the Apply button make your changes take effect.
  10. Finally, click the App Mapping tab to display the application mapping options (figure13):

    figure 13

    The App Mapping tab allows you to define both prefix and suffix mappings for your servlets. For example, when defining a prefix mapping, you can specify whether the request contains a particular prefix, with which a specified servlet should run.

    Mapping prefixes

    You map the prefix /servlet/ to the servlet invoker and point your browser at the following URL:

    http://www.yourdomain.com/servlet

    The servlet invoker is run.

    If any information follows the prefix, it is sent to the servlet as extra path information. The URL:

    http://www.yourdomain.com/servlet/mypath

    invokes invoker with /mypath as the extra path information.

    Mapping suffixes

    For suffix mappings, you can define a file extension that will invoke a particular servlet. For example, you could map the .asp extension to run the aspServlet.

    Note: The suffix mappings are invalid for any 3rd party servlet interface (such as Zeus, Sun Webserver, Apache JServ etc).

  11. To add a new mapping, simply select the Add button in Application Configuration|App Mapping window (figure 7). A new row is added and you can enter the suffix or prefix along with the servlet name. When entering a suffix mapping, use an * (asterisk) to denote any file with that suffix.
  12. To edit an existing mapping, click the Modify button and edit the mapping in place.
  13. To delete an entry, select row in the list and click the Delete button.
  14. When you have finished, click the Apply button to make your changes take effect.

If you encounter any problems or errors, please contact support@halcyonsoft.com.


Copyright © 1998-2000, Halcyon Software Inc. All rights reserved.