Important notice: HTML5 client should be always first instance in the network chain, it plays the role of SSL decrypter
Even if you decide to use third part web server like IIS/Apache the HTML5 instance should be still the SSL decrypter else no Websocket connectivity will be available (or you will have to setup IIS/Apache in reverse proxy mode if HTML5 should stay second instance). The HTML5 instance has to decrypt it to distinguish packets to be correctly forwarded.
Let’s assume you have 3 different domains pointing to same IP ( -> ( -> ( ->

In order to serve different certificates according to the domain name do following.

1. create subfolder “multicerts” under “*\Clients\webserver\” folder like so “*\Clients\webserver\multicerts\

2. rename approved *.jks files for example above > ***\webserver\multicerts\ > ***\webserver\multicerts\ > ***\webserver\multicerts\

(if you have multidomain certificate * and you want to serve this certificate for all domains ending 
with inclusive then add leading point to jks certificates name as in example 
https://**** > ***\webserver\multicerts\

3. restart HTML5 in AdminTool GUI or reread configuration locally on server

In such case when ever you access, or you will get different certificates served (however this requires SNI support by browser, but all modern browsers support it for longer time)
For other unrecognized (not in “multicerts” folder) domains the default *\Clients\webserver\cert.jks will be served.
This SNI feature makes sense only for authority signed certificates, for self signed certificates one such cert is enough, since it makes no sense to serve different self signed certificates.