My good friend and HCL Lifetime Ambassador Daniel Nashed already wrote a post about this topic, here.
Since in my test environment I do not have a proper domain name I had to tweak a bit some configuration settings in order to make the installation work; this can be useful if you want to setup a Meeting server inside your network using a domain like .local instead of your company real domain and hosts file instead of DNS.
The instructions in Daniel’s post are very clear, if you follow them the installation will go fine. The next step is to enable Sametime Community for Meetings
One critical thing to be aware of is this part:
Enable Windows Sametime Community server to support Meetings
Contact HCL Support for instructions to receive a required patch to allow JWT Configuration. Do not continue on Windows until this patch is in place.
Obviously I tried to configure ST Meetings without the patch, (what is a geek doing test installations expected to do ?) and it did not work.
So open a case with Support and obtain that patch before setting up the Meeting server integration with Community server.
UPDATE: As per the comment from Tony Payne, the needed patch is now available on Flexnet when you download the product
What you need to do to make it work with hosts file instead of DNS is this:
Edit the file docker-compose.yml and in the sections ‘auth’ and ‘nginx’ add an “extra hosts” entry and put there the name of your community and meeting servers, like this
This is a yaml file, so be careful to use spaces and not tabs and align text correctly as in the images.
Then run the commands
docker-compose up -d
to restart the server
Many thanks to the Sametime Wizard, Tony Payne from HCL ,for helping me with this.