Instant JChem System Requirements

    Hardware Requirements

    Minimal requirements:

    Hardware Minimal requirement
    CPU 1.2 GHz dual-core or higher
    RAM 2 GB or higher
    Hard-drive space 1 GB

    Instant JChem employs a sophisticated caching system so that it can handle large data sets without needing all the data to be in the memory. In general this works very well, but everything has its limits. You may need to increase the memory that IJC will have access to.

    Additional memory for JChem Base database tables:

    • Each million structures need additional 100 MB of memory

    • For 600 Markush structures, around 700 MB of additional memory is needed

    • For more detail, see memory usage documentation.

    For JChem Cartridge based solutions, minimum recommended memory should suffice. For server memory settings, see documentation here.

    Software Requirements

    Operating System

    Instant JChem is tested on the following platforms:

    • Windows 8 (64-bit)

    • Windows 10 (64-bit)

    • GNU/Linux (64-bit)

    • Mac OS X (64-bit)

    JChem Cartridge Compatibility

    Instant JChem is tested with the current version of JCC (with the same version as the last release).

    <a name="src-1803031-instantjchemsystemrequirements-supporteddatabases"></a>

    Supported Databases

    • Derby

    • MySQL 5.5 and newer

    • Oracle 10g and newer

    • Composite

    • Microsoft SQL Server 2005 Express and newer

    • PostgreSQL 9.6. and newer

    For more info, please refer to user guide.

    {primary} Please note, that Instant JChem might work with older versions of the databases (such as Oracle 9i), but as we do not test those, full functionality is not guaranteed.

    Known issues and limitations

    • MySQL tables created with COLLATION uft8_bin will not work. Current workaround is to use different collation. For example utf8_general_ci

    • Can not create IJC Schema on MySQL 5.7. Current workaround is to turn off NO_ZERO_DATE restriction in the MySQL server instance.

    There are multiple ways to do that. E.g. find out your settings with:

    SELECT @@GLOBAL.sql_mode;

    and then apply new ones without NO_ZERO_DATE mode:

    SET GLOBAL sql_mode = "<new-value-without-the-mode>";

    • In order for IJC to work correctly with MySQL 8 ONLY_FULL_GROUP_BY option has to be Turn off in the MySQL server instance.

    There are multiple ways to do that. E.g. find out your settings with:

    SELECT @@GLOBAL.sql_mode;

    and then apply new ones without ONLY_FULL_GROUP_BY mode:

    SET GLOBAL sql_mode = "<new-value-without-the-mode>";

    • MySQL 8 uses caching_sha2_password rather than mysql_native_password as of MySQL 5.7. As a result you may encounter difficulties when accessing MySQL 8 database.
    images/download/attachments/1803031/ijc.png

    To fix this, you should adjust your database settings, e.g.

     ALTER USER 'user'@'localhost' IDENTIFIED WITH mysql_native_password BY 'your_new_password';
    
     FLUSH PRIVILEGES;

    For more details see https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password

    Java

    Supported major Java versions:

    • Java 8 (from IJC version 15.2.20 until IJC version 21.14.0 and LTS Helium)

    • AdoptOpenJDK 8 (from IJC version 18.22.0 and LTS Carbon 1 until IJC version 21.14.0 and LTS Helium)

    • Java 11 (from IJC version 20.11.0)

    {primary} Using 64-bit Java is highly recommended.

    {warning} AdoptOpenJDK8 and JWS: Please note that AdoptOpenJDK8 and Java 11 doesn't support Java Web Start.

    ChemDraw

    Only 32-bit version of ChemDraw is supported.

    IJC version ChemDraw supported
    5.12.x ChemDraw 12 (32-bit)
    since 6.0.3 until 18.21.0 ChemDraw 12 or 13 (32-bit)

    {warning} Support of ChemDraw as molecule sketcher has been dropped since IJC version 18.21.0.

    Spotfire

    Currently supported versions of Spotfire server are: 7.x up to 10.10.

    {warning} The Spotfire integration has been removed from IJC. Since version 21.10.0., it is available via Plexus Connect. For more details about deploying and usage of the new Spotfire integration, please refer to documentation.