On this page


The installation of Magic Collaboration Studio services and initial configuration is described in this section. Installation using the provided script is highly recommended. The process involves installing the service(s), generating an initial self-signed SSL certificate, creating the twcloud user for file and service ownership, then configuring the Linux environment for performance and security. 

Prerequisites

Installing Magic Collaboration Studio services

To install Magic Collaboration Studio services

  1. To install OpenJDK 17 on a new Magic Collaboration Studio server, execute the following command:

    yum -y install java-17-openjdk


  2. Download the <product>_<version_number>_installer_linux64.bin file and place it in the same location as the install_twc_mcs_ol_rhel.sh script.

  3. Install Magic Collaboration Studio by executing the install_twc_mcs_ol_rhel.sh script.

    sudo ./install_twc_mcs_ol_rhel.sh


  4. Follow the on-screen installation guidance.

  5. When the Magic Collaboration Studio pre-installation summary is displayed, check if the information is correct and press ENTER.

  6. Start the twcloud, zookeeper, and webapp services (in this particular order) by executing the following commands:

    sudo systemctl start twcloud
sudo systemctl start zookeeper
sudo systemctl start webapp

  7. Make sure that Magic Collaboration Studio is operational by going to https://<server_address>:8443/webapp. You should see the Magic Collaboration Studio login screen.

    For more information, see Accessing Magic Collaboration Studio web applications.


When you complete the steps above, the preliminary Magic Collaboration Studio configuration is created. This means that your system is functional and you can login to Magic Collaboration Studio. After making sure that Magic Collaboration Studio is operational, you can optionally perform the post-installation configuration described in the section below.

Post-installation Magic Collaboration Studio configuration

The post-installation configuration is an optional step and you should only perform it after making sure that Magic Collaboration Studio is operational.


To perform the post-installation Magic Collaboration Studio configuration

  1. Edit the <install_root>/TeamworkCloud/configuration/application.conf configuration file and make the following changes:
    • Change the value of the contact-points property to point to the listen_address you set in the cassandra.yaml file (i.e., contact-points = ["192.168.130.10:9042"]). This points Magic Collaboration Studio to the Cassandra database.
    • Use this parameter only if you need to deploy Magic Collaboration Studio in private network but client connect from public network. Change the value of the server-broadcast-host property to the public IP address instead of the local IP address. This way upon the initial connection the client application will know the external IP address to which it must connect (if Magic Collaboration Studio is installed behind a proxy or firewall with NAT).

  2. Edit the <install_root>/WebAppPlatform/shared/conf/authserver.properties configuration file and make the following changes:

    • If you are accessing the server by FQDN, change the value of the authentication.redirect.uri.whitelist property by adding an the FQDN entry to the whitelist (e.g., authentication.redirect.uri.whitelist=https://FQDN:8443/,https://FQDN:8111/,https://md_redirect). Make sure to add the public IP and/or FQDN for ports 8443 and 8111 to the whitelist.

  3. Edit the <install_root>/WebAppPlatform/shared/conf/webappplatform.properties configuration file and make the following changes:
    • Change the value of the twc.admin.username property to the username of a local account with Administrator privileges (the default value is Administrator).
    • Change the value of the twc.admin.password property to the password corresponding to the Administrator user (the default value is Administrator).
  4. Restart the affected Magic Collaboration Studio services.

Document exporter font package

To use Cameo Collaborator document export, a TrueType font package is required for the PDF export functionality. Both font packages listed below will work for exporting PDF documents. The dejavu-serif-fonts package can be installed from the base Linux repository, while Microsoft TrueType requires building the RPM.

TrueType Font options:

  • dejavu-serif-fonts package (repository)
  • Microsoft TrueType (RPM build)