Jama 8 FAQ

By Gustavo Flores posted 11-04-2016 01:55


Jama 8 FAQ (Questions expand on click)

A: No, your account representative will give you a new license when you select an upgrade distribution channel for Jama 8.x

A: You can choose between 2 channels: Standard or Standard Airgap. You can refer to this page to help decide.

A: Yes, it does. Your Jama application server will contact our license server to get updated information every time it starts. The only way to avoid this is to request an Airgap version of Jama. This version uses a local license and the updates need to be downloaded and performed manually. Reach out to your account representative for more details.

A: Yes, it can. You need to make sure that the traffic between the Docker containers is not routed through the proxy. You can refer to this article for more information.

A: You can install Jama 8 as long as you can install the dependencies necessary for Docker and Docker itself. Check this article for details.

A: Jama must run on a dedicated server. The database must be hosted on a server separate from the Jama application. This database server can host other databases, but we do not support other applications running on the same server as the database.

A: This is probably related to the fact that you have an outdated version of Replicated. Please follow these instructions to update it.

Q: Which Jama versions do you support on the Standard channel?

A:We support the most recent year of Standard releases.

Q:Some of are users are on the same subnet as the Docker installation. Can I configure the default bridge (docker0) network for Docker Engine to a different subnet?

A:Yes, you can configure the bridge. Please see Docker's site for instructions.

Q:How is the application monitored in this new environment?

A:Utilize embedded JavaMelody
Hook into JMX, configured in the admin console
Monitor if the host is up
Monitor the Docker process to ensure Jama is running
Monitor the Docker process table to ensure 4 Jama containers are running: jamacore, jamanginx, search, and elasticsearch

Q: Multi-host instances?

A: We currently support our Elasticsearch container to run remotely which will allow for greater resource utilization for searching and indexing large amounts of data. Contact your CSM for details around licensing requirements.
We do not support multiple Jama application containers connected to a single database.

Q:Why Replicated and not some other orchestration technology?

A: We chose Replicated, an orchestration tool, to manage the installation and configuration of Jama. We determined that this was a best in class tool and organization that we could work closely with to provide the best experience.

Q: Do we have to use Replicated to install Jama?

A: Yes, this is our only supported deployment orchestration tool.

Q: Can we install Jama with other Docker containers we have running?

A: No, this is not supported. Although technically capable, the Jama application is configured to utilize the maximum amount of system resources on the host.

Q: Must the Docker daemon run as root?

A: Yes. This is due to the nature of the Docker application. See https://docs.docker.com/engine/security/security/ for more information.

Q: Is root access necessary to run the install script?

A: No, but ‘sudo’ access is required. To install Docker the script must be run with elevated user privileges or as root.

Q: Can we change the contents / configuration of the Docker containers?

A: No, this is not supported. Although technically capable, the containers are ephemeral, so any changes would will be lost.

Q: How do we handle security updates?

A: Every deployment is built and shipped with the latest security patches for the operating system running in the containers. Jama continually monitors the distributed third-party applications for high severity defects and will ship an update if needed.

Q: What is Jama’s proposed SLA for security patches on Tomcat and Java once they are announced?

A: When a critical CVE is published, Jama will rebuild the application and deploy it to the two customer application channels.

Q: How can server monitoring be set up to send notifications when thresholds are met?

A: You can use any number of tools that can speak JMX. For example, Nagios has a JMX plugin.

Q: Attachment storage backup and restore: how is this done with Jama 8?

A: Jama recommends the usage of native backup tools: database replication with a backup policy and filesystem replication or backup policy used with an exported filesystem like NFS. The /data directory can be mounted in low latency environments. Amazon's EFS technology is not suggested. Note that policy differences between the database and mounted filesystem can lead to a loss of data. It is suggested to have a similar if not identical backup policy for both tools.
For manual, occasional backups, the Jama root user account has a backup that can be executed. This file is stored as a backup file on the filesystem of the server, within the /data/backup directory. A backup consists of all the filesystem assets within /data as well as an export of the database to XML format and wrapped up using ZIP. The backup file has a “.jama” file extension even though it is of ZIP format. This option is typically used for migrating Jama data between instances or moving between database vendors. It can also be used for provisioning during the upgrade process from > 2015.2 to 8.x.

Q: What data is sent to Jama and/or Replicated during and after installation?

A: Data Policy
The admin dashboard provides some console settings to change timing intervals.
Update Check
Current version of the Jama application
Jama application status
Replicated products and versions that are running
Number of operators provisioned and connected
(e.g. replicated, replicated-ui and replicated-operator 2.4.0)
Default set to every 5 hours
Configurable: Never, 1, 3, 5, 10 hours and a custom value set in crontab syntax
License sync
Default interval set to 10 hours
Configurable: Never, 1, 3, 5, 10 hours

#administration #Jama8 #installation