|#1 Ranking: Read how InetSoft was rated #1 for user adoption in G2's user survey-based index
Configuring the Report Data Source
The 'Configuration' > 'Datasource/Lib' page allows you to set the location of the following registry files:
- datasource.xml: Database connection information and data model definition.
- query.xml: Query definitions.
- stylereport.srl: Reusable report components.
The 'Query variable names are unique' option allows you to indicate whether repeated query variable names should be treated as unique (and utilize a common prompt).
The 'Connection Pool' option allows you to specify the type of connection pool to use for JDBC data sources. If you select the 'Application Server' connection pool, the data source names in the data source registry file must match a corresponding JNDI lookup name in your application server. Supported application servers are Tomcat, WebSphere and WebLogic. If you select a 'User Defined' connection pool, you must enter the fully qualified class name of the ConnectionPool implementation in the provided text field, and it must be accessible from the web application's classpath.
View a 2-minute demonstration
of InetSoft's easy, agile, and robust BI software.
Note that the 'Application Server' connection pool option will not apply to the Scheduler, as it runs in an independent JVM and cannot access the application server connection pool.
You can use a database for persistent storage of the following items:
- Data space (report templates, datasource.xml, query.xml, etc.)
- Asset repository
- Audit Records
The following databases are supported: Oracle, DB2, SQL Server, and Derby.
To configure a database for persistent storage, open the 'Configuration' > 'Database' page, and specify the database type, connection information, and the transaction isolation level.
The storage of these elements can be configured on the 'Data Space' and 'Audit' pages under the 'Repository' node.
Note: The cache and temporary files cannot be stored in a database.
The 'Default DB' field indicates the name of the database schema to be used. If left unspecified, the default database schema for the particular user profile will be used. Once the required information for the database is specified, the connection can be tested by clicking on the 'Test Connection' button.