This chapter explains how to install Teamwork Cloud services by using the install_twc_mcs_centos_rhel.sh installation script.


To install Teamwork Cloud services

  1. To install OpenJDK 17 on a new Teamwork Cloud server, execute the following command:

    yum -y install java-17-openjdk
  2. Download the twcloud_<version_number>_installer_linux64.bin file and place it in the same location as the install_twc_mcs_ol_rhel.sh script.

  3. Install Teamwork Cloud by executing the install_twc_mcs_ol_rhel.sh script.

    Example
    sudo ./install_twc_mcs_ol_rhel.sh
  4. Follow the on-screen installation guidance.

  5. When the Teamwork Cloud 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. To ensure Teamwork Cloud services start after the reboot, execute the following commands:

    sudo systemctl enable twcloud
sudo systemctl enable zookeeper
sudo systemctl enable webapp

  8. Make sure that Teamwork Cloud is operational by going to https://<server_address>:8443/webapp. You should see the Teamwork Cloud login screen.

    For more information, see Accessing Teamwork Cloud web applications.

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


Post-installation Teamwork Cloud Configuration

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


To perform the post-installation Teamwork Cloud configuration

  1. Edit the <install_root>/CATIANoMagicServices/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 Teamwork Cloud to the Cassandra database.
    • Use this parameter only if you need to deploy Teamwork Cloud 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 Teamwork Cloud is installed behind a proxy or firewall with NAT).

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

    • Change the value of the cassandra.contactPoints property to the local IP address.

    • 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>/CATIANoMagicServices/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 Teamwork Cloud services.