i-net Clear Reports

Session Datasource Plugin

If you create a datasource in i-net Clear Reports then normally, all users see the same data with it. If you want different users to see different data for the same report then you can filter the data of a report in the record selection formula depending on the logged in user. Or you could set your server to use a database login and use the class “LoginDatabase” which causes your report to use the same database connection as the one for the current user.

Another solution are session datasources. A session datasource exists only during the runtime of the logged in user.

This sample demonstrates a javax.servlet.Filter which creates a session datasource with the name datasource, pointing to a MySQL database. The URL request parameters user, password, host, port and database must be set and will be used to create the datasource.

Important: Use this sample only inside a backend server which is protected from a frontend server. It would be unsafe to be injecting these credentials from outside of your intranet.

Activate the included plugin

If you want to try this plugin then you need to copy the file sessiondatasource.zip of this sample in the plugins folder of your server installation and restart the server.

If you want to write your own filter then you need to create an instance of javax.servlet.Filter similar to the one in the sample. For more information please see the source files of this sample and the chapter Platform Programming Guide | Plugins in the Help of the SDK.

Server Plugin

In the next step you write your own server plugin. It must implement the interface com.inet.plugin.ServerPlugin and have an empty public constructor for loading. In the method registerExtension you must register both of your classes. This can look like:

public void registerExtension( ServerPluginManager spm ) {
    spm.register( Filter.class, new MyFilter() );

Please refer to the sample com.inet.session.datasource.SessionDatasourcePlugin to see how this is done there.

Build the plugin

The following steps need to be taken if changes are made to the plugin code.

The plugin.properties and server plugin class are preconfigured to be used without modifications. If the sample is the basis for a custom plugin or just needs some adaptions, please refer to the platform programming guide for detailed instructions.

Collect the required jar files

In order to build this plugin the following jar files are required at minimum:

  • inetcore.jar (included in the core directory)
  • javax.servlet-api.jar (included in the core directory)
  • reporting.jar (included in the plugins/reporting.zip file)

You can copy these to the current sample directory or link them into the project of your IDE.

Build the plugin

The plugin must be compiled into a jar file that is named like the id of the plugin. In this example it is sessiondatasource.jar. It also must contain the compiled sources as well as required language resources and images.

The target plugin is a zip file, named sessiondatasource.zip in this example. It contains the compiled jar file and the plugin.properties which configures the custom plugin.

The provided build.gradle in the sample can be used to build the plugin as well as any other build system.


Copy the ZIP file of the plugin into the plugins directory of the server and restart it. If there are problems, then check the log file of the server for more details. The “Config” logger is used to log plugin registration issues.


© Copyright 1996 - 2021, i-net software; All Rights Reserved.