Loading Configurations

The report engine i‑net Crystal-Clear and the i‑net Designer will search for it's configuration in a predetermined order.
As soon as a configuration is found, it is used until the configuration is changed in any way. In this case, the configuration is reloaded as soon as a new report is requested.

In order to choose which configuration you wish to use in i‑net Designer, select the menu item “File → Designer Options”. In the tab “Options” you can choose the configuration to use in i‑net Designer. To create, modify, delete, copy, import, and export configurations choose the menu item “File → i‑net Crystal-Clear Options”. With the “Activate” button you can choose the configuration that will be used for the current session of the i‑net Designer.

The i‑net Crystal-Clear listener will search for it's configuration in the following order. As soon as a configuration is found, it is used until the configuration is changed in any way. In this case, the configuration is reloaded as soon as a new report is requested.

1. If the Java system property “crystalclear.config” has been set, it's value is used to locate a configuration. This name must have “USER” or “SYSTEM” as it's prefix and then have the configuration name after a slash, for example:
   ”-Dcrystalclear.config=USER/myconfig”
   ”-Dcrystalclear.config=SYSTEM/mysystemconfig”
2. If the Java system property “crystalclear.configfile” has been set, it's value is used to locate a crystalclear.properties file. This file is then imported and used as a temporary configuration called ”<temp copy>”, for example:
   -Dcrystalclear.configfile=crystalclear.properties”
3. A configuration called “Default” in the User scope.
4. A configuration called “Default” in the System scope.
5. A configuration called ”<Temporary Default>” in the Temporary scope.

If none of the above configurations could be found, a temporary, empty configuration is created and set. Note that this configuration will only have default configuration values and no license key, so it will not be possible to display reports with a listener running with this temporary configuration. To change the configuration a listener is using once it is running, you can use the API of ConfigurationManager, e.g. ConfigurationManager.setCurrent(Configuration).

The i‑net Crystal-Clear servlet will search for it's configuration in the following order.

1. There are two init parameters for the servlet in the web.xml. The first one has the name “crystalclear.config”. This enables you to set the configuration you wish to use. It's value format is the same as for the listener: the name must have “USER” or “SYSTEM” as it's prefix and then have the configuration name after a slash, e.g.: “USER/myconfig” or “SYSTEM/mysystemconfig”.
   If this first init parameter was not set or did not point to a valid configuration, the second init parameter is “crystalclear.configfile” and can specify a crystalclear.properties file with it's full absolute path. This file is then imported into a temporary configuration called ”<imported config>”.
2. The Java system parameters are checked for the same properties as for the Listener. Please consult the documentation of your application server for how to set Java system properties.
3. A configuration called “Default” in the User scope.
4. A configuration called “Default” in the System scope.
5. A configuration called ”<Temporary Default>” in the Temporary scope.

If none of the above configurations could be found, a temporary, empty configuration is created and set. Note that this configuration will only have default values and no license key, so it will not be possible to display reports with a servlet running with a temporary configuration.

You can use the Configuration Manager without gui to import an i‑net Crystal-Clear configuration or a Data Source configuration with command line parameters, for example:

java -jar core/crystalclear.jar -importConfig System/Default crystalclear.properties
This command imports the properties file into the permanent configuration called “Default” in the System scope).

• System Properties
• Command Line Parameters