This article applies to the Admin Console > Storage Management settings.
The path and filename of the DLL that implements the
IStorageManagement interface. The default value is <WebApp>\bin\WebReports.ContentDatabase.dll, which will use Exago's Storage Management implementation, where <WebApp> represents the Web Application's installation directory.
Provide the fully qualified path to the file. If no path is supplied, Exago will check the Web Application's
\bin directory for the DLL.
The name of the class in the assembly that implements the
IStorageManagement interface. The default value is WebReports.ContentDatabase.StorageMgmtDatabase, which will use Exago's Storage Management implementation.
Click the Validate Assembly icon to validate that the assembly exists and that all methods of
IStorageManagement can be found by Exago in that class.
Out-of-the-box, Exago provides a SQLite implementation of the Storage Management database. The default values noted for each setting below reflect the default SQLite installation.
Exago recommends using the included SQLite database for development, testing and demonstration purposes only. Use MSSQL, MySQL, Oracle or PostgreSQL in a production environment.
Choose the type of the Storage Management database:
- SQLite (default value)
- MSSQL — Microsoft SQL Server
Specify the name of the database provider Exago will use to connect to the Storage Management database. This matches the InvariantName found as a property of DbProviderFactories in the server's
machine.configfile is located in the
The default value is SQLite.
Use the applicable database provider name from the Admin Console > General > Database Settings.
Connection string Exago will use to connect to the Storage Management database.
Default value for SQLite is Data Source=<FILENAME>. Replace <FILENAME> with the absolute path and file name to the database file. For example:
For PostgreSQL, include
Unicode=true in the connection string.
Review Storage Management: Database Schema and Storage Management: Introduction for more information about the purpose of each of these tables. Each table name may also include a schema (e.g. dbo.content).
Provide an optional prefix for all Storage Management database tables. Review the Storage Management: Database Schema article for information. This option can be used to add a schema if it exists.
test_will result in tables named test_content, test_party_type, test_content_access and test_storage_meta
dbo.will result in tables named dbo.content, dbo.party_type, dbo.content_access and dbo.storage_meta
Check Database Settings
Click to check the connection between Exago and the Storage Management database. Also checks that the tables exist in the database.
Prepare Database (SQL)
Click to display the SQL statements that will initialize a Storage Management database with the schema and default party types. Works similar to the Prepare Database button but will display the SQL statements on screen instead of executing them.
This button will also show any SQL statements needed to update the schema if necessary on an existing database.
Click to create the four Storage Management tables, load default party types into the Party Type table and create the Public and My Reports folders if they don't already exist.
This button will also update the schema if necessary on an existing database. It is not destructive.
Click to load chart, ExpressView, CrossTab and GeoChart themes from the
<WebApp>\Themes folder into the Storage Management database.
This is only necessary for first time installations of Exago or after upgrading to Storage Management from a legacy storage mechanism and themes were not imported with one of the transitioning utilities.
The Storage Management Identity keys are used similar to the system-wide @userId@ and @companyId@ parameters but only affect content storage. Like @userId@ and @companyId@, they should be set each time an Exago session is created via the API.
The settings here can be used for testing and demonstration purposes. Review the Storage Management: Introduction and Storage Management: Database Schema articles for more information on how these keys are used in the application.
Set a value for the Class Id identity key.
This is similar to, but is not the same as the system-wide @companyId@ parameter.
Set a value for the Company Id identity key.
This is similar to, but is not the same as the system-wide @userId@ parameter.
Set a value for the User Id identity key.
When accessing Storage Management properties through the Admin Console (e.g. when viewing Role Folder Permissions) all access filters will be removed and all content will be available.
Set the value for Owner Id. When the Owner Id of a content item matches the value of the Owner Id identity key, full access is granted to that content item automatically.
Default Settings & Content Access Permissions
The default settings determine how permissions are configured for newly created content in the root.
Individual folders have their own inherit flag, default party type and default access flags properties. The settings here affect only new content created in the root. If for some reason individual folders do not have their own inherit flag, default party type or default access flags set (i.e. they are null) then the values here will be applied.
Set the default value of the Inherit Flag.
If True, new folders created in the root will have their inherit flag set to true. When a folder's inherit flag is true, new content created in that folder will copy all of the access records from its parent.
If False, new folders created in the root will have their inherit flag set to false. When a folder's inherit flag is false, new content created in that folder will have a single new content access record written with the default party type and default access flags.
Default value is True.
This setting determines the value of the Inherit Flag on child folders of the root. Folders created in the root do not copy the access records from the root folder. Instead, a single content access record with the Default Party Type will be written for new folders in the root.
Set the default party type for newly created folders in the root. Regardless of the value of Party Type, new folders created in the root will have their default party type set to this value.
When Inherit Flag is True, this dropdown is disabled as content access records will be inherited from the content's parent and therefore will not have an effect.
Set the default access flags that will be used for newly created content when not inheriting access from the parent objects. Choose from:
- Full Access — there will be no restriction on access to content
- Read Only — content is marked as read-only in a similar way to Roles. When content is read-only, it cannot be edited, saved or deleted. Read-only folders cannot have new content saved into them. Read-only reports can be duplicated into non-read-only folders.
- Custom — a different content access strategy can be implemented by manually editing the XML configuration file and providing a value in the
Each of the access flags are defined in the Storage Management: Introduction article. CanView, CanSave and CanEdit are implemented now. The other flags are not yet active and will be implemented in a future release.
Enable Report List Caching
This setting was formerly located in General > Other Settings.
Set to True to enable the folders and report list in the Report Tree to be cached, rather than querying the Storage Management database each time they are needed. Default value is True.
It is recommended to enable Report List Caching, even with a small timeout. Care should be taken when running Exago in a web farm environment, as the caches will become unsynchronized.
If Enable Report List Caching is True, set the timeout in seconds that the folder and report list cache should expire. Default value is 30 seconds.
Enable Report XML Caching
This setting was formerly located in General > Other Settings.
If True, the XML report definition content will be cached rather than being read from the database each time it is needed. Enabling this setting will reduce the number of calls to the Storage Management database and may help with performance. Default value is True.
It is recommended to enable Report XML Caching, even with a small timeout. Care should be taken when running Exago in a web farm environment, as the caches will become unsynchronized.
If Enable Report XML Caching is True, set the timeout in seconds that the folder and report list cache should expire. Default value is 30 seconds.
Theme List Caching Timeout
Set the timeout in seconds that the report and chart theme cache should expire. Default value is 30 seconds.