Installing Sametime Meetings on Docker

This section provides information on installing Sametime Meetings on Docker.

About this task

To deploy Sametime meetings on docker:

Note: All commands provided require running as ROOT or SUDO access. If not running as root user, preface all commands with ‘sudo'.

Procedure

  1. Download HCL Sametime Meetings 11.6 file from Flexnet.
  2. Extract the zip file to any directory.
  3. If CentOS 8 is in use, complete the steps in topic defining extra hosts for Docker deployments.
  4. To load and initialize the Docker images, from the directory where you extracted the zip file, run the following command:
    ./install.sh 
    
    Note: Before running ./install.sh, make sure permissions are set correction. Run the command:
    chmod 777 install.sh
    .

    The install.sh script will load and run the following list of docker images.

        meetings-location.node
    
        meetings-jibri-web
    
        meetings-persistence.node
    
        meetings-auth.node 
    
        meetings-recordings.node 
    
        meetings-web 
    
        meetings-prosody 
    
        meetings-jicofo 
    
        meetings-jvb 
    
        meetings-jigasi 
    
        meetings-jibri 
     
    

    When prompted, specify the appropriate values for the deployment.

    Note:
    • These values are case sensitive and must be entered in lower case.
    • When prompted for Enter fully qualified Server Name, this value will be the Sametime Meeting server host name.

    Example:



  5. To verify that the Meetings Server is running, run the following commands:

    Show all the loaded docker images

    docker images


    List all running containers in docker engine

    docker ps 
    


  6. Optional:To enable Docker for auto start, run the following commands.
     
    systemctl daemon-reload 
    
    systemctl enable docker
    systemctl restart docker 
    
  7. Optional: If SAML is used for authentication, update the IDP_URL parameter in the custom.env. The default is empty.

    Optional: If a host machine has multiple network interface cards, it may be required to specify the rout-able IP address for the DOCKER_HOST_ADDRESS. Entering a Meeting, receiving infinite "Loading Meeting..." is one cause for needing DOCKER_HOST_ADDRESS set to a rout-able IP address in the custom.env file.

    To enable configuration changes after install, see Enabling Meeting Configuration Changes.

  8. Optional: In the .env file the default system time zone is:
    # System time zone. 
    TZ=America/New_Yor

    If desired, update to the local time zone. By setting to the local time zone, the logging time stamps will be accurate to the host system time.

    Note: Rules to update the custom.env and .env files:
    • Each line in an env file to be in VAR=VAL format.
    • Lines beginning with "#" are processed as comments and ignored.
    • No special handling of quotation marks. This means that they are part of the VAL.
    • Blank lines are ignored.

    To enable configuration changes after install, see Enabling Meeting Configuration Changes.

  9. For information on updating TLS, see Updating the Sametime Meeting Server TLS Certificates

What to do next

Enable Sametime Community for Meetings.