JChem Microservices consists of two types of microservice modules: common modules and chemical functional modules.
The common modules ensure the technical framework for the separate chemical functional microservice modules working together as a system.
The chemical functional modules make possible to reach the chemical functionalities provided by other ChemAxon products through microservices interface.
Chemical functional modules
Calculation Web Services provide endpoints for chemical property calculations and chemical-term evaluation.
DB Web Services provide methods for storing and searching chemical structures in a persistent database
There are methods for
creating / deleting tables
inserting / deleting / modifying structures and data in the tables
executing duplicate, substructure, full fragment and similarity searches
Input/Output (IO) Web Services provide methods for
converting molecules to different chemical file formats,
analyzing molecule string and defining its file format,
preparing molecule file for download,
collecting properties from molecule.
Markush Web Services provide enumeration of Markush structures.
Reactor Web Services provide endpoints for Reactor operations.
Structure Checker Web Services provide methods for
Structure Manipulation Web Services provide methods for manipulations on chemical structures like
extracting textbox content from the structures,
cutting structures into their fragment structures,
two-dimensional and three-dimensional cleaning of chemical structures,
Task Manager provides the possibility of scheduling special long lasting tasks for the following web services:
Download jws-installer - appropriate for your operating system - from
On Debian, Ubuntu
sudo dpkg -i jws_linux_<version-number>.deb
On Redhat, Centos
Upgrade is the same process as installation.
The content of the config folders and the data folder of the DB Web Services module will not be overwritten.
However, special care must be taken in case of DB Web Services.
If the data structure version number of the new DB Web Services is higher than that of the existing old DB Web Services, the
updateMode configuration parameter controls how the upgrade will be performed when DB Web Services service is started:
The available options are as follows.
EXIT: the service start process exits if any change is detected. Afterwards
updateMode parameter must be set to DROP or REINDEX to start, or you should migrate back to the previous version.
DROP: the existing table and index data will be dropped.
REINDEX: the existing tables will be reindexed.
Depends on the operating system and on the installation mode you applied.
C:\Program Files\ChemAxon\JChem Micro Services\uninstall.exe
<Installation folder>/ChemAxon/JChem Micro Services/uninstall
On Debian, Ubuntu
sudo dpkg -r jws
On Redhat, Centos
Put the license file under jws/license/ folder with name: license.cxl or apply any of the options listed on the Installing to servers page.
For using DB Web Services , " JChem Microservices DB " license is required.
For using IO Web Services , " JChem Microservices IO " license is required.
For using Structure Checker Web Services , " JChem Microservices Structure Checker " license is required.
For using Structure Manipulation , " JChem Microservices Structure Manipulation "license is required.
For using Calculations Web Services , " JChem Microservices Calculations " license is required.
For using Markush Web Services , " JChem Microservices Markush Enumeration " license is required.
By default, the log files of all the modules are separately stored in jws/logs/ folder. The place of log files and the logging level can be modified in the application.properties file of each service.
/actuator/health endpoint on the gateway reports the health status of the whole microservices system. It reports Status 2xx if all services are alive and work well.
The individual health status of the modules can be seen on the
The idea behind JChem Microservices is to provide a solution with High-Availability, Robust and modern Web Service where highly used parts can be scaled up and rarely used parts can be switched down. For this we provide the opportunity to set up different arts of the software on many machines. All of the services can be configured by a central configuration service, they all register into a discovery service and have a common entry point, which should be the only visible service in your network.
Spring Cloud Configuration service is provided.
Run the service in command line in folder jws/jws-config/
jws-config-service --start (on Windows)
jws-config-service start(on Linux)
run-jws-config.exe (on Windows)
|## You can set all settings here for all applications|
|## LOG config:
|## DB config:
com.chemaxon.zetor.types.version = 1
com.chemaxon.zetor.types.typeName = sample
com.chemaxon.zetor.types.typeId = 1
com.chemaxon.zetor.types.tautomer = OFF com.chemaxon.zetor.types.standardizerAction = aromatize com.chemaxon.zetor.types.version = 1
com.chemaxon.zetor.types.typeName = taumol
com.chemaxon.zetor.types.typeId = 2
com.chemaxon.zetor.types.tautomer = GENERIC
com.chemaxon.zetor.types.standardizerAction = aromatize
|If DB Web Services are run as part of a microservices system, specify here its configuration parameters.
If DB Web Services are run as standalone web application, specify its configurations in its own module's application.properties file.
See explanations here
|## Communication settings of gateway:
|You can set up various timeouts in JChem MicroServices. We use the Spring Cloud Stack with solutions from Netflix. Ribbon load balancer is responsible for the communication between the services. You can set up its timeout settings with the ribbon prefix, like: ribbon.ReadTimeout. This property controls when to interrupt waiting for an answer between ChemAxon services. You can also setup a guard with Hystrix circuit breaker with properties like: execution.isolation.thread.timeoutInMilliseconds which will interrupt your request if it does not get an answer during the timeout.|
Copy the right JDBC driver to 'extra-libs' folder.
In jws-config/config/application.properties set the followings:
spring.profiles.active=jdbc spring.datasource.url=<jdbc url> spring.datasource.driver-class-name=<jdbc driver class name> spring.datasource.username=<username of jdbc connection> spring.datasource.password=<password of jdbc connection>
more on Spring data source settings: https://docs.spring.io/spring-boot/docs/current/reference/html/appendix-application-properties.html#data-properties
This setting will only work if you have a table, called: PROPERTIES with this 5 text fields (these fields can be any text fields):
example properties table creation SQL:
CREATE TABLE PROPERTIES ( APPLICATION VARCHAR(255) DEFAULT 'application', PROFILE VARCHAR(255) DEFAULT 'default', LABEL VARCHAR(255) DEFAULT 'master',KEY VARCHAR(255) NOT NULL,VALUE CLOB);
It is possible to use a different table than properties. In this case you have to set the QUERY to get key-value pairs, like:
spring.cloud.config.server.jdbc.sql=SELECT MY_PROPS.K AS KEY, MY_PROPS.V AS VALUE FROM MY_PROPS WHERE APP=? AND PROF=? and LBL=?
What are the defaults in the example SQL?
Spring Cloud Config is designed to provide properties from git repositories. This database schema mimics that. In the git repository all application can have their own settings in their application_name.properties file, or common properties can be in application.properties file. The default value 'application' in the APPLICATION column means it is "found" in application.properties file so it is distributed to all applications.
Every properties file can be linked to a specific profile, like: production, development, aws, etc. and their settings are only taken into account if their profile is active. The default value 'default' in PROFILE column means this setting is not paired to any specific profile name, but to the default profile.
Since in the original concept the configuration distribution is solved by git repositories, all files are also part of a git branch. The branch currently checked out is represented in the LABEL column, with default value 'master' it is mimicking to be part of the master branch. Here basically any value different from NULL is acceptable.
In the KEY column the keys should be set with the Properties syntax, so a simple property, like:
should be a.b.c
a: b: c: value
it is also transleted to a.b.c;
Example with lists:
prop.path.list.a_key=a0_value prop.path.list.b_key=b0_value prop.path.list.a_key=a1_value prop.path.list.b_key=b1_value
prop: path: list: - a_key: a0_value b_key: b0_value - a_key: a1_value b_key: b1_value
would translate to this insert sql (if the defaults are as in the example table creation SQL):
INSERT INTO PROPERTIES (KEY, VALUE) VALUES ('prop.path.list.a_key', 'a0_value'), ('prop.path.list.b_key', 'b0_value'), ('prop.path.list.a_key', 'a1_value'), ('prop.path.list.b_key', 'b1_value');
Eureka, the Netflix Service Discovery Server and Client is provided.
Run the service in command line in folder jws/jws-discovery/ :
jws-discovery-service --start (on Windows)
jws-discovery-service start (on Linux)
run-jws-discovery.exe (on Windows)
Spring Cloud Gateway is provided.
Run the service in command line in folder jws/jws-gateway/ :
jws-gateway-service --start (on Windows)
jws-gateway-service start (on Linux)
run-jws-gateway.exe (on Windows)
run-jws- gateway(on Linux)
|server.port=8080 logging.file.name=../logs/jws-gateway.log eureka.client.enabled=true|
CORS is not allowed by default but can be enabled in Gateway, if required:
Our Gateway is a simple Zuul Proxy (https://github.com/Netflix/zuul), developed by Netflix. By default it has a smart algorithm to retry failed requests on different backend instances. For this it keeps each request in memory until it is answered successfully or it cannot be retried on any other servers. This leads us to a limitation where the sent message is kept in memory so if we want to send lots of data at once (like indexing a large batch of molecules), we have to grant enough memory for Zuul to keep our whole request in memory during the process. You can set Gateway's maximum memory as any Java process in the appropriate
.vmoptions file. (If you execute the service with
jws-gateway-servcie, then use
jws-gateway-service.vmoptions; if you execute the service with
run-jws-gateway, then use
run-jws-gateway.vmoptions.) The default setting is
-Xmx256m, which means maximum 256 MB memory.
To protect Gateway from overloading its memory, we have introduced a filter to reject every message where
Content-Length header is greater than 1/3 of the available maximum memory. With default memory settings this will lead you to reject every request with body greater than 85 MB.
You can also specify directly how many bytes do you allow in a request. For this set
gateway.max-message-size=<number_of_bytes_to_allow> to the number of bytes you want to allow in a request. (Set this as any other property in Config server.)
A docker image of JChem Microservices is provided as an example.