System Preferences

---

Use this form to set up system-wide general Webstore preferences.

Template reloads

Enter the path to your Webstore templates, or use the Browse button to set the path. The path to the templates should be a network path to make it easier to re-load the templates while logged into Greentree Desktop from another computer.

Templates contain all the detail and formatting displayed on each Webstore page. To speed the display of Webstore pages, all templates are pre-loaded and indexed in the database for quick access when requested by a web user.

Note: Webstore templates are in the folder <Greentree System Path>\Webstore\Templates.

If you make a change to a template, you must re-load the change into the database using the Reload option. You can re-load templates from any Greentree Desktop client to update the network.

Server Settings

Specify the Webstore server port number. This is the port that jhp.dll uses to communicate with the Webstore server. The default port number is 7010. This port number must match the JadeServerPort attribute in the jhp.ini file.

If the Enable debugging or Output code options are selected, information is output to the JADE output monitor text form for each request and response made between all web browsers and Webstore. This may be useful in determining whether the correct response is being made by Webstore when testing page display.

General Settings

Log Webstore activity

If you select this option, a Webstore Log.txt file containing all Webstore activity is created in the system folder on the database server. This file is cleared after it reaches 900,000 characters. The Webstore log details all requests, responses and errors while processing a Webstore request.

Session timeout (minutes)

Specify the time between page requests that can lapse before the session is removed and the web user, on making another request, is required to log in again.

Session check (minutes)

Specify the time between checks if any sessions have exceeded the session timeout.

Update Password

If you require templates to be updated without using this form, enter a certain URL into the web browser that either reloads a single template, reloads all templates, or reloads the webtext. Part of this URL is a password which you can enter for reference.

You can update the password while the web server is running. Be sure to test your template changes first.

To reload templates without being logged into Greentree Desktop, you must include a current session ID in the URL:

https://www.yourdomain.com/webstore/index.ect?session01=1238sdf23sdf7u2&page01=update&pagename01=all&password01=passwordhere

Where:

• www.yourdomain.com = the computer running Webstore - use 'localhost' if it is the current computer.
• 1238sdf23sdf7u2 = the session found from navigating to any page link once within Webstore.
• all = the template name to reload, without the ect extension, or 'all' for all templates and webtext, or 'webtext' for just the webtext.
• passwordhere = the password defined as the update password.

A message displays when the page reloads. When reloading all templates, this may take some time. Don't try to refresh during this time.

If this update password is not set, templates cannot be updated through the web.

Check session's IP address

This option is selected by default. If you select this option, an IP address is stored against each session and checked with each page request to see that the page request is coming from the same computer that the session was originally created for.

This is optional because with some Internet service providers, the IP addresses are in a pool and swap randomly. This could result in a web user not being able to continue making page requests as the IP address they were using is changed to a new IP address in the same connection.

Worker Thread Settings

Webstore is multi-threaded which means that many web page requests to Webstore can occur all at once. Greentree Desktop can process all requests up to the number of worker threads open at the same time.

Note: A page request only lasts for 0.5 to 2 seconds and a maximum of 15 seconds. It does not include the time reading a page after it is requested. The web, in most scenarios is state-less meaning the web server only takes a request and sends a response, then forgets about everything.

It does not maintain a connection to a web browser over the time that a web page is being read. This is why a session ID must be maintained and timed out within Webstore.

Single threaded

This option should usually be left deselected and only be used to debug the Webstore code. If it is selected, the remaining worker thread options are unavailable.

Worker threads

This is a numeric value defining the number of worker threads to start when first starting Webstore. The default is 10, which means if 10 page requests are made at the same time, all pages can be responded to immediately.

Minimum Available

Enter the minimum number of worker threads that must be sitting idle and available (not processing a web page request) at any one time. If the number of available worker threads is less than this value, this triggers the opening of X number more threads, if X is the Increase by amount.

Increase by

See Minimum Available above.

Maximum available

Enter the maximum number of worker threads that can be opened at once. Note that each worker thread requires more memory and more connection time with the database server. This prevents too many worker threads from being opened when the occasional spike of very heavy Webstore traffic occurs so that the web server does not crash by running out of memory.

Exception Settings

This option should usually be left deselected and only be used to debug the Webstore code if or when an exception occurs. If an exception does occur, the Exception page displays information for reporting to help diagnose and solve the problem.

---