The following chapters describes the various things to know when migrating from older versions of i-net Crystal-Clear to version 10.x of i-net Crystal-Clear.
Depending on the API and/or components you use, some of these changes may create the need for you to customize or change your usage of i-net Crystal-Clear when migrating to version 10.x – either in order to take advantage of new features, or perhaps because the original way of doing things may not work any more at all (for example if you were using deprecated API methods).
The following list includes the methods that are deprecated in version 10 and should no longer be used. Please consult the API documentation of the individual methods for more information about newer methods to use instead.
The following list includes the methods that have been entirely removed in version 10 of i-net Crystal-Clear.
The following methods had been deprecated for longer than 2 major versions and have now been entirely removed in version 10 of i-net Crystal-Clear.
The directory structure in the installation directory has been changed. The directory “crystalclear” has been replaced with 2 new directories: “client” and “core”.
The directory “core” contains all library files of the root class path and the “lib” directory contains contains library files, which can be loaded dynamically. The directory “client” contains resources for the i-net Crystal-Clear client, e.g. the new HTML parameter request dialog.
If a report element has a border and/or shadow and the lower border of the report element is exactly on the lower edge of a section, then the height of this section is increased at runtime by the width of the border and / or shadow.
In previous versions, the border and/or shadow was painted into the next section. To use this behavior of the older versions with version 10, you need to set the value of the property “Compatibility Level” to “compliant to version 9.x”.
The behavior of the section property “Suppress Blank section” has been changed. If this property is enabled, an emtpy section will be suppressed. A section is emtpy, if it does not contain dynamic data.
That means, the section will be suppressed if the following report elements does not contain any data:
and no chart, crosstab, Java Bean or subreport is displayed.
The following elements does not effect this property:
For security reasons the property “Allow unknown Data Sources” has been added to the configuration category “General Options”.
If this property is disabled, then it is not possible to execute reports containing an unknown datasource. A data source is unknown, if no data source configuration exists with this name on the report server. This will prevent that each user has the possibility to load data from external databases.
Since version 10, the new default (and recommended) value for the property “Max HTTP Requests” is 250. Because of a bug in channel handling of various Java VMs, i-net Crystal-Clear report server now uses sockets instead of channels and therefore requires more threads. The previous default value of 8 would now actually decrease performance of the report server.
If the current value of this property is less than 50, then the setup increases it to 250 during the installation of version 10.
If the current value is already between 50 and 250, then it is necessary to manually set the value to 250 if this default is desired.
Single string parameter fields (prompts) which do not have any length limit now accept null in addition to an empty string. In the prompt dialog, they have a “no value” option which can be toggled on and off for the string prompt.
If you do not want to allow null values for string prompts, you can simply specify 0 as the minimum length of the string - note that in the i-net Designer, this is now the default setting when creating new string prompts.
Up to now the password form of the Remoter Interface appears, if report permissions and/or system permissions are enabled and no login script was specified in the configuration (see Security Guide for more details).
Since version 10, i-net Crystal-Clear supports several authentication methods. The property Login Type defines, how the user has to log into the system and where the permitted user names are administrated.
The default value of the Login Type is: Automatic. In this case, the server tries to request the login in the following order: External Webserver (URL of Login Script must be set), Windows Authentication (if the server is running on a Windows operating system), Internal Webserver, Master Password.
To use a specific authentication method, you need to select it in the Configuration Manager, property: Login Type in the category System Permissions.
The cluster feature of i-net Crystal-Clear Plus has been removed. Operating system or application server clusters should be used instead.
Reports created with Crystal Reports version 6 are no longer supported. If you have such reports, then you will have to open and save these reports either with a newer Crystal Reports version or with a previous version of i-net Designer.