Jama Connect User Guide

Preparing your application server (traditional installation)

Make sure your application server meets all requirements. See Supported software and system requirements.


For users and administrators to properly access Jama Connect, the following ports must be accessible to inbound traffic. Work with your network admin to make sure your network is configured properly.

  • 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.

User IDs

For Jama Connect to successfully run its processes, the following User IDs must be 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.

Time sync schedule

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

To set up the cron job, use the command: 

ntpdate pool.ntp.org

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.

  • Docker pre-routes traffic, so be sure to set rules in the DOCKER-USER table, not the INPUT table.

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

Setting up dedicated volumes

We recommend setting up dedicated volumes for the data your application is going to write.

Use this example to partition the logical volumes on your application server.

Start 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_log
  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
  8. Confirm that all volumes were mounted properly:

    df -h