A3. PostgreSQL is not supported for use with IUCLID 6. The only databases supported are JavaDB/Derby (free, as in no charge) and Oracle (commercial). For more information about software requirements please refer to the documentation section of this website.
A4. Tomcat is not supported for use with IUCLID 6. This is one of the major technical changes between IUCLID 5 and IUCLID 6. The Tomcat application server is replaced by GlassFish (version 3.1.2 or 4).
A5. Details of the operating systems tested and supported by ECHA are available on the system requirements page of the IUCLID website.
A6. Yes. IUCLID 6 Desktop is available for macOS from the download page of the IUCLID website.
Installation and system configuration
A9. Indeed, you should still use the version 5.6 of IUCLID to prepare dossiers for submission to ECHA for example, until the update of ECHA's submission tools. However you can install and migrate your data to IUCLID 6 already now. The migration from IUCLID 5 to IUCLID 6 copies data from one system to another so both systems can be used in parallel. Once the submission systems are updated to accept IUCLID 6 files, a final migration from IUCLID 5 to IUCLID 6 will have to be performed.
A22. This depends on whether users have been migrated from IUCLID 5 and whether the password of user SuperUser was changed via the Windows installation wizard. If neither of these were done, use the following credentials to log in to IUCLID 6 for the first time:
All credentials are case sensitive. For non-administrative use of IUCLID 6 it is recommended to use a user other than SuperUser. You can create new users whilst logged in as SuperUser.
IUCLID 6 Desktop version now also offer the option to work without user management. In that case the login step is by-passed.
If you have installed one of the IUCLID 5 Portable versions, please note that the credentials to login are admin / admin
A23. Technically it is possible to install IUCLID 5.6 Distributed and IUCLID 6 Server side by side on the same server. To do it you must first ensure that Tomcat (IUCLID 5) and Glassfish (IUCLID 6) use different ports. Such configuration should be used for test purposes only, because we do not support this for production.
To install IUCLID 6 Server, follow the steps from the installation manual which can be downloaded here.
A46. In case you do not remember which version of IUCLID is installed, you can download a small executable file to find out. Here is how to check your IUCLID 6 version:
- Download the IUCLID 6 version checker
- Extract the file to your IUCLID 6 installation folder, as below
- Execute the file by double-clicking it
- For a 32-bit version you should obtain the following result
- For a 64-bit version you should obtain the following result
Please note that there is only one updater provided for IUCLID 6 that will update your existing IUCLID 6 Desktop installation to the latest one, whether it is a 32-bit or a 64-bit installation.
A48. The following problems can be caused by insufficient system memory (RAM) being available to IUCLID 6 or its associated software tools:
- IUCLID 6 or a tool does not start;
- Unusually slow performance, especially when large files are handled;
- The error “Out of Memory exception” is output either to log files or the command line.
To avoid these problems, and to use resources most efficiently, consider the total RAM available to the computer, and how it is allocated to IUCLID 6 and each of its software tools. The recommended system resources for IUCLID 6 are stated here. Many problems like those given above can be solved simply by changing the values of certain system parameters in settings files. A detailed guide to memory management for IUCLID 6 and its tools, aimed at non-IT specialists, is provided in the document Java and Memory in IUCLID 6. What follows below is aimed at users with sufficient IT skills that they need to know only where to find the parameters.
IUCLID 6 and its tools are Java applications. Many problems relating to memory can be solved simply by increasing the maximum limit of allocation of RAM by increasing the value of the parameter Xmx for the relevant Java virtual machine (JVM). Where Xmx is set, Xms may also be set. The locations and default values are:
|Application||Default value||Settings file|
|IUCLID 6 Desktop||2 GB (-Xmx2048m)||<installation directory>\glassfish4\glassfish\domains\domain1\config\domain.xml|
|IUCLID 6 Server (Server)||4 GB (-Xmx4096m)||<installation directory>\glassfish4\glassfish\domains\domain1\config\domain.xml|
|IUCLID 6 Server (Client)||1 GB (-Xmx1024m)||<installation directory>\glassfish4\glassfish\domains\domain1\iuclid6\iuclid6-war-<version>.war\launch.jnlp|
|Updater tool (command line version)||1 GB (-Xmx1024m)||<IULCID updater tool>\bin\updater.cmd|
Migration from IUCLID 5 to IUCLID 6
A10. Data can be migrated from any supported IUCLID 5.6 database to IUCLID 6 using the installer for IUCLID 6. In addition, IUCLID 5.6 files with extension i5z can be imported into IUCLID 6. For more information see the following page on this website https://iuclid6.echa.europa.eu/archive-iuclid-5..nnn..
A16. Yes, IUCLID 6 accepts the import of IUCLID 5.6 files. During import, the data is automatically migrated to the IUCLID 6 format. However, IUCLID 6 is not able to export data in the IUCLID 5 format.
A17. Yes. The IUCLID 6 installer migrates data from PostgreSQL to Derby databases. It connects to both IUCLID 5 and IUCLID 6 databases at the same time, and executes the migration from any supported IUCLID 5.6 database to the latest version of any supported IUCLID 6 database.
A18. The migration of data from a IUCLID 5 database to a IUCLID 6 database performed by the IUCLID 6 installer works independently of whether either database were used in a desktop or a server configuration. There is no separate tool for the desktop and server configurations.
It is not always essential to migrate data using the IUCLID 6 installer, because i5z files created in IUCLID 5.6 can be imported into IUCLID 6. The use of the IUCLID 6 installer is recommended for large amounts of data, for example, thousands of dossiers.
A19. Yes. Use the IUCLID 6 installer to migrate the data from a IUCLID 5.6 database, to a fresh IUCLID 6 database. The IUCLID 6 database can then be used with either a desktop or server version of IUCLID 6.
A33. The introduction of Instance Based Security (IBS) in IUCLID 6 allows data to be migrated and/or imported from different IUCLID 5 databases into one merged IUCLID 6 database in which access to the data is partitioned between Users and groups of Users.
Before attempting to merge IUCLID 5 databases, familiarise yourself thoroughly with the IBS functionality and consider what action to take (Cf. IUCLID 6 User Manual).
Some common scenarios are described here.
A34. When the IUCLID 6 installer is closed after a migration, it writes a report on the migration to the following file:
<iuclid 6 installation directory>/logs/installer-report.log
The file contains a report in structured text, that for further analysis, can be imported in to a spreadsheet application such as Excel.
IUCLID functions and integration with other systems
A20. Web services are designed for using IUCLID 6 with external systems, but the integration with specific systems; such as IHS Intelligent Authoring, and SAP EHS, will have to be implemented by the users. ECHA will develop the integration of IUCLID 6 with, for example, Chesar 3 and the QSAR Toolbox. In addition, ECHA will provide guidelines on how to achieve integration with other systems.
A26. This problem can be caused by an antivirus program; or by a firewall or a proxy between the client and the server. There could be an intermediate proxy that rewrites requests or responses. Try to run the IUCLID 6 client locally on the server. If the client can run locally without this problem, you will have to configure your network so that the IUCLID 6 clients make direct connections to the server.
A30. A user with 'Access All' can view and update the accessibility of all sections in Role - Data access.
A user with 'Read/Write/Delete' rights to roles but with 'No access 'on a section in 'Data Access' cannot see or update the accessibility of that section for any role.
A user with 'Read/Write/Delete' rights to roles but with 'No access' to an entity in 'Permissions' can see and update the accessibility of that section for any role.
The visibility of data sections should be the same as for entities.
The work-round is that a user must have at least 'Read Access' to any section in order to be able to see and grant rights to it in 'Roles - Data Access'.
A39. The log files generated by IUCLID can be found in different locations according to your installation type:
IUCLID 6 Desktop: <IUCLID6 installation folder>\glassfish4\glassfish\domains\domain1\logs
- IUCLID 6 Desktop installer wizard: <IUCLID6 installation folder>\logs or i6inst\logs (in case the installation is not successful)
- IUCLID 6 Server
- Server side logs - from the IUCLID 6 server: <IUCLID6 installation folder>\glassfish4\glassfish\domains\domain1\logs
- Client side logs - from the computer where IUCLID 6 was used: C:\Users\<username>\iuclid6\<URL>\logs
- IUCLID 6 migration tool: folder “logs” in a folder where the migration tool was launched, or one level above. If the migration was executed with the IUCLID 6 Desktop installer wizard then the migrator logs will be in: <IUCLID6 installation folder>\logs
A49. At present, we can only ensure full compatibility between Chesar 3.3 and IUCLID 6.2.
Be aware that neither IUCLID nor Chesar updates are necessary for you to finalise your dossiers for the 2018 deadline. You can finalise both your Chesar files and IUCLID technical dossier using IUCLID 6.1.3 and Chesar 3.2.
Although Chesar 3.3 and IUCLID 6.1.3 are compatible in the majority of cases, some small issues may occur which may break the compatibility between the applications. At this moment we are aware of the following incompatibilities between those versions:
- If you select more than one option in the field “Regulatory status” at use level in Chesar Box 2 (available in Chesar when you tick the box “Show additional fields relevant for use description in IUCLID”), the export of uses to IUCLID and the generation of the full CSR will not be successful.
- Some issues appear in the generation of sections 1-8 of the CSR when generating the full CSR from Chesar, such as double printing of the hazard pictograms or display of the UUID instead of the name of the linked service life.
A54. The error message, "The file you are importing is not supported by your Iuclid instance." is given when an attempt is made to import data into IUCLID 6.1.x that was exported from IUCLID 6.2.x using the default options. To import data from IUCLID 6.2.x in to IUCLID 6.1.x it must have been exported with the option 'Export to previous major version' turned on, as shown below.
There are two ways to proceed:
1) Upgrade the instance of IUCLID 6.1.x to IUCLID 6.2.x, and then retry the import.
2) Re-export the data from IUCLID 6.2.x with 'Export to previous major version' turned on, and then retry the import.
Bear in mind that the data might have been exported with 'Export to previous major version' turned off to preserve the data format used in IUCLID 6.2.x. Therefore, before re-exporting from IUCLID 6.2.x with 'Export to previous major version' turned on, ensure that it will not cause any unwanted effects. For an example, see section 17.4.4 of the manual Functionalities of IUCLID 6.