Helma Logo
main list history

Version 8 by hannes on 29. September 2009, 09:56

238<a name="rhino.profile"></a>
239<tr bgcolor="#ccccff">
240<td valign="top" nowrap="nowrap"><tt>rhino.profile</tt></td>
241<td valign="top">app</td>
242<td valign="top">If set to true, the Rhino *profiler* is enabled. The default value is false.</td>
245<a name="rhino.profile.session"></a>
246<tr bgcolor="#ccccff">
247<td valign="top" nowrap="nowrap"><tt>rhino.profile.session</tt></td>
248<td valign="top">app</td>
249<td valign="top">If set, the *profiler* is only applied to requests with a session id matching the property value. The default value is to debug all requests and internal calls.</td>

Version 7 by Philipp on 19. August 2009, 17:36

139<a name="httpOnlySessionCookie httpOnlySessionCookie"></a>

Version 6 by Philipp on 19. August 2009, 17:34

139<a name="httpOnlySessionCookie "></a>
140<tr bgcolor="#ccccff">
141<td valign="top" nowrap="nowrap"><tt>httpOnlySessionCookie </tt></td>
142<td valign="top">app</td>
143<td valign="top"><a href="http://www.owasp.org/index.php/HTTPOnly">HttpOnly session cookies</a> are enabled by default since Helma 1.6.3. This means that browsers might prevent client-side JavaScript from accessing session cookies stored in the document.cookie property. If client-side JavaScript needs to access session cookies, you have to set httpOnlySessionCookies to <tt>false</tt>!</td>

Version 5 by hannes on 19. February 2009, 11:59

Version 4 by zumbrunn on 18. February 2009, 21:44

5Regarding type.properties files please refer to the *Object-Relational Mapping* documentation.

Version 3 by maks on 18. February 2009, 05:26

240<a name="rhino.strictvars"></a>
242<td valign="top" nowrap="nowrap"><tt>rhino.strictvars</tt></td>><tt>strictvars</tt></td>

Version 2 by hannes on 17. February 2009, 22:08

75<td valign="top">Defines the size of the node cache. See the docs of the <% this.link to="http://helma.org/stories/77405/" text="cache mechanism" %></td>*caching* documentation</td>
96<td valign="top">Allows cron jobs to be defined, similar to the unix cron daemon, <a href="http://helma.org/development/rfc/cronjobs/">but *but with a nicer configuration syntax</a>syntax|Cronjobs*.</td>

Version 1 by hannes on 17. February 2009, 22:04

1This is a list of properties recognized by Helma that can be set in the server.properties and/or app.properties files.
3Hints about which property can be set in which property file are displayed in the "Range" column.
5Regarding type.properties files please refer to the *Object-Relational Mapping* documentation.
7<table width="95%" border="1" cellspacing="0" cellpadding="5">
8<tr class="small">
14<a name="ajp13Port"></a>
15<tr bgcolor="#ccccff">
16<td valign="top" nowrap="nowrap"><tt>ajp13Port</tt></td>
17<td valign="top">server</td>
18<td valign="top">Specifies the port number where Helma should listen for AJP13 connections.</td>
21<a name="allowAJP13"></a>
22<tr bgcolor="#ccccff">
23<td valign="top" nowrap="nowrap"><tt>allowAJP13</tt></td>
24<td valign="top">server</td>
25<td valign="top">Specifies ip adresses that are allowed to connect to the Helma AJP13 server (port 8009). By default, only connections from localhost are accepted.</td>
28<a name="allowRMI"></a>
29<tr bgcolor="#ccccff">
30<td valign="top" nowrap="nowrap"><tt>allowRMI</tt></td>
31<td valign="top">server</td>
32<td valign="top">Specifies ip adresses (or networks) that are allowed to connect to the Helma rmi servlet server (port 5055). For more than one ip adress put a comma, semicolon or space between the entries, subnets should be written as e.g. "192.168.0.*". (the same setting is also settable using the somewhat misleading property name allowWeb)</td>
35<a name="allowXmlRpc"></a>
36<tr bgcolor="#ccccff">
37<td valign="top" nowrap="nowrap"><tt>allowXmlRpc</tt></td>
38<td valign="top">server, app</td>
39<td valign="top">Same as <a href="#allowRMI">allowRMI</a>, but for the XML-RPC server (port 5056).</td>
42<a name="appHome"></a>
43<tr bgcolor="#ccccff">
44<td valign="top" nowrap="nowrap"><tt>appHome</tt></td>
45<td valign="top">server</td>
46<td valign="top">Defines the path to the location of Helma applications. If not specified, [hopHome]/apps will be used.</td>
49<a name="appsPropFile"></a>
50<tr bgcolor="#ccccff">
51<td valign="top" nowrap="nowrap"><tt>appsPropFile</tt></td>
52<td valign="top">server</td>
53<td valign="top">Sets the location of the apps.properties file (i.e. for security reasons). The default is the root directory of your Helma installation.</td>
56<a name="autoETags"></a>
57<tr bgcolor="#ccccff">
58<td valign="top" nowrap="nowrap"><tt>autoETags</tt></td>
59<td valign="top">app</td>
60<td valign="top"> Enables ("autoETags = true") or disables ("autoETags = false") automatic generation of ETag headers for HTTP conditional GET. Switched on per default.
64<a name="baseURI"></a>
65<tr bgcolor="#ccccff">
66<td valign="top" nowrap="nowrap"><tt>baseURI</tt></td>
67<td valign="top">server, app</td>
68<td valign="top">Specifies the prefix to add to urls generated by a Helma application. For example, if your application is "mounted" at /myapp in the server's document tree, you'd state "baseURI = /myapp".</td>
71<a name="cachesize"></a>
72<tr bgcolor="#ccccff">
73<td valign="top" nowrap="nowrap"><tt>cachesize</tt></td>
74<td valign="top">server, app</td>
75<td valign="top">Defines the size of the node cache. See the docs of the <% this.link to="http://helma.org/stories/77405/" text="cache mechanism" %></td>
78<a name="charset"></a>
79<tr bgcolor="#ccccff">
80<td valign="top" nowrap="nowrap"><tt>charset</tt></td>
81<td valign="top">server, app</td>
82<td valign="top">Defines the character encoding. The default is ISO-8859-1 (Western) encoding. You can use any of the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html">encodings supported by Java</a>.</td>
85<a name="country"></a>
86<tr bgcolor="#ccccff">
87<td valign="top" nowrap="nowrap"><tt>country</tt></td>
88<td valign="top">server</td>
89<td valign="top">Like language, this is used to set the country for proper localisation. For details you can refer to this <a href="http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html">list of country codes</a>.</td>
92<a name="cron"></a>
93<tr bgcolor="#ccccff">
94<td valign="top" nowrap="nowrap"><tt>cron</tt></td>
95<td valign="top">app</td>
96<td valign="top">Allows cron jobs to be defined, similar to the unix cron daemon, <a href="http://helma.org/development/rfc/cronjobs/">but with a nicer configuration syntax</a>.</td>
99<a name="dbHome"></a>
100<tr bgcolor="#ccccff">
101<td valign="top" nowrap="nowrap"><tt>dbHome</tt></td>
102<td valign="top">server</td>
103<td valign="top">Defines the path to the location of the embedded database files. If not specified, [hopHome]/db will be used</td>
106<a name="debug"></a>
107<tr bgcolor="#ccccff">
108<td valign="top" nowrap="nowrap"><tt>debug</tt></td>
109<td valign="top">server, app</td>
110<td valign="top">Switches between "normal" logging output ("debug = false") and the extensive "debug" output ("debug = true") which may be useful when developing. Default setting is "false".</td>
113<a name="error"></a>
114<tr bgcolor="#ccccff">
115<td valign="top" nowrap="nowrap"><tt>error</tt></td>
116<td valign="top">server, app</td>
117<td valign="top">The name of the Action defined in the Root prototype that will be called if an application error occurs. This provides the facility to output a nice error page to the user, rather then the default helma one.</td>
120<a name="hopHome"></a>
121<tr bgcolor="#ccccff">
122<td valign="top" nowrap="nowrap"><tt>hopHome</tt></td>
123<td valign="top">server</td>
124<td valign="top">This property defines the Helma working directory, e.g. "hopHome = /hop/apps". If not specified, the current directory is used.</td>
127<a name="hrefFunction"></a>
128<tr bgcolor="#ccccff">
129<td valign="top" nowrap="nowrap"><tt>hrefFunction</tt></td>
130<td valign="top">app</td>
131<td valign="top">The name of a function to be called to postprocess the result of the HopObject <% shortcut name="href()" %> function. If this option is specified, Helma will walk up the object's path until it finds an object that does have a function with the given name. If it is found, the function is called with the raw href string as only argument. The return value of this function is then returned to the original caller of href().</td>
134<a name="hrefSkin"></a>
135<tr bgcolor="#ccccff">
136<td valign="top" nowrap="nowrap"><tt>hrefSkin</tt></td>
137<td valign="top">app</td>
138<td valign="top">The name of the skin that is assigned to this property is used to extend the <% shortcut name="href()" %> function. E.g. setting "hrefSkin = customLink" will cause Helma to set param.path to the result of href() and to render the skinfile customLink.skin as if the function renderSkin("customLink", param) was invoked. Take a look at the <% shortcut name="hrefSkin example" %> for the whole picture.</td>
141<a name="idBaseValue"></a>
142<tr bgcolor="#ccccff">
144<td valign="top" nowrap="nowrap"><tt>idBaseValue</tt></td>
145<td valign="top">server, app</td>
146<td valign="top">Used to set the current value of the internal ID generator. This is useful when starting a new internal db (where the id value would normally start at 1), but relational dbs are used that already contain data. Only applied if the current counter value is smaller than idBaseValue.</td>
149<a name="language"></a>
150<tr bgcolor="#ccccff">
151<td valign="top" nowrap="nowrap"><tt>language</tt></td>
152<td valign="top">server</td>
153<td valign="top">Used to set the language on systems where the Java runtime doesn't recognize it by itself (e.g. Linux), which may be important for date formatting and the like. Refer to this <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">list of language codes</a> for details.</td>
156<a name="logDir"></a>
157<tr bgcolor="#ccccff">
158<td valign="top" nowrap="nowrap"><tt>logDir</tt></td>
159<td valign="top">server, app</td>
160<td valign="top">Defines the path to the location where log files will be written. Either in the form  "logdir = /path/to/log/directory" or "logdir = console" to log directly to the console. If not specified, [hopHome]/log will be used</td>
163<a name="loggerFactory"></a>
164<tr bgcolor="#ccccff">
165<td valign="top" nowrap="nowrap"><tt>loggerFactory</tt></td>
166<td valign="top">server</td>
167<td valign="top">Can be set to a class name, enabling the <a href="http://helma.org/docs/howtos/log4j/">use of alternative loggers like log4j</a></td>
170<a name="logSQL"></a>
171<tr bgcolor="#ccccff">
172<td valign="top" nowrap="nowrap"><tt>logSQL</tt></td>
173<td valign="top">server, app</td>
174<td valign="top">With this option set to "true", Helma writes out all SQL select statements to the logging device (and just those, so you won't find any insert, update or delete statements in there).</td>
177<a name="maxThreads"></a>
178<tr bgcolor="#ccccff">
179<td valign="top" nowrap="nowrap"><tt>maxThreads</tt></td>
180<td valign="top">server, app</td>
181<td valign="top">Sets the maximum number of Helma's Java threads, e.g. "maxThreads = 12". This is one of the parameters you should adjust for each server depending on the applications you run. If you see an error like "maximum thread count reached" you should increase the value of this property.</td>
184<a name="minThreads"></a>
185<tr bgcolor="#ccccff">
186<td valign="top" nowrap="nowrap"><tt>minThreads</tt></td>
187<td valign="top">server, app</td>
188<td valign="top">Sets the minimum number of Helma's Java threads and evaluators to be allocated at application startup time, e.g. "minThreads = 3". This is one of the parameters you should adjust for each server depending on the applications you run. If you expect lots of traffic and experience slow evaluator inialization when the server is started you might want to set this property.</td>
191<a name="notfound"></a>
192<tr bgcolor="#ccccff">
193<td valign="top" nowrap="nowrap"><tt>notfound</tt></td>
194<td valign="top">server, app</td>
195<td valign="top">The name of the Action defined in the Root prototype that will be called if the object specified by a http request cannot be found. This provides the facility to output a nice 404 'not found' page to the user, rather then the default helma one.</td>
198<a name="paranoid"></a>
199<tr bgcolor="#ccccff">
200<td valign="top" nowrap="nowrap"><tt>paranoid</tt></td>
201<td valign="top">server</td>
202<td valign="top">If set to "true", Helma switches to "paranoid" mode which means that it won't accept connections from servers with unknown ip adresses >you can specify allowed ip adresses with the <a href="#allowWeb">allowWeb</a> and <a href="#allowXmlRpc">allowXmlRpc</a> properties. Default setting is "paranoid = false".</td>
205<a name="persistentSessions"></a>
206<tr bgcolor="#ccccff">
207<td valign="top" nowrap="nowrap"><tt>persistentSessions</tt></td>
208<td valign="top">server, app</td>
209<td valign="top">Setting "persistentSessions=true" in the app.properties file will attempt to preserve sessions through an application reset or server shutdown/restart, except for sessions that have expired in the meantime. Optional read-only property, default is false.</td>
212<a name="requestTimeout"></a>
213<tr bgcolor="#ccccff">
214<td valign="top" nowrap="nowrap"><tt>requestTimeout</tt></td>
215<td valign="top">server, app</td>
216<td valign="top">Defines the time in seconds after which a request receives a timeout. Normally there is no need to change this value, but if you have tasks in your Helma application that take a longer time, you should increase this value.</td>
219<a name="requestTimeoutStop"></a>
220<tr bgcolor="#ccccff">
221<td valign="top" nowrap="nowrap"><tt>requestTimeoutStop</tt></td>
222<td valign="top">app</td>
223<td valign="top">If set to true threads get stopped using Java's deprecated Thread.stop() (see <a href="http://java.sun.com/j2se/1.4.2/docs/guide/misc/threadPrimitiveDeprecation.html">related notes from Sun</a>). The default value is false.</td>
226<a name="rhino.debug"></a>
227<tr bgcolor="#ccccff">
228<td valign="top" nowrap="nowrap"><tt>rhino.debug</tt></td>
229<td valign="top">app</td>
230<td valign="top">If set to true, the visual Rhino debugger activated (this happens on the server-side, of course). The default value is false.</td>
233<a name="rhino.languageVersion"></a>
234<tr bgcolor="#ccccff">
235<td valign="top" nowrap="nowrap"><tt>rhino.languageVersion </tt></td>
236<td valign="top">server, app</td>
237<td valign="top">If set to "170", new Javascript 1.7 features will be enabled when using a Rhino 1.7 jar file.</td>
240<a name="rhino.strictvars"></a>
241<tr bgcolor="#ccccff">
242<td valign="top" nowrap="nowrap"><tt>rhino.strictvars</tt></td>
243<td valign="top">server, app</td>
244<td valign="top">If set to true, reports errors for variables with missing var statement. The default value is false.</td>
247<a name="rmiPort"></a>
248<tr bgcolor="#ccccff">
249<td valign="top" nowrap="nowrap"><tt>rmiPort</tt></td>
250<td valign="top">server</td>
251<td valign="top">Specifies the port number where Helma should listen for Java RMI connections.</td>
254<a name="schedulerInterval"></a>
255<tr bgcolor="#ccccff">
256<td valign="top" nowrap="nowrap"><tt>schedulerInterval</tt></td>
257<td valign="top">server, app</td>
258<td valign="top">The time in seconds after which scheduled cron jobs are executed again. Makes it possible to cause cron jobs to be run several times per minute.  Note that this will have the side effect to invoke *all* cronjobs at the specified seconds interval within the minute that they are scheduled to run. For example, with this setting set to 5, a cron job that is scheduled to run once a week, will run every five seconds during one minute once a week.</td>
261<a name="sessionTimeout"></a>
262<tr bgcolor="#ccccff">
263<td valign="top" nowrap="nowrap"><tt>sessionTimeout</tt></td>
264<td valign="top">server, app</td>
265<td valign="top">This determines the time (in minutes) after which an inactive session becomes invalid. The default is 30 minutes.</td>
268<a name="skinCharset"></a>
269<tr bgcolor="#ccccff">
270<td valign="top" nowrap="nowrap"><tt>skinCharset</tt></td>
271<td valign="top">server, app</td>
272<td valign="top">Defines the character encoding for skins. If not set, the platform's default encoding is used. You can use any of the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html">encodings supported by Java</a>.</td>
275<a name="skinPath"></a>
276<tr bgcolor="#ccccff">
277<td valign="top" nowrap="nowrap"><tt>skinPath</tt></td>
278<td valign="top">app</td>
279<td valign="top"></td>
282<a name="smtp"></a>
283<tr bgcolor="#ccccff">
284<td valign="top" nowrap="nowrap"><tt>smtp</tt></td>
285<td valign="top">server, app</td>
286<td valign="top">Specifies an SMTP server, e.g. "smtp = mail.server.dom". If you want Helma to send e-mail you should define this property.</td>
289<a name="sourceCharset"></a>
290<tr bgcolor="#ccccff">
291<td valign="top" nowrap="nowrap"><tt>sourceCharset</tt></td>
292<td valign="top">server, app</td>
293<td valign="top">Defines the character encoding for source files (*.js, *.hac). If not set, the platform's default encoding is used. You can use any of the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html">encodings supported by Java</a>.</td>
296<a name="timezone"></a>
297<tr bgcolor="#ccccff">
298<td valign="top" nowrap="nowrap"><tt>timezone</tt></td>
299<td valign="top">server</td>
300<td valign="top">It might be necessary to explicitly set the timezone for Helma. If "new Date()" puts out the wrong date, check if this option was set correctly. For details, refer to this <a href="http://greenwichmeantime.com/info/timezone.htm">list of timezones</a>.</td>
303<a name="webPort"></a>
304<tr bgcolor="#ccccff">
305<td valign="top" nowrap="nowrap"><tt>webPort</tt></td>
306<td valign="top">server</td>
307<td valign="top">Specifies the port number where Helma should listen for HTTP connections.</td>
310<a name="xmlParser"></a>
311<tr bgcolor="#ccccff">
312<td valign="top" nowrap="nowrap"><tt>xmlparser</tt></td>
313<td valign="top">server</td>
314<td valign="top">Can be used to specify a different XML parser, e.g. "xmlparser = minml". If not specified, the system property "sax.driver" is considered before defaulting to OpenXML. Note that this setting effects XML-RPC and the Xml host object only, but not the E4X XML object, nor the global.getHtmlDocument() and global.getXmlDocument() methods.</td>
317<a name="xmlRpcAccess"></a>
318<tr bgcolor="#ccccff">
319<td valign="top" nowrap="nowrap"><tt>xmlRpcAccess</tt></td>
320<td valign="top">app</td>
322<td valign="top">Functions which should be callable via XML-RPC need to be listed in this property on a per-application basis. The list contains entries of the kind "prototype.function" for each exposed function separated by commata, e.g. "xmlRpcAccess = weblog.getStory, weblog.showStatus".</td>
325<a name="xmlRpcHandlerName"></a>
326<tr bgcolor="#ccccff">
327<td valign="top" nowrap="nowrap"><tt>xmlRpcHandlerName</tt></td>
328<td valign="top">app</td>
329<td valign="top">Setting this property makes it possible to change the name under which an application is registered with the XML-RPC server. For example, this means that the functions exposed via XML-RPC could be given a "blogger" prefix. For instance a function called "newPost" will then be XML-RPC callable as "blogger.newPost" instead of "antville.newPost".</td>
332<a name="xmlrpcPort"></a>
333<tr bgcolor="#ccccff">
334<td valign="top" nowrap="nowrap"><tt>xmlrpcPort</tt></td>
335<td valign="top">server</td>
336<td valign="top">Specifies the port number where Helma should listen for XML-RPC connections.</td>