Domenico Donofrio

When embedding an external sub-report using resource bundles files (meaning not contained in the same report unit of the master report), it is necessary to propagate the resource bundles to the sub-report which has been embedded as .jrxml file. One typical scenario deployed on the Jasper Reports Server is: - A folder containing the resource bundles. It will be referenced by the Master Report and the sub report when run autonomously. - a Master Report which embeds a sub-report as .jrxml file published on the server. - A Sub-Report Unit that can be run autonomously and uses the resource bundles from the external folder One important thing to notice is that the master report has to include the subreport element by passing to it the full parameter map which also includes the resource bundles file defined as resource of the master report. The resource bundle files, loaded on the Jasper server are linked to the master report that will be forwarding them to the sub-report by using the mentioned parameter ${REPORT_PARAMETER_MAP} - see previous image The same way, the sub-report unit running autonomously, will be linked to the same resource bundles file, so in case it is needed to modify the resource bundle, changing or adding a translation, the modification will have to be done only once, and both the sub-report run in stand-alone mode, both the one embedded, will benefit of the same update and the resource bundle file will have to be mantained in just one server's folder. Attaching also an example of master/sub-report. master_report_0.zip resource_bundles_0.zip sub_report_0.zip

When deploying a Dockerized version of JasperReports Server (https://github.com/TIBCOSoftware/js-docker/tree/main/jaspersoft-containers/Docker/jrs) it is possible to enable SSL security by using Nginx as a reverse proxy. This article explains how to configure a Nginx Docker Container and enable Https for JasperReports Server by using a self-signed certificate. 1 - Generate SSL certificates using OpenSSL After installing OpenSSL, for example by using Chocolatey in Windows, run the following command to generate a self signed certificate and related key (as included in the example attached, feel free to replace them with yours). openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout nginx-selfsigned.key -out nginx-selfsigned.crt 2 - Configure Nginx: Dockerfile example FROM nginx:1.17.4-alpine RUN rm /etc/nginx/conf.d/default.conf COPY nginx.conf /etc/nginx/conf.d 3 - Define a nginx.conf file to use the self signed certificates underscores_in_headers on; server { listen 443 ssl; server_name localhost; ssl_certificate /etc/nginx/certs/nginx-selfsigned.crt; ssl_certificate_key /etc/nginx/certs/nginx-selfsigned.key; access_log /var/log/nginx/data-access.log combined; location /jasperserver-pro { proxy_pass http://${JASPER_SERVER}:8080/jasperserver-pro; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real_IP $remote_addr; } } The JASPER_SERVER variable is set in the .env file as host.docker.internal and represents the Docker host IP. Please notice that it is not recommended to use localhost for Ngingx server/proxy_pass setting as the container would just refer to itself and would not reach the JasperReports Server running on another container. 4 - Setting up docker-compose There is another global variable defined for SSL certificate paths in the .env file (SSL_src). It is used in the docker-compose.yml file looks like this: version: '3' services: nginx: build: ./docker/nginx expose: - 443 - 80 ports: - 80:80 - 443:443 volumes: - ${SSL_src}:/etc/nginx/certs 5 - Run docker compose build and then docker compose up. If you see the nginx container up and running by using the command docker-compose ps, and you Dockerized JSR is also up and running, it can now handle https request to the server on the default port 443 thanks to the nginx container. This is very handy in case it is necessary to enable HTTPS like for instance when embedding visualise.js, and avoiding CORS problems. If after these steps, the proxying is not working well, after checking that the JRS containers and Nginx are up and running on Docker (docker ps), you might also check the Nginx containers logs which will highlight any issue in the communication between JRS and Nginx Docker containers. In attachment the complete example that I run on my Windows machine. ssl.zip