Document numberRevision
TN119092

 

Parameter loading

Parameter loadingLoad sequenceDifferent parameters for different websites and web applications

Load sequence

Parameters are loaded in the following order.

  1. Web.config <appSettings> section
  2. Parameter table in database (ts_parameter table).
  3. Schema (parameter elements).

When a parameter has been loaded then it cannot be overwritten, first occurrence of a parameter wins. Examples on order of precedence:

 

Different parameters for different websites and web applications

Highstage supports that different websites and sub-applications runs the same or different code, database, web.config, parameters and schema.

In many situations a company will run the same code, database, web.config but slightly different parameters or schemas.

Different parameters (also SchemaFile parameter) for different web-sites and/or web-applications can be specified in web.config.

Consider the following IIS configuration:

Differentiation in parameters can be done in web.config. In the sample further down a prefix: specifies a web-site, sub-application or a combination.

For setting a parameter on highstage_internal web-site and all highstage_internal sub-applications use the prefix highstage_internal.

For setting a parameter on all sub-applications in all web-sites use no prefix and make sure the parameter is placed in top of web.config.

For setting a parameter on all ts_sales sub-applications in all web-sites, use the prefix ts_sales.

For setting a parameter on ts_sales sub-application in highstage_external web-site, use the prefix highstage_external/ts_sales.

 

Sample:

 

highstage_footer