User Queries Installation


Learn how to save Standard Edition report configurations to a database.

Pull Reports™ supports saving a user's queries to a database. The Standard Edition license supports infinite user queries per user while the Community Edition license restricts user queries to ten per user.

Activating user queries requires creating the user_queries table and setting configuration properties. After the following steps are complete, Pull Reports™ will automatically enable user queries upon redeployment.

Create the user_queries table

Pull Reports™ stores user queries in a table called user_queries. Use the following scripts to create the table, indexes, and sequences in your database of choice.

By default, Pull Reports™ assumes that user_queries will exist in a table namespace (also called schema or user) called pullreports such that the full path to the table is pullreports.user_queries. However, you may create user_queries in any namespace you choose and override the schema name via the system.userQueriesSchema configuration property.

Specify a DataSource

User queries use a separate JNDI DataSource configuration from reports. Provide the JNDI resource path to the javax.sql.DataSource implementation via the system.jndiDataSource configuration property. This DataSource must have select, insert, update, and delete privileges on the user_queries table.

Specify a UserProvider

Pull Reports™ must know the user identifier of the user persisting a user query. By default, Pull Reports™ uses the username from HttpServletRequest#getRemoteUser. Override this implementation via the system.userProvider configuration property.