Logging in to an IJC Schema

    Before you can use an IJC Schema that you have in your project you must login (or connect) to it. A disconnected Schema is signified by the disconnected icon images/download/attachments/1804857/Connection16Disconnected.gif. You login by double clicking the disconnected icon, or right clicking on it and choosing 'Connect...'.

    You can disconnect from a Schema by right clicking in its node and choosing 'Close connection...'. Some operations, such as editing the connection settings and deleting the Schema can only be performed when it is disconnected.

    The login process for an IJC schema depends on the security settings that are in place for that schema. For local databases that have the default security the login process is completely transparent and you are logged in full administrative privileges. If different security settings are in place then the login process will change and you may see various dialogs to define the log in criteria. These can include:

    Database connection criteria

    • The database connection criteria. The username and/or password can be stored, but if they are not then you will be prompted during the login process.

      Encryption password

    • If the connection details are encrypted then you will need the password to decrypt them.

      The Instant JChem login criteria

    • The username and/or password can be stored, but if they are not then you will be prompted during the login process.


    Login modes

    • To make 'structural' changes to the database you need to be logged in to the database as the schema administrator. If you have sufficient privileges then you will be prompted for whether you want to connect as the schema administrator. If you do you will prevent other users from connecting as the schema administrator. More normal users can be connected at the same time. Note that this is only valid for MySQL and Oracle, as the Derby database in IJC is not designed for concurrent access. You are always logged in as the schema administrator if you are using local Derby database.

    Logout earlier session

    • IJC manages your session in the database, and each user can only have one session running at a time. If for some reason you are already logged in (maybe you are logged in on a different computer, or maybe your last session did not exit cleanly) then IJC detects that you are already logged in and asks whether you want to log out that earlier session.

      Update JChem tables

    • The JChem tables containing structures might need to be updated when a new version of JChem is used. This can involve full regeneration of the molecular descriptors (e.g the chemical hashed fingerprints) and can be a slow process. This is described in more detail in the document about updating document.


    • Any errors that occur during the process, such as the database not being available or a username and password being incorrect are reported to the user, with the ability to correct the error if appropriate. The previously reported schema warnings are now replaced with a link which the user will see at logging in time in the output window. On clicking the link, the user can optionally chose to process each issue prior to re-connect.