TIBCO JasperReports® Server application should be able to run on any OpenShift container platform by using the scripts under js-docker.

1. Docker-engine (19.x+) setup with Docker Compose (3.9+)
2. OpenShift container platform
3. TIBCO JasperReports® Server
4. KeyStore
5. Git
6. Helm 3.5
7. Minimum Knowledge of Docker, K8s, and OpenShift

helm repo add haproxytech https://haproxytech.github.io/helm-charts
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add elastic https://helm.elastic.co

These parameters and values are the same as parameters in K8s/jrs/helm/values.yaml.

1. Go to js-docker/K8s, and to update the dependency charts, run helm dependencies update jrs/helm.

2. Update the default_master.properties in Docker/jrs/resources/default_properties as needed.

   Note: Update the dbhost in Docker/jrs/resources/default-propertes/default_master.properties with the name respository-postgresql.<k8s-namespace>.svc.cluster.local to create DB in K8s cluster.

3. Build the docker images for TIBCO JasperReports® Server see the Docker TIBCO JasperReports® Server readme and push it to your docker registry.

4. Generate the keystore and copy it to the K8s/jrs/helm/secrets/keystore folder, see the key Store generation section in TIBCO JasperReports® Server readme.

5. Copy the TIBCO JasperReports® Server license to the K8s/jrs/helm/secrets/license folder.

By default, TIBCO JasperReports® Server will install using activemq docker image. You can disable it by changing the parameter jms.enabled=false.

External JMS instance can also be used instead of in-build JMS setup by adding the external jms url jms.jmsBrokerUrl. You can access it by using tcp port, for instance tcp://<JMS-URL>:61616.

• To set up the Repository DB in K8s cluster, run the below command. For this, we are using bitnami/postgresql Helm chart. See the Official Docs to configure the DB in cluster mode.

helm install repository bitnami/postgresql --set postgresqlPassword=postgres --namespace jrs --create-namespace

• Check the pods status and make sure pods are in a running state.

• If Namespace already exists, remove --create-namespace parameter.

• Go to js-docker/k8s and update the jrs/helm/values.yaml, see the Parameter section for more information.

• Set buildomatic.enabled=true for repository setup. By default samples are included, if it is not required, set buildomatic.includeSamples=false

• Run the below command to install TIBCO JasperReports® Server and repository setup.

helm install jrs jrs/helm --namespace jrs --wait --timeout 20m0s

Note: If Repository Setup fails in the middle then increase the timeout.

helm install jrs jrs/helm --namespace jrs --create-namespace

Note:

• If DB is not able to create using bitnami/postgresql Helm chart due to Persistent volume issues then create a Postgresql container from OpenShift console under Database section.
• It is always recommended to create an external database

By default, accessing the application from outside the cluster is disabled. To access the application from outside the OpenShift cluster, create a OpenShift Route's.

• It can be created directly from OpenShift console and select the jasperserver-pro service or

• It can also be created from oc command line tool.

  oc expose svc/<jasperserver-service-name>

• TIBCO JasperReports® Server application requires stickiness, to get the stickiness from the Route, run the below command from the oc command line tool.

  oc annotate route <route-name> annotation:router.openshift.io/cookie_name=JRS_COOKIE

• For securing the route see the OpenShift Official docs.

• If repository setup fails due to password authentication, remove the PostgreSQL helm chart, and the persistent volume claim and then re-install the PostgreSQL chart by setting the password --set postgresqlPassword=postgres.
• If you encounter an issue with deployment due to keystore issues, check the Keystore Generation steps to resolve this issue.