The following chapters describe the various things to know when migrating from version 21.x of i-net Clear Reports to version 22.x. If you migrate from older versions of i-net Clear Reports, then you should also read the other migration information depending on the version that you migrate from.
The following chapters describe the various things to know when migrating from version 20.x of i-net Clear Reports to version 21.x. If you migrate from older versions of i-net Clear Reports, then you should also read the other migration information depending on the version that you migrate from.
The initialization for WebSocketEndPoint to be registerable in Oracle Weblogic was changed in version 21.10. This fixed the error `java.lang.IllegalStateException: Not in 'deploy' scope.`.
If you use an web.xml file of another WAR file you need to add the listener com.inet.http.ExpandableServletContextListener
The following chapters describe the various things to know when migrating from version 19.x of i-net Clear Reports to version 20.x. If you migrate from older versions of i-net Clear Reports, then you should also read the other migration information depending on the version that you migrate from.
The internal structure has changed. That is why the new plugin reporting
(file: plugins/reporting.zip
) is now mandatory to start i-net Clear Reports. Due to this change the previous startup scripts are no longer valid and have to be changed.
In addition, the i-net Designers plugin remotedesigner.zip
has been renamed to designer.zip
.
If manual changes were made to the startup scripts, they have to be updated accordingly:
java -cp core/ClearReports.jar com.inet.report.ClearReportsServer
java -jar core/inetcore.jar
java -jar core/designer.jar
java -jar core/inetcore.jar designer
java -jar core/ClearReports.jar -forceImportConfig ...
java -cp core/inetcore.jar com.inet.config.recovery.RecoveryConfiguration -forceImportConfig ...
*.war
or *.ear
: the servlet class has to be changedcom.inet.report.ReportServlet
com.inet.http.PluginDispatcherServlet
. See the reference war
file for details.
Note: Developers who utilise API classes such as com.inet.report.Engine
from the reporting.jar
have to extract this jar file from the reporting.zip
plugin now.
com.inet.report.ReportServlet
has been removed. If there were extensions from the previously deprecated API, then they have to be moved to a plugin, registering an extension now.BytesFromFile
and TextFromFile
now limits access to files to prevent a path traversal for normal users. The specified file must be from a valid report location, and if it is located in the file system then it must be from the same directory or subdirectory as the report itself.com.inet.report.PropertiesChecker
can not be added to the lib
directory anymore. They have to be implemented using a plugin. See <SDK>\Documentation and Samples\Plugin - Samples\PropertiesChecker
for an example plugin.javax.servlet.Filter
can not be added to the lib
directory anymore. They have to be implemented using a plugin. See <SDK>\Documentation and Samples\Plugin - Samples\ SessionDatasource
for an example plugin.com.inet.report.Listener
class has been removed. The web server has not been started by this class since version 15.x. The web server is started using the plugin webserver.zip
.The following chapters describe the various things to know when migrating from version 18.x of i-net Clear Reports to version 19.x. If you migrate from older versions of i-net Clear Reports, then you should also read the other migration information depending on the version that you migrate from
Server Printers
plugin enabled users will not be able to use the server printer after upgrading to version 19. They will have to have group permissions assigned to regain access to server printersThe following chapters describe the various things to know when migrating from version 17.x of i-net Clear Reports to version 18.x. If you migrate from older versions of i-net Clear Reports, then you should also read the other migration information depending on the version that you migrate from.
/remote
context of the Remote GUI has been removed. Applications beneath this entry point have been moved up one level.