basicweb
This configuration is required when using the plugin Cadenza.
-
Documentation
-
YAML Format
-
XML Format
| Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets. |
This is basic configuration for Cadenza Web.
A simple configuration could look like:
<basicWebConfiguration>
<publicCadenzaUrl>http://localhost:8080/cadenza</publicCadenzaUrl>
<management>
<maxConcurrentUsers>10</maxConcurrentUsers>
</management>
</basicWebConfiguration>
ISO 8601 Duration Format
Format: P[n]Y[n]M[n]DT[n]H[n]M[n]S
- P is the duration designator (period) placed at the start of the duration representation
- Y is the number of years
- M is the number of months
- D is the number of days
- T is the time designator that precedes the time components
- H is the number of hours
- M is the number of minutes
- S is the number of seconds
Examples:
PT5M- 5 minutesPT1H30M- 1 hour and 30 minutesP1D- 1 dayP1Y2M3DT4H5M6S- 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds
This is the duration that items will be kept in the QueryResultCache for a particular datasource if no specific timeout is defined on the datasource itself.
Default: PT5M
This is the message key that will be used to look up a localized name for this menu entry.
The printNameKey will be resolved against the custom message properties that you can customize
(see Customizing Message Properties ) to return an
appropriately localized name.
This is the message key that will be used to look up a localized URL for this menu entry.
Alternatively you can configure a url directly.
The urlKey will be resolved against the custom message properties that you can customize
(see Customizing Message Properties ) to return an
appropriately localized name.
A URL is required for URL type menu entries.
If you have a HELP type menu entry and no URL is provided, it will default to /help/.
This configures one entry to appear in the "help" menu of Cadenza. We support different types of
menu entries (HELP, URL and KEYMAP) and depending on the type certain settings are either
required or optional:
-
For
HELPmenu entries aprintNameKeyis required -
For
URLmenu entries aprintNameKeyis required as well as aurlorurlKey -
For
KEYMAPmenu entries neither aprintNameKeynor a URL is required. This is a special menu entry that triggers a popup with all the available keyboard shortcuts.
This is the Content-Security-Policy configuration for Cadenza. This configuration governs how a set of HTTP headers is sent to the browser to regulate a few security settings.
The frame-ancestors configuration allows Cadenza to defend itself against
Clickjacking attacks.
Cadenza defends itself against this by setting the frame-ancestors directive
of the Content-Security-Policy header to self. This prevents Cadenza from
being embedded in sites other than itself.
If you want to allow Cadenza to be embedded into a site on another origin, then
you need to configure the origin of that site as a frame-ancestors source in
this configuration.
You can enable or disable the `Content-Security-Policy` entirely with this flag. This should *not* be disabled in production.
Default: true
Externally reachable base URL of the Cadenza installation (e.g. “https://disy.net/cadenza”), e.g. for notification emails. Mandatory if such functionalities are in use.
With cluster operation, the URL of the load balancer must be specified as the base URL and work with “sticky sessions”. If Cadenza is not called directly, but only via a custom application in which Cadenza is integrated, the URL of the custom application must be specified as the base URL.
For more information see Public Base URL
Defines a set of labels. Example of use: The URL to the Cadenza home page can be parameterized to prefilter the Navigator content according to the specified labels, e.g. http//localhost/cadenza/?labelSet={NAME}. Users can remove or change the filter settings as required.
| This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. |
cadenzaconfig:
settings:
basicweb:
management:
maxConcurrentUsers: 15
defaultDatasourceMaxCachingAge: "P2DT3M"
maxUploadFileSize: "text"
layout:
userSpecific: true
appearance:
menuEntries:
- id: "help"
printNameKey: "text"
url: "text"
urlKey: "text"
- id: "help"
printNameKey: "text"
url: "text"
urlKey: "text"
csp:
frame-ancestors:
enabled: true
source:
- "text"
- "text"
publicCadenzaUrl: "text"
labelSets:
- name: "text"
label:
- "text"
- "text"
- name: "text"
label:
- "text"
- "text"
Filename: basicweb-config.xml
| This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. |
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<basicWebConfiguration>
<management>
<maxConcurrentUsers>15</maxConcurrentUsers>
<defaultDatasourceMaxCachingAge>P2DT3M</defaultDatasourceMaxCachingAge>
<maxUploadFileSize>text</maxUploadFileSize>
</management>
<layout userSpecific="true"/>
<appearance>
<menuEntries>
<menuEntry id="help">
<printNameKey>text</printNameKey>
<url>text</url>
<urlKey>text</urlKey>
</menuEntry>
<menuEntry id="help">
<printNameKey>text</printNameKey>
<url>text</url>
<urlKey>text</urlKey>
</menuEntry>
</menuEntries>
</appearance>
<csp>
<frame-ancestors enabled="true">
<source>text</source>
<source>text</source>
</frame-ancestors>
</csp>
<publicCadenzaUrl>text</publicCadenzaUrl>
<labelSets>
<labelSet name="text">
<label>text</label>
<label>text</label>
</labelSet>
<labelSet name="text">
<label>text</label>
<label>text</label>
</labelSet>
</labelSets>
</basicWebConfiguration>