configuration.properties
Location | <tomcat_home>\webapps\webapi\WEB-INF\classes\configuration.properties |
---|
The following properties are available in this configuration file.
SuperWEB2 Settings
Property | Description | More Information | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
global.enableUserRegistration | Whether to enable the built in user registration system:
The user registration system is disabled by default and will not appear as an option on the login page. Enabling it through this configuration activates the registration option, but the feature will not work without additional configuration (for example you need to configure the email server for sending registration messages). See User Registration for full details. | User Registration | ||||||||
global.enableMapView | Whether to display the Map View tab:
| |||||||||
global.enableGuidedTutorial | Whether to enable the guided tour:
| Customise the Interactive Tour | ||||||||
global.enableNewFeatureTutorial | Whether to enable the new features popup. This can be used to display information about new data or new features that have been added to SuperWEB2.
| |||||||||
global.enableGuestAccess | Whether to allow guest access to SuperWEB2:
| Configure Guest Access | ||||||||
superAdmin.zmq.address | The address for connecting to SuperADMIN. This should typically be left blank, in which case it will use the value from the AdministrationServerCatalog.xml file. | |||||||||
superAdmin.zmq.subscriptionPort | The subscription port for connecting to SuperADMIN. The default is 9002. | |||||||||
superAdmin.zmq.messagePort | The message port for connecting to SuperADMIN. The default is 9003. | |||||||||
superAdmin.zmq.reconnectionInterval | The time between subsequent attempts to reconnect to SuperADMIN if the connection is broken and the initial, immediate reconnection attempt fails. Specify the value as an integer, followed by one of the following units:
The default is | |||||||||
superAdmin.zmq.socketTimeout | The time to wait without receiving a heartbeat (or any other message) from SuperADMIN before resetting the underlying Specify the value as an integer, followed by one of the following units:
The default is | |||||||||
superAdmin.zmq.synchronisedStateTimeout | The time to wait without receiving a heartbeat (or any other message) from SuperADMIN before considering any cached state (such as the contents of the Open Data API cache) to be out of date. This value should be the maximum time you are willing to allow that state to possibly be out of sync with SuperADMIN when experiencing communication issues (for example for a permission change or deleted dataset to take effect). It should also be greater than the value of Specify the value as an integer, followed by one of the following units:
The default is | |||||||||
cube.showNaNAsZero | Whether to display 0 or a custom string if there are cells with no records contributing to the result:
| Configure Settings for Concealment and Cells with No Contributors | ||||||||
confidentiality.requireConfidentialityModule | Whether to prevent the release of datasets that do not have confidentiality modules applied to them.
| |||||||||
confidentiality.requireSpecificModules | Whether to prevent the release of datasets that do not have a specific Data Control API module applied to them. If any modules are specified, then users will only be able to access datasets that have at least one of those modules applied (the user must also have standard permission to access the dataset). This property accepts a comma separated list of modules. For example, the following prevents access to datasets that do not have either perturbation or the confidentiality rule modules applied to them:
CODE
| |||||||||
catalogue.sortDatabases | Whether to sort the list of Datasets shown in the catalogue screen:
| Change the Sort Order of Tables and Datasets | ||||||||
catalogue.databaseFolderExpansionDepth | How many levels of folders should initially be expanded when a user opens the Catalogue page in SuperWEB2:
| |||||||||
catalogue.infoPanel.displayDatabaseMetadataDescription | Whether to read the text for the catalogue page from the metadata database. This setting only applies when metadata server has been set up and is only used for datasets that have been set to
| Use the Metadata Server to Store the Data Catalogue Information Pages - SuperWEB2 | ||||||||
schemaTree.expandOnSelection | Whether to automatically expand a field in the tree when a user selects the Select all at level drop-down list. This property takes the following values:
| Automatically Expand the Fields when Selecting All | ||||||||
schemaTree.hierarchicalFieldDepthLimit | The maximum number of levels of hierarchy to show in the Select all at level drop-down list. Set this to a negative value if you do not want to limit the levels of hierarchy. The default setting is -1. | |||||||||
schemaTree.showSummationOptions | Whether to show the summation options in the customise table panel in Table View.
| |||||||||
schemaTree.selectAtLevelShowsValuesetName | Which labels to show in the Select all at level drop-down:
| Configure Field Drop-down Labels | ||||||||
schemaTree.schemaFolderExpansionDepth | How many levels of folders (field groups) to expand automatically when opening a dataset:
| |||||||||
table.showCurrentName | Whether to show the name of the currently open table in Table View (when opening a saved table):
| |||||||||
table.maximumFootnoteLength | When you have recodes (custom groups) in your table, a footnote automatically appears at the bottom of the table indicating which individual items make up the recode. You can use this setting to control whether this recode footnote is truncated. This setting specifies the maximum length of recode footnotes in a table prior to truncation. The default is 120. | |||||||||
table.annotations | Whether to display annotations beneath the table. This property takes the following values:
| Configure Display of Annotations | ||||||||
table.annotationPanelExpanded | Whether to automatically expand annotations. This property takes the following values:
| Configure Display of Annotations | ||||||||
table.defaultRSEView | The default display mode for tables with Relative Standard Error values. This property takes the following values:
| Configure Relative Standard Error | ||||||||
table.autoRetrieveDataDefault | Whether to retrieve data in Table View automatically by default:
| |||||||||
table.enableConcatenation | Whether to allow users to concatenate fields in tables:
| Disable Concatenation | ||||||||
table.enablePrintButton | Whether to display the Print Table button in Table View:
| |||||||||
table.enableAddToWafer | Whether to allow users to add fields to wafers in Table View:
| |||||||||
table.totalsInitialState | Whether to show totals by default when adding fields to the table or loading a saved table.
| Disable Automatic Totals | ||||||||
table.enableDrillUpAndDrillDown | Whether to allow users to drill up and down (navigate) through hierarchical fields in tables.
| |||||||||
table.useSavedTableLanguage | Whether to use the saved table language when opening a saved system table (a TXD saved from SuperCROSS and stored in the txd directory on the SuperWEB2 server).
| |||||||||
table.displayMetadataAsAnnotations | Whether to display metadata as annotations at the bottom of the table. This setting only applies to multilingual datasets that have been configured to use metadata server for descriptive metadata.
| Display Metadata as Annotations Below the Table | ||||||||
table.enableDerivations | Whether to allow users to create derivations in tables:
| Derivations | ||||||||
table.largeTableMode.previewDataSize | The number of row and column cells to show in the table preview when SuperWEB2 enter large table mode. You can set this property to any positive integer value. If you do not give the property a value, it will use the default (3). | Configure Settings for Large Tables | ||||||||
table.largeTableMode.thresholdTotal | The total cell threshold for entering large table mode. If the table has more than this number of cells, SuperWEB2 will enter large table mode. You can set this property to any positive integer value. If you do not give the property a value, it will use the default (100000). | Configure Settings for Large Tables | ||||||||
table.largeTableMode.thresholdRow | The row threshold for entering large table mode. If the table has more than this number of rows, SuperWEB2 will enter large table mode. You can set this property to any positive integer value. If you do not give the property a value, it will use the default (8000). | Configure Settings for Large Tables | ||||||||
table.largeTableMode.thresholdColumn | The column threshold for entering large table mode. If the table has more than this number of columns, SuperWEB2 will enter large table mode. You can set this property to any positive integer value. If you do not give the property a value, it will use the default (1000). | Configure Settings for Large Tables | ||||||||
recordview.maxCells | The maximum number of cells of data that a user can download at a time from Record View. You can set this property to any integer value. If you do not give the property a value, it will use the default (100,000). | Enable or Disable Record View | ||||||||
graphView.maxCells | The maximum size of a table that can be visualised in Graph View. By default, there is a limit of 1,000 cells; if users create tables with more than this number of cells then they will not be able to access Graph View. If necessary, you can increase the cell limit to a higher amount. The limit only applies to the number of cells in the currently selected wafer, not the number of cells in the table as a whole. | |||||||||
download.enableQueueManager | Whether to enable the Job Queue Manager. This property takes the following values:
| Configure JQM | ||||||||
download.allowDuplicateQueueManagerTableNames | Whether to allow duplicate table names in the job queue:
| Configure JQM | ||||||||
download.formatNumbers | Whether to format cell data in downloads. This setting is intended to be used if your users are working with extremely large tables (millions of cells), as it can provide a performance boost that dramatically reduces the time taken to download a table.
| Set Precision for Summation Options | ||||||||
download.enableOpenDataApiQuery | Whether to allow users to download a table as an Open Data API query.
| Use SuperWEB2 to Build API Queries | ||||||||
configServer.failOnUnknownProperties | What to do if any invalid or unknown SuperWEB2 configuration properties have been set using the SuperADMIN
| SuperADMIN cfg command | ||||||||
| These parameters define the URLs for the online help. You should not need to change these settings unless you want to replace the supplied user guide with your own customised version. | Customise the Online Help | ||||||||
metadata.scanForDescriptions | Whether to scan for metadata in the metadata database:
| Display Metadata Icons in the Field List | ||||||||
metadata.cacheSpec | The cache settings for metadata in SuperWEB2. By default, SuperWEB2 is configured to cache data from the Metadata Server for 1 day. You can change this by editing this setting. There are a number of options you can set (see http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/cache/CacheBuilderSpec.html for full details of the syntax), but the main change you are likely to want to make is to change how often SuperWEB2 automatically refreshes its cache. To do this, use the following setting:
CODE
Replace For example, the following setting configures SuperWEB2 to refresh its cache every 10 minutes:
CODE
| Clear Metadata Cache | ||||||||
externalLink.dataConfidentialityURL | The URL to link to from the data confidentiality footnote in Table View. | |||||||||
externalLink.metaInfoBaseURL | The base URL to link to for SuperWEB2 metadata. | Metadata | ||||||||
externalLink.loginURL | The URL of the SuperWEB2 login page. | |||||||||
login.requireTerms | Whether to show a terms and conditions screen during login. The user must accept the terms in order to log in.
| Add a Terms and Conditions Screen | ||||||||
login.guest.username | The username for the account to use for guest access. | Configure Guest Access | ||||||||
login.guest.password | The password for the account to use for guest access. | Configure Guest Access | ||||||||
externalLink.STRWebSiteURL | A link used in the standard footer section at the bottom of SuperWEB2. | Customise Header, Footer and Logo | ||||||||
graph.graphPdfTemplateLocation | The full path to the directory on the file system where the PDF template for graph downloads is located. You must escape any backslashes in the file path with an additional slash. For example:
CODE
If you leave this blank the PDF template will be loaded from the context directory (by default this is <tomcat_home>\webapps\webapi). | Branding PDF Downloads | ||||||||
graph.graphPdfTemplateName | The name of the PDF template file to use for graph downloads. Do not include the .pdf extension. For example:
CODE
If you leave this blank SuperWEB2 will expect the template file to be called SWDownloadGraph.pdf. | Branding PDF Downloads | ||||||||
externalLink.pdfTemplateFonts | A list of fonts to embed in the downloaded PDF, separated by commas. You may need to configure font embedding if your PDF template uses a font that is not one of the default Adobe fonts. If you use a non standard font, then you can embed this in the PDF to ensure that it will display correctly regardless of whether users have that font installed on their computer. Specify the full path to the font file. If you want to embed multiple fonts, use commas to separate them. For example:
CODE
| Branding PDF Downloads | ||||||||
kmz.author | The author name that will be embedded in KMZ files downloaded from Map View. | Branding KMZ Downloads | ||||||||
kmz.atomLink | A web link that will be embedded in the extended parameters field in KMZ files downloaded from Map View. | Branding KMZ Downloads | ||||||||
kmz.copyright | A copyright statement that will be embedded in KMZ files downloaded from Map View. | Branding KMZ Downloads | ||||||||
kmz.logoOverlayPath | The full path to the location of a logo image on the server. This will be embedded in KMZ files downloaded from Map View. | Branding KMZ Downloads | ||||||||
map.mapPdfTemplateLocation | The full path to the directory on the file system where the PDF template for map downloads is located. You must escape any backslashes in the file path with an additional slash. For example:
CODE
If you leave this blank the PDF template will be loaded from the context directory (by default this is <tomcat_home>\webapps\webapi). | Branding PDF Downloads | ||||||||
map.mapPdfTemplateName | The name of the PDF template file to use for map downloads. Do not include the .pdf extension. For example:
CODE
If you leave this blank SuperWEB2 will expect the template file to be called SWDownloadMap.pdf. | Branding PDF Downloads | ||||||||
map.mapPdfDocumentPropertyAuthor | The value to set for the Author document property in PDF map downloads. | Branding PDF Downloads | ||||||||
map.mapPdfDocumentPropertyKeywords | The Keywords to set in the document properties in PDF map downloads. | Branding PDF Downloads | ||||||||
map.mapPdfDocumentPropertyApplication | The value to set for the Application document property in PDF map downloads. | Branding PDF Downloads | ||||||||
map.mapPdfMaxCacheItemSize | The number of PDFs to cache on the server after generating them. | Branding PDF Downloads | ||||||||
map.mapPdfRastersSupportHttps | Whether the PDF service supports HTTPs calls to the base map server:
| Branding PDF Downloads | ||||||||
map.mapArcGISEndpointPattern | The pattern to use when setting the ArcGIS endpoint URI. This is used to extract the service name and layer index for caching. The default value is | Caching Map Data | ||||||||
map.mapCacheLocation | The location of the directory to store cache information for mapping. Make sure that the directory exists and that the user running Tomcat has permission to write to it. You must escape any backslashes in the file path with an additional slash. For example:
CODE
Forward slashes do not need to be escaped. For example:
CODE
If no directory is specified, then SuperWEB2 will use the default location: <tomcat_home>\work\Catalina\localhost\webapi | Caching Map Data | ||||||||
preferences.usersCanEditPreferences | Whether users can access the Account page options in SuperWEB2.
| Change the Sort Order of Tables and Datasets | ||||||||
preferences.usersCanChangePassword | Whether users can change their password in SuperWEB2 (via the Account page).
| |||||||||
preferences.usersCanDeleteAccount | Whether users can delete their account in SuperWEB2 (via the Account page).
| |||||||||
preferences.usersCanChangeContactPreferences | Whether users can opt in or out of email updates from the Account page.
| Regulatory and Privacy Compliance | ||||||||
preferences.allowContactDefault | Whether the default setting for the user contact preference is opt in or opt out:
| Regulatory and Privacy Compliance | ||||||||
csv.outputEncodingPreference | The output encoding to use for CSV files downloaded from SuperWEB2. By default, CSV files will be downloaded in UTF-8 encoding. You may need to change this to use a specific Windows codepage in some cases. For example, some versions of Microsoft Excel (including Excel 2003) have a bug that causes them not to support UTF-8 encoding when CSV files are opened either by double clicking the file or selecting Open from the download option in a web browser. If your users are experiencing problems opening downloaded CSV files in Excel, you may need to set SuperWEB2 to use a specific Windows codepage. See this page for a list of available codepages. When configuring SuperWEB2, you need to use the value from the Name column. For example, to use the Windows CP-1252 codepage, you would configure SuperWEB2 using one of the following values:
CODE
Or:
CODE
| |||||||||
numberFormat.enableCustomUDFValueFormat | Whether to use custom number formatting for values in range and quantile labels.
| Configure Quantiles and Ranges | ||||||||
numberFormat.customUDFValueFormat | The number formatting to use for values in range and quantile labels. See http://docs.oracle.com/javase/7/docs/api/java/text/DecimalFormat.html for details of how to specify the number formatting. Note that:
| Configure Quantiles and Ranges | ||||||||
udr.maxQueryParams | The size of chunks to use when connecting to the user data repository. Some relational databases have a limit on the number of parameters that can be used in the WHERE clause of a SELECT query. Queries that are likely to overrun this limit are broken up into chunks and run in parts to avoid errors. The default setting for this value is 1000, which should work for all supported databases. |
Open Data API Settings
The following settings apply to the Open Data API only. While they appear in the standard version of configuration.properties supplied with SuperWEB2, changing them in that version of the file will have no effect. The Open Data API has its own copy of the configuration.properties file (located in <tomcat_home>\webapps\webapi#rest#v1\WEB-INF\classes). If you want to configure the Open Data API then you must make the changes in the API's copy of the configuration file.
Property | Description | More Information | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
openDataApi.schema.pageSize | If a query to the Open Data API returns a large number of results then it will be paginated. By default, this occurs when there are more than 100 objects in the result set. You can use this setting to increase of decrease the limit for pagination. | Configure API Performance Settings | ||||||||
openDataApi.schema.numberOfRateLimitPerPeriod | The number of requests that any given API key can make within a one hour period. This property has been deprecated. It can still be used, but you are strongly recommended to remove this from your configuration and use the new | Configure API Performance Settings | ||||||||
openDataApi.table.maximumResponseCellLimit | The maximum number of cells that can be returned to a client via the | Configure API Performance Settings | ||||||||
openDataApi.table.maximumRequestItemLimit | The maximum number of field items that a user can query via the | Configure API Performance Settings | ||||||||
openDataApi.rateLimit.global | The number of requests that any given API key can make within a one hour period. If you do not want to impose any limits, set this to | Configure API Performance Settings | ||||||||
openDataApi.rateLimit.schema | The number of requests to the If you have also set a limit using the | Configure API Performance Settings | ||||||||
openDataApi.rateLimit.table | The number of requests to the If you have also set a limit using the | Configure API Performance Settings | ||||||||
openDataApi.auth.cacheSize | The maximum number of entries stored in the authentication cache. This cache is designed to speed up authentication in situations where the authentication process is slow (for example because the Open Data API and the authentication server are separated by a slow network connection). If the authentication process is fast, then you are recommended to disable the authentication cache by setting this value to The default is | Configure the Cache | ||||||||
openDataApi.auth.cacheExpiryTime | How quickly an authentication entry will expire from the cache. Specify the value as an integer, followed by one of the following units:
For example, The default is | Configure the Cache | ||||||||
openDataApi.table.cacheSizeUnits | The units to use when setting the size of the table cache. This setting applies to the value specified for the
| Configure the Cache | ||||||||
openDataApi.table.cacheSize | The size of the cache in either megabytes, gigabytes or total entries (depending on the value of To disable the table cache entirely, set this to The default is | Configure the Cache | ||||||||
openDataApi.table.cacheExpireAfter | Whether the cache expiry time is reset when a result is accessed from the cache:
| Configure the Cache | ||||||||
openDataApi.table.cacheExpiryTime | How quickly a table result will expire from the cache. Specify the value as an integer, followed by one of the following units:
For example, The default is | Configure the Cache | ||||||||
openDataApi.table.referenceType | Whether the table cache should use soft or hard memory references to hold its contents:
| Configure the Cache | ||||||||
openDataApi.schema.cacheSizeUnits | The units to use when setting the size of the schema cache. This setting applies to the value specified for the
| Configure the Cache | ||||||||
openDataApi.schema.cacheSize | The size of the cache in either megabytes, gigabytes or total entries (depending on the value of To disable the schema cache entirely, set this to The default is | Configure the Cache | ||||||||
openDataApi.schema.cacheExpireAfter | Whether the cache expiry time is reset when a query is accessed from the cache:
| Configure the Cache | ||||||||
openDataApi.schema.cacheExpiryTime | How quickly a schema result will expire from the cache. Specify the value as an integer, followed by one of the following units:
For example, The default is | Configure the Cache | ||||||||
openDataApi.schema.referenceType | Whether the schema cache should use soft or hard memory references to hold its contents:
| Configure the Cache |