Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


ProductAreaDescriptionMore Information
SuperADMINDisplay Options

For performance reasons, the displayoptions settings are now stored in the configuration server. Previously, these settings used an XML file (DisplayOptionsCatalog.xml).

Existing settings will be migrated automatically when SuperADMIN is upgraded, and no user action is required.

The command used to set and check these settings remains the same, although as part of this change, display options settings can now be set for record counts (previously they could only be set for measures).

SuperADMINMax Attempts and Account Locking

As a result of changes to the user catalogue (see below), there has been a minor change to the behaviour of the account locking feature.

Previously, changing the global settings for maxattempts and locktime only applied to new accounts. Now, changes to the global defaults will apply to all accounts unless you have specifically applied custom settings to individual accounts.

In addition, it is now possible to configure individual groups or users whose accounts cannot be locked.

SuperADMINPort UsageAs part of the implementation of user registration, SuperWEB2 communicates with SuperADMIN via a new REST API. If you want to deploy the user registration system then you must ensure that port 9001 is accessible.
SuperADMINUser Catalogue and Data Storage

For performance reasons, SuperADMIN now uses a relational database to store all user data (previously, it used an XML file). When you upgrade to version 9.9 SuperADMIN will automatically convert the existing user data to an H2 database, but you can .

It is possible to switch to another RDBMS, although this change should only be made before going into production. Please contact STR for advice if you wish to change the RDBMS for a production system.

SuperADMIN also uses a relational database H2 to store the configuration server data and data related to user registrations. Switching to another RDBMS will move all of this data in addition to the user data.

SuperSERVERAudit Logging

Some additional details are now recorded in the audit logs:

  • The SuperADMIN logs now record the client that generated the event.
  • SuperWEB2 now records the user's IP address on login events.
  • A unique job ID is now recorded for all events relating to a specific tabulation request. The same ID will be recorded in the SuperWEB2 and SuperSERVER log files.
  • The structure of the SuperWEB2 logs has been modified slightly: event types have moved to an action element and the query.part event type has been removed.
SuperSERVEROutput Scaling and Precision

The outputscaling data control module now supports:

  • Custom precision for individual measures.
  • Negative values for precision (negative values round values to the left of the decimal point; for example -1 will cause all values to be expressed as multiples of 10).

As a result of this change, an additional column (precision) has been added to the measures scale file.

SuperWEB2Direct URLs

The direct URLs feature has been extended. Previously if you wanted to link directly to a dataset you could construct a link that opens that dataset in Table View (/opendatabase?id=<dataset_id>). There is now an alternative option for linking to a dataset, which will take users to the dataset's info page (/openinfopage?id=<dataset_id>).

In addition, a new URL parameter (#db=<dataset_id>) has been added to allow you to link to other dataset info pages from within info pages.

SuperWEB2Graph ViewIt is now possible to configure specific colours for specific fields to be used in Graph View.
SuperWEB2Guest Access

A new configuration setting (global.enableGuestAccess) has been added to the file that allows you to disable guest access for a SuperWEB2 instance.

In addition, the username and password for guest access are now configured in the file, rather than web.xml.

SuperWEB2Large Table Mode

The thresholds for large table mode are now configured in Previously these settings were configured in CubeCatalog.xml.

In addition, the default total cell threshold for large table mode has been increased from 10,000 to 100,000.

SuperWEB2Mandatory Fields

Mandatory fields are now indicated in the field list by a small red * image that appears on top of the field icon and the field item icon.

A new configuration option has been added that allows you to specify whether mandatory fields will be automatically tabulated when opening a dataset.

SuperWEB2MetadataThe default metadata template supplied with SuperWEB2 has been renamed from sa-metadata.xhtml to metadata.xhtml. If you wish to continue using the default template you will need to update the settings in your file to match the new location (please also note that, as documented above, the path to this file changed from /webapi/help/ to /webapi/jsf/help/ in version 9.8).
SuperWEB2PreferencesThe Preferences page has been renamed to Account and now has additional options for users to change their password and delete their account. New settings have been added to the file that allow you to turn off these settings.
SuperWEB2Saved Tables and DatasetsSuperWEB2 now displays a tool tip when you hover the mouse pointer over a saved table on the dataset catalogue page. This can be particularly useful if you have tables with very long names, as it is no longer necessary to use the horizontal scrollbar to see the full table name.
SuperWEB2Table Download as Open Data API Query

A new download format has been added to the Download Table drop-down menu in Table View: you can now download the table as an Open Data API query.

Selecting this option will download a text file containing JSON that you can pass in to the API in a table query. This feature is designed to make it easier to set up your API queries, as you can now use the SuperWEB2 drag and drop interface to design your queries and then easily reuse these in the application you are building with the API.


Some table features are not supported by this download option. Learn more.

SuperWEB2User Registration

SuperWEB2 now has an automated user registration system, designed to make it easy to allow users to sign up for an account on your SuperWEB2 deployment, set their own password, and change or reset their password.

As part of this change, users can now change their password and delete their account from the Account page (accessible from the top-right menu).