4.4 Specifying Data Source Information

The 'Configuration' > 'Datasource/Lib' page allows you to set the location of the following repository files:

datasource.xml: Database connection information, data model definitions, and VPM configuration.

query.xml: Query definitions.

stylereport.srl: Reusable report components, such as parameter sheets, table styles, script functions, beans, etc.

 

The 'Query variable names are unique' option allows you to specify whether a variable name that is used in multiple queries or binding conditions should be treated as unique or non-unique. If unique, the report or Viewsheet accepts a single value to be re-used across all variable occurrences (and the user is prompted only once for this value). Otherwise, the report or Viewsheet accepts a distinct value for each occurrence (and the user is prompted once for each occurrence).

If you make a change to your database schema, select the corresponding data source in the 'Metadata' menu, and click 'Refresh Metadata'. (Select 'All' to refresh metadata for all listed data sources.) This will allow schema changes to be reflected in the listing under the 'TABLE' node of the Visual Composer Asset panel.

Connection Pool

The query engine uses connection pooling for enhanced database performance. The 'Connection Pool' option allows you to specify the type of connection pool to use for managing connections to JDBC data sources. Use the 'Application Server' connection pool if your webapp server is running other applications (in addition to the sree webapp) that also require database connections. Otherwise, use the 'Report Server' connection pool to allow Style Intelligence to manage the connections.

Supported applica­tion servers are Tom­cat, WebSphere, and WebLogic.

If you select the 'Application Server' connection pool, each data source name that you define in Style Studio must match a corresponding JNDI lookup name in your application server.

Note also that the 'Application Server' connection pool option will not apply to the Scheduler, as the Scheduler runs in an independent JVM and cannot access the application server connection pool. (See the Scheduler section for more details.)

The default size of the pool is five connections. For enterprise level deployment, the number of connections can be increased to a more appropriate size by setting the property jdbc.connection.pool.size in sree.properties.

jdbc.connection.pool.size=50

If you select a 'User Defined' connection pool, you must enter the fully qualified class name of the inetsoft.uql.jdbc.ConnectionPool implementation in the provided text field, and the class must be accessible from the web application's classpath. See Pooling Database Connections Programmatically in Integration for more information.

See Also

Pooling Database Connections Programmatically, in Integration, for finer grained control over pooling.

Creating a New JDBC Data Source, in Data Modeling, to configure and name a data source.

<< 4.3.7 Using a Clustered Environment © 1996-2013 InetSoft Technology Corporation (v11.5) 4.5 Configuring Database for Audit/Data Space >>