Skip to main content

Jama Connect User Guide

Prepare your application server (traditional)

Make sure your application server is set up properly before installing the application.

See Supported software and system requirements.

Important considerations

  • To improve resolution time of any issues, keep ports open. Closing access to ports for communication within the server isn't supported and poses a risk to application accessibility.

  • To avoid blocking issues when installing on RHEL or CentOS Linux distributions, disable firewall or add the docker0 interface to the "trusted" zone.

  • Work with your network admin to make sure your network is configured properly.

To prepare your application server:

  1. Make sure the following ports are accessible to inbound traffic:

    • Port 22 — SSH port allows admins to make remote connections to the application server using SSH.

    • Port 8800 — Admin Console port allows admins to access the Admin Console, which is used to configure, install, and upgrade Jama Connect.

    • Port 80 — Jama Connect port for clear text communication (HTTP), which is used to access Jama Connect. It can be disabled or the port number can be reconfigured.

    • Port 443 — Jama Connect port for SSL/TLS communication (HTTPS), which is used to access Jama Connect. It can be disabled or the port number can be reconfigured.

  2. Verify that the following User IDs are available and unused on the application server.

    • User ID 91 — Used by Tomcat to read and write to directories under /data.

    • User IDs 480 – 499 — Used by the various services.

  3. To ensure accurate time on the application server, set up a cron job to sync the time on a routine schedule (for example, every day or hour). Use this command to set up the cron job:

    ntpdate pool.ntp.org

  4. Set up dedicated volumes for the data your application is going to write. Use this example to partition the logical volumes on your application server, starting with a 100 GB disk.

    1. Create a mountpoint:

      mkdir /data /logs /var/lib/docker /var/lib/replicated

    2. Create a physical volume:

      pvcreate /dev/<your-disk-name>

    3. Create a volume group:

      vgcreate vg_jama /dev/<disk-name>

    4. Create logical volumes:

      lvcreate -L 30G -n lv_docker vg_jama
lvcreate -L 20G -n lv_replicated vg_jama
lvcreate -L 10G -n lv_logs vg_jama
lvcreate -l 100%FREE -n lv_data vg_jama

    5. Write file systems:

      mkfs.xfs -L docker -n ftype=1 /dev/vg_jama/lv_docker
mkfs.ext4 -L replicated /dev/vg_jama/lv_replicated
mkfs.ext4 -L data /dev/vg_jama/lv_data (ext4 or NFS)
mkfs.ext4 -L logs /dev/vg_jama/lv_logs

    6. Edit the file /etc/fstab to include the following lines:

      LABEL=docker /var/lib/docker xfs defaults 0 0
LABEL=replicated /var/lib/replicated ext4 defaults 0 0
LABEL=data /data ext4 defaults 0 0
LABEL=logs /logs ext4 defaults 0 0

    7. Mount all volumes:

      mount -a
In this section: