Skip to main content

Jama Connect User Guide

Prepare your application server (KOTS)

Make sure your application server meets all requirements. See System requirements and supported software.

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

  1. Inbound rules and ports for nodes — Make sure the ports in the following table are accessible to inbound traffic and the inbound rules are configured for each server in the KOTS cluster.

    Protocol

    Port range

    Source*

    Inbound rule applies to node...

    Description

    HTTPS

    443

    Anywhere

    All

    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.

    HTTP

    80

    Anywhere

    All

    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.

    TCP

    8800

    Anywhere

    All

    Allows admins to access the KOTS Admin Console, which is used to configure, install, and upgrade Jama Connect.

    SSH

    22

    Anywhere

    All

    Allows admins to make remote connections to the nodes using SSH.

    TCP

    6443

    Anywhere

    Any node

    Primary

    Allows admins and KOTS nodes to access the Kubernetes API server.**

    TCP

    2379–2380

    Any node

    Primary

    Allows the KOTS nodes to access the etcd server client API.**

    TCP

    10250

    Any node

    All

    Allows the KOTS nodes to access the Kubelet API server.**

    UDP

    8472

    Any node

    All

    Allows KOTS (Flannel) to create a virtual network that connects the services running inside the cluster.**

    * Anywhere means anyone or anything that must consume the resources in the environment.

    ** Can be disabled in single node clusters.

  2. User IDs — 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 inside jamacore pods.

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

  3. Time sync setting — 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
In this section: