Publication attributes

Specifies the name of the Publication Configuration. This name is only important at publish time in Web Designer. You must choose exactly one Publication Configuration to publish against. Your choice determines the set of publication attributes, system-defined publication properties, and user-defined publication properties (if any) that will be applied to your publication.

Specifies the folder where the file tree of published materials will be created or updated.

Specifies an alternative location where CSS style sheets, images, and scripts can be stored. During publication, all files in the publication folder are overwritten by files with the same name in the same subfolder of this alternative location (if any). This way, the Alternative Template Folder provides a safe location for files that you have changed and wish to keep. See The Alternative Template Folder for more details.

If you are using .ASPX with IIS for web server settings (the pre-USoft 9.1 technology), then this property specifies the JDBC connection string with which the USoft Page Engine connects to the Rules Service.

If you are using a Page Engine defined in Service Definer as a REST Service, then this property does NOT supply any necessary runtime information, but its value must still be according to syntax in order to avoid such errors as "Resource not found" or "Rules Service not available".

Syntax

jdbc:jrec:application@computer-name:port-number

where application is the published USoft application, computer-name is the machine where the web server runs, and port-number is the port number where the Rules Service runs. If the web server runs on the current development machine, you can use the localhost keyword for computer-name.

Example

jdbc:jrec:TRAVEL@localhost:7777

Specifies the information logged in the log file:

•NOLOG specifies that no logging takes place.

•ERROR (default) specifies that only errors will be written in the log subfolder.

•INFO specifies that also the appropriate Combined.xml file (generated by the Page Engine before it is transformed by the XSL transformations) is written. The INFO setting is advised in a development environment, ERROR is advised in the production environment for performance reasons.

•DEBUG specifies that all requests to a Rules Engine are logged.

For performance reasons, the USoft Page Engine caches the combination of each user and first menu page. The Cache Refresh Period attribute specifies the amount of time in seconds after which this cache is always refreshed. The default is 180 (seconds). Note that when the USoft Page Engine is shut down, the cache is also automatically refreshed. The first time the user credentials are checked, the cache is not used. If this attribute is set to -1, menus are refreshed on each call. If set to 0, menus are refreshed only on the first call.

Do not confuse this cache refresh period attribute with the resource name with the same name used by the the Rules Engine to specify the refresh period for all authorization data. This setting is described in the Authorizer help.

When sending a SQL statement to the Rules Service, the Page Engine uses an 'INVOKE xml.import' statement. The Verify original Values attribute specifies whether you want the Rules Engine to check whether the original values are checked (whether the data manipulated has not already been changed). Allowed values are:

•NO (no check),

•ALLCOLUMNS (all columns of the manipulated record are checked), and

•CHANGEDCOLUMNS (default - only columns that are changed are checked).