You can use the Remote Console Applet Application Settings to perform
the following tasks:
Viewing the Properties of an Application
- Click the Application button to display the Application tree in the
left-hand pane of the Remote Console Applet.
- Optionally, expand the Application Root branch by clicking the + sign
adjacent to it.
If you have no existing applications, the Application Root branch is
selected by default.
- Right-click the application for which you want to view properties.
You can view the Application Root properties to view properties shared
by multiple ASP applications.
- From the pop-up menu, choose Properties.
- When you are finished, click the Cancel button to quit and return
to the main window of the Remote Console Applet.
Creating a New Application
- Click the Application button to display the Application tree in the
left-hand pane of the Remote Console Applet.
- Right-click the Application Root branch in the left-hand pane of the
Remote Console Applet.

- From the pop-up menu, choose New-->Application.
The Welcome to the New Application Wizard launches.

- Enter the name of the application in the Application text field.
- Enter the fully qualified path to the application in the Path to the
application text field.
- Click the OK button.
After the application is created, the global server variables in the
global.asa file (which exists in the same directory as the application)
will be loaded along with the application.
Configuring the Properties of a Single Application
- Click the Application button to display the Application tree in the
left-hand pane of the Remote Console Applet.
- Expand the Application Root branch by clicking the + sign adjacent
to it.
A list of existing applications displays.
- Right-click on the application you would like to configure.

- From the pop-up menu, choose Properties.
The right pane of the Remote Console Applet displays the Application
Properties settings.
The Application Configuration page appears by default.
The name and fully qualified path of the application appear in at the
top of the pane for your reference.

- Change the properties on each tabbed page as appropriate and click
the Apply button to save the changes on each page.
Refer to Application Properties Setting for
the details on the properties that you can set.
NOTE: The properties that you set for
a specific application take precedence over the properties that you set
for the Application Root branch. You can override a property when you
modify it in the Application Root branch. (If you change a property of
a specific application and then change the same property from the Application
Root branch, the Inheritance Overrides dialog pops up and asks you for
which applications you wish to make the change.)
Deleting an Application
- Click the Application button to display the Application tree in the
left-hand pane of the Remote Console Applet.
- Expand the Application Root branch by clicking the + sign adjacent
to it.
A list of existing applications displays.
- Right-click on the application you would like to delete.
- From the pop-up menu, choose Delete.
Making Global Changes to the Configurations of
Multiple ASP Applications
To make global changes to the configurations for all of your ASP applications,
you modify the properties of the Application Root branch.
The properties that you set for the Appication Root branch act as a template
for applications that you create. That is, once you set a property in
the Application Root branch, the setting applies to each specific application
unless you override it by editing it for that specific application.
- Click the Application button to display the Application tree in the
left-hand pane of the Remote Console Applet..
- Right-click the Application Root branch.
NOTE: By default, the Application
Root's name is "root" and its local path is mapped to your
web server's documentation root path.

- From the pop-up menu, choose Properties:
The right pane of the Remote Console Applet displays the Root Properties
settings.
The Application Configuration page appears by default.
- Change the properties on each tabbed page as appropriate and click
the Apply button to save the changes on each page.
Refer to Application Properties Setting for
the details on the properties that you can set.
NOTE: If you change a property
of a specific 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. Click Select
All to make a global change or you select the individual applications
to which you want the property to apply. Click the OK button to apply
the changes or the Cancel button to return to the Application Configuration
window:
Application Properties Settings
The Application Properties (and Root Properties) settings appear on five
tabbed pages as the following table shows.
Tab Name
|
Page Name
|
App Options
|
Application Configuration
|
App Engine
|
Application Engine:
NOTE: This page is only for the
Enterprise version of iASP.
|
App Security
|
Application Security
|
App Tuning
|
Application Tuning
|
App Mapping
|
Application Servlet Mapping
|
Use these pages to configure properties that you want to apply to multiple
ASP applications using the Application Root branch or to configure specific
properties for a single application.
Using the Application Configuration Page
The App Options tab displays the Application Configuration page as the
following graphic shows. Use the Application Configuration page to set
general configuration properties.
The following table describes the controls that appear on the Application
Configuration page.
When you finish changing settings on this page, click the Apply button
to make your changes take effect.
Control
|
Description
|
Enable Session State |
When this check box is selected, multiple instances
of the application are allowed at the same time. When session
state is enabled, the Session timeout and the Maximum sessions
edit boxes are enabled and you can specify numeric values for
both. |
Session Timeout |
The length of time a session is inactive before it is autmatically
disconnected.
This control is available only when the box for Enable Sesson
State is selected.
|
Maximum Sessions |
The maximum number of sessions allowed at one time.
This control is available only when the box for Enable Sesson
State is selected.
|
Enable Buffering |
When this check box is selected, output to the browser is buffered.
That is, all output generated by the ASP program is collected
before it is sent to the browser. Buffering output enables you
to set HTTP headers from anywhere in an ASP script.
When this check box is cleared, output is returned to the browser
as the page is processed.
|
Enable Parent Paths |
When this check box is selected, 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 |
The primary script language used in your Active
Server pages. Instant ASP comes with two ActiveX script engines:
Microsoft Visual Basic Scripting Edition (VBScript) and Microsoft
JScript (Jscript). The default is VBscript. |
ASP Script Timeout |
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 |
The number of ASP applications which will be stored
on the server after finishing execution. The maximum is 50.
|
Using the Application Engine Page
The App Engine tab displays the Application Engine page as the following
graphic shows. Use the Application Engine page to set the method of executing
asp files on your server. NOTE:
The Application Engine page is available only for the Enterprise version
of iASP.

The default method is Interpreter. When you enable the Interpreter option,
the code contained in an asp file is compiled and executed each time the
page is requested. 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.
When you enable the Pre-Compiler option, iASP compiles your asp file
to a Java Servlet class file. You can then run the Java Servlet class
directly on your server instead of compiling and executing the asp file
each time the page is requested. The Pre-Compiler option is an efficient
and fast way of executing frequently requested asp files.
When you enable the Pre-Compiler Option, the page displays available
pre-compiler settings.

The following table describes the pre-complier controls that appear on
the Application Engine page.
When you finish changing settings on this page, save the changes and
restart the Proxy Server so that the changes can take effect.
Control
|
Description
|
Update Settings |
Dynamic Update: When this button is selected, the asp file is checked
each time you make a request to see if there is any change.
Static Update: When this button is selected, the asp file is not
checked. If it does not stay the same, Pre-Compiler will re-do the
compiling process
|
ASP Settings |
ASP to Java: Compile the asp file to Java Servlet class file.
ASP to JSP: Compile the asp file to JSP(Java Server Page) class
file.
|
Pathname |
The pathname to the directory in which 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. The path
also should be writable so that the generated class files can be saved.
|
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 the settings of Application
Root level.
When you have finished, click the Apply button to make your changes take
effect.
Using the Application Security Page
The App Security tab displays the Application Security page as the following
graphic shows. Use the Application Security page to set security properties.
The following table describes the controls that appear on the Application
Security page.
When you finish changing settings on this page, click the Apply button
to make your changes take effect.
Control
|
Description
|
Unrestricted Access |
When this check box is selected, all ASP pages and applications
have access /permissions.
If you do not specify any security properties for a registered
application, unrestriced access is allowed by default.
|
Allow execution to all scripts |
When this check box is selected, iASP grants execution to unregistered
scripts.
ASP scripts that do not belong to any registered applications
can be executed only if either the Unrestricted Access
or the Allow execution to all scripts check box is checked.
|
Execution of Subprocess |
When this check box is selected, Allows executing sub-process.
Apply permission check for Execution in a script method if this
method launches a sub-process. |
Database Access |
When this check box is selected, Allows access to database. |
File Write |
When this check box is selected, 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.
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.
|
File Read |
When this check box is selected, 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.
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.
|
Network Access |
When this check box is selected, Allows establishing network
connection. |
Access to External Java Class |
Allows dynamically accessing to Java classes at run-time. |
Filename |
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. |
NOTES: You can set different security
properties for the root and registered applications. They do not affect
one another.
Using the Application Tuning Page
The App Tuning tab displays the Application Tuning page as the following
graphic shows. Use the Application Tuning page to set performance tuning
options.
The following table describes the controls that appear on the Application
Tuning page.
When you finish changing settings on this page, click the Apply button
to make your changes take effect.
Control
|
Description
|
Limit the Number of Applications |
When this check box is selected, iASP limits the number of applications
that can be run. |
Maximum number applications |
The maximum number of applications that can be run. This option
is available only when the Application number limited check box
is selected.
|
Application Servlet Mapping
The App Mapping tab displays the Application Servlet Mapping page as
the following graphic shows. Use the Application Servlet Mapping page
to define both prefix and suffix mappings for your servlets.
You can add, edit, or delete current prefix mappings or suffix mappings.
- To add a mapping click the Add button and provide values for the Virtual
Path / Extension and Servlet Invoked fields in the new row that displays.
- To edit a current mapping, select a row in the list, click the Modify
button, and make the appropriate changes.
- To delete a current mapping,, select a row in the list and click the
Remove button.
- When you have finished, click the Apply button to make your changes
take effect.
Prefix Mappings
When you map prefixes, you specify that if a request contains a particular
prefix, it should invoke a particular servlet.
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. For example, the URL:
http://www.yourdomain.com/servlet/mypath
invokes the invoker with /mypath as the extra path information.
Suffix Mappings
For suffix mappings, you can define a file extension that will invoke
a particular servlet. For example, you can map the .asp extension to run
the aspServlet. Enter the suffix in the Virtual Path / Extension field
and the servlet name it will invoke in the Servlet Invoked field.
When entering a suffix mapping, use an * (asterisk) to denote any file
with that suffix.
NOTE: The suffix mappings are invalid
for any 3rd party servlet interface (such as Zeus, Sun Webserver, Apache
JServ etc).
If you encounter any problems or errors, please contact support@halcyonsoft.com
|