How to provision your Jama Connect® Industry-Specific dataset (KOTS)

Author: Amanda Jennewein

Date: August 22, 2024

Audience: Jama Connect® System Administrators

Environmental details: Self-hosted, Replicated KOTS 

Summary

How to provision your Jama Connect® Industry-Specific dataset (KOTS)

Important

You must set up a Jama Connect® dataset before giving users access to Jama Connect®. If you require the dataset link, please get in touch with your Customer Success Manager.

Provision your Jama Connect dataset (KOTS)

We strongly recommend that you provision an industry-specific dataset. This will ensure that your organization has a sample framework as you begin to use Jama Connect®.

Suppose you choose not to provision an Industry-Specific dataset during installation. In that case, you will miss out on the sample data and the Industry-Specific dataset framework when logging in and using Jama Connect®. This could potentially impact your use of Jama Connect®.
Your purchase confirmation email includes the .jama license file and a link to the Industry-Specific dataset. If you don't have this link, contact your Customer Success Manager.

Requirements

• Jama Connect® must be installed before you provision your dataset. Otherwise, the provisioning will fail.
• If the /data/restore directory doesn't exist, you must manually create it.

To provision your dataset:

1. Download the .jama license file for the industry-specific dataset using the link in your purchase confirmation email.

2. Copy the .jama file to a node within the KOTS cluster on a host system.

3. Copy the .jama file to the /data/restore directory on the host system:

kubectl cp -c core <path to .jama archive> default/core-0:/data/restore/

Configure the file permissions so that all users can read it:

chmod 644 /data/restore/<filename>.jama

5. Delete the tenant properties file: 

kubectl exec --tty -c core pods/core-0 -- rm /home/contour/tenant_properties/tenant.properties

6. Remove the resources:

kubectl delete sts/core
kubectl delete job/tenant-manager
kubectl delete pod/hazelcast-0

7. Drop the current database and create a new one with the same name in SQL Server or MySQL. If you choose to create a database with a new name, please update the database settings in the config tab of the KOTS Admin Console.

8. From the KOTS Admin Console, enter the path to the backup file in the Restore Jama Backup section and click Save.

9. Select Go to Updated version, then click Deploy.

Once your dataset has been provisioned, the status in the Application section of the dashboard changes to "Ready."

Additional Resources

• Installing and Upgrading Jama Connect® v9.6.x (KOTS) Latest

  • Pages 21 - 22
• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Please feel free to leave feedback in the comments below.