URL Properties
A URL can be configured as a property at many places throughout the system. URLs can be configured in three ways:
URLs can be either absolute or relative.
An absolute URL begins with a protocol, usually http: e.g. http://www.ebasetech.com. The protocol can be omitted in which case the protocol used to load the content page is used e.g. a URL of //www.ebasetech.com is changed to http://www.ebasetech.com or https://www.ebasetech.com depending on whether the content page was loaded using http or https.
A relative URL does not begin with a protocol or // and is resolved as being relative to the web application root. In the supplied Tomcat system, this is <domain>/ufs e.g. a relative URL of images/helpimage1.gif will be resolved as <domain>/ufs/images/helpimage1.gif. In addition, A URL beginning with a single / is resolved relative to the root of the application server e.g. a URL of /images/helpimage1.gif will be resolved as <domain>/images/helpimage1.gif.
A URL beginning with $ws represents a URL to be resolved from within the workspace, where the remainder of the URL following $ws is treated as the path to the workspace file. For example a URL of $ws/housing/images/home.gif will load an image from the workspace at path /housing/images/home.gif. The system will search all linked projects looking for this image.
In most cases, URL’s can contain a field name and other variables as part or all of their content. These variables are then dynamically evaluated at runtime and substituted into the URL. Field variables and environment variables can be specified.
Substitution examples:
· &&VAR1
· images/&&{IMAGES_DIR}/&&{IMAGE_NAME}.gif
· &&{$ENV_IMAGES_ROOT}/help1.gif