ChemAxon 9c0afc9aaf
14-03-2006 17:35:11
Detailed information on this licencing schema:
(for other licensing types contact sales _at_ chemaxon.com for details)
The default limit without license key is 1 search per minute (without key).
The number of connected users does not count.
For example in a web application unlimited number of users can download a page with Marvin and draw their queries for unlimited time.
The only thing that counts is when a user starts a database search (e.g.
by pressing a "Search" button after drawing the query, or a SELECT that uses the index is uses in the Cartridge).
The start time of the search is registered.
At the start of each search JChem checks how many searches were
initiated in the past 60 seconds.
If this is less than the limit allowed by your license, it allows the search.
Otherwise a specific exception is thrown, and the user should try again after some time.
The exception is MaxSearchFrequencyExceededException:
http://www.chemaxon.com/jchem/doc/api/chemaxon/jchem/db/MaxSearchFrequencyExceededException.html
Of course unsuccessful tries are not registered as a search, so these
do not increase the number of performed searches.
JChem can also log the searches to the standard error stream: each
search log contains statistics about how many searches are used currently.
It can be useful to determine if user activity is close to the limit,
and a license extension is necessary.
A typical log looks like this:
The "peak" search (here 5) records the record number, since the
application / server was last started (goes back to 0 on restart).
You can enable logging by calling "JChemSearch.setInfoToStdError(true)":
http://www.chemaxon.com/jchem/doc/api/chemaxon/jchem/db/JChemSearch.html#setInfoToStdError(boolean)
The messages will appear in the standard error, or in case of a web
server in the server's log.
In case of the Cartridge this logging can be toggled in the web
administration interface ("Extra information to the standard error"),
and will be visible in Tomcat's log.
(for other licensing types contact sales _at_ chemaxon.com for details)
The default limit without license key is 1 search per minute (without key).
The number of connected users does not count.
For example in a web application unlimited number of users can download a page with Marvin and draw their queries for unlimited time.
The only thing that counts is when a user starts a database search (e.g.
by pressing a "Search" button after drawing the query, or a SELECT that uses the index is uses in the Cartridge).
The start time of the search is registered.
At the start of each search JChem checks how many searches were
initiated in the past 60 seconds.
If this is less than the limit allowed by your license, it allows the search.
Otherwise a specific exception is thrown, and the user should try again after some time.
The exception is MaxSearchFrequencyExceededException:
http://www.chemaxon.com/jchem/doc/api/chemaxon/jchem/db/MaxSearchFrequencyExceededException.html
Of course unsuccessful tries are not registered as a search, so these
do not increase the number of performed searches.
JChem can also log the searches to the standard error stream: each
search log contains statistics about how many searches are used currently.
It can be useful to determine if user activity is close to the limit,
and a license extension is necessary.
A typical log looks like this:
| Code: |
Wed Mar 01 01:10:23 CET 2006 Search mode: SUBSTRUCTURE Structure table: nci Query: Clc1cccc(Cl)c1 Screened: 6305 Hits: 200 Total time: 50 ms Screening: 9 ms Processing threads: 2 Current / peak / maximum searches per minute: 2 / 5 / 99 |
The "peak" search (here 5) records the record number, since the
application / server was last started (goes back to 0 on restart).
You can enable logging by calling "JChemSearch.setInfoToStdError(true)":
http://www.chemaxon.com/jchem/doc/api/chemaxon/jchem/db/JChemSearch.html#setInfoToStdError(boolean)
The messages will appear in the standard error, or in case of a web
server in the server's log.
In case of the Cartridge this logging can be toggled in the web
administration interface ("Extra information to the standard error"),
and will be visible in Tomcat's log.