or link on the Administrator Home Page.Administrator Interface
There are several features and settings that can be set from this page.
To access the Web Manager Application
Settings, click the Application
icon or link on the Administrator Home Page.
If for some reason the Web Manager configuration gets out of sync with what is stored in memory, it may be necessary to reload the application.
On the Administrator
Home Page, click the Application
icon or link.
Click the Reload button. The Web Manager application will be reloaded into memory.
The Web Manager has a very powerful scripting capability. If you are using the Web Manager scripting feature, you can run scripts using this interface.
On the Administrator
Home Page, click the Application
icon or link.
Select the desired script from the drop down list.
Click the Run Script button. The script will run and you will receive a confirmation message.
The Miscellaneous Settings page is used to configure several features of the Web Manager application.
Most configurable settings are accessed via the standard Web Manager Administrator Interface and are described in the following Miscellaneous Settings section . However several less frequently used features can only be configured by editing the configurable.properties page with Notepad as described at the end of this section.
NOTE All
the following Automatic Login options are global in scope. In
other words, once you turn this feature on, it will apply to all Users.
Automatic Login is a feature that allows users to bypass the Login screen and go directly to the launch screen.
Server Authentication - This mode allows the Administrator to handle authentication from within the server's security framework. If a user has already authenticated to a server via the Web browser, then Web Manager can detect the user name accepted by the server. Consult your server's documentation for controlling Web access to the server.
If the user is not authenticated, then Web Manager will deny the request. The user will be presented with the following screen:
If the user is authenticated, Web Manager will attempt to match the authenticated User's Username to a Login ID and proceed to the Launch Page.
If Web Manager cannot match the Username to a Login ID, then Web Manager will perform "implicit configuration" and will assume the user is a member of the Default Group and proceed to the launch screen.
If you do not wish to allow implicit configuration with Server Authentication, simply delete all sessions from the Default Group and place all users in other groups. Any user who is "implicitly configured" will simply receive a blank launch screen.
Implicit configuration can be a very convenient and powerful tool for administrators lucky enough to not have to assign user specific Session Overrides such as LU Name/Device Name. This mechanism allows the administrator to run Web Manager, without configuring a single user! Use multiple instances of Web Manager for multiple groups.
IP Address - This mode instructs Web Manager to detect the IP address of the requesting browser and use it as the Login ID. Web Manager then sets the Login password to an empty string "", then attempts to perform the Login. If no matching Login ID is found, then Web Manager will deny the request.
Host Name - This mode instructs Web Manager to detect the Host Name of the requesting browser and use it as the Login ID. Web Manager then sets the Login password to an empty string "", then attempts to perform the Login. If no matching Login ID is found, then Web Manager will deny the request.
CAUTION! The
Web server supplies the Host Name to Web Manager. If
the server is performing DNS lookups then the name may be a DNS name of
the form "machine.domain.com", however if it does not perform
the lookup then the Web Server may simply return the IP address of the
requesting browser. It
is also possible that the Web Server will return the name of an intermediate
proxy server. Use
this mode with CAUTION!
Short Host Name - This mode works identically to the Host Name mode, with the exception that prior to attempting the Login, Web Manager will take the given Host Name and will substring it up until the first dot "." character encountered. Thus a host name of "machine.domain.com" will become "machine". For the reasons outlined in "Host Name", use this mode with CAUTION!
NetBIOS Name - This mode instructs Web Manager to perform a NetBIOS lookup on the requesting machine IP address. This will return the "Network Neighborhood" name of the machine. Web Manager then sets the Login password to an empty string "", then attempts to perform the Login. If no matching Login ID is found, then Web Manager will deny the request.
This feature is used in conjunction with the Login Script feature below. If you want to use a Login Script, change the value to "True".
If you are using a Web Manager Login Script, use the drop down list to select the particular script file.
NOTE Web
Manager Scripting is designed to support advanced automated User Login
via external databases like SQL, LDAP, Novell NDS, etc.
This setting determines whether debug information should be printed to the bottom of every screen in the Administrator interface. This information is only useful to Seagull Software Customer Care Personnel while debugging the Web Manager application itself.
Normally, Debug to Screen should be set to "False".
The Web Manager maintains several logs which contain information about its activities. Certain activities, like User Logins, are always logged; but other activities of the Web Manager are logged only when it is necessary for debugging purposes. The information contained in theses logs are effectively traces of the application.
In production environments, logging should be kept at the "INFO" level. The other levels are typically used for troubleshooting and debug purposes.
SEE Application
Logs for more information.
In addition to the Miscellaneous Settings described above, there are a few less frequently used settings which can not be accessed via the Application Section. To change these settings, edit the configurable.properties page with Notepad. This page can be found in the following location:
\swm\WEB-INF\configurable.properties
The beginning of the configurable.properties page will look similar to this:
##
# Print application debug information to the browser in
# the Admin section.?
# Browser configurable - Application Section.
##
show.debug=false
##
# On Login to the Hosts section, if the Login fails
# redirect the client to this Login. Set to empty
# to use application default.
# Not browser configurable.
##
onfail.url=
The single # sign is used as a comment. The double ## sign is used to note the start and end of a section.
To tell whether a feature is accessible via the browser, or if you must make changes to the configurable.properties page, edit the configurable.properties page with Notepad and look at each individual section. If the particular section has the following note:
# Browser
configurable - Application Section.
Then you would use the Miscellaneous Settings feature described above to make your changes. If the particular section has the note:
# Not browser configurable.
Then you must make your desired changes on this page. The features along with their possible settings are well documented on this page and will not be described in this guide.