vchiem

There is one particular scenario where this can occur that I am aware of...although there may be other possibilities.
When there is the existence of the same Windows user, either as a local account or the same user in a different domain, and the installation is done with this user, then the script creates keystore files with 0 bytes...with the error Failed to create the keystore. 

If your mail server does not require authentication then ensure mail.smtp.auth is set to false in applicationContext-report-scheduling.xml the above config shows that this is already set. Perhaps the problem lies somewhere else but there is not enough information. You can enable mail debug to see more SMTP debug logging. Check this article on how to set mail.debug : https://community.jaspersoft.com/wiki/gmail-smtp-report-jobs-failing-smtp-authentication-error-despite-correct-username-and-password
 

Start by looking at the Installation Guide downloadable from the community docs section.

Installation should really be on a certified version of Mac OSX. The supported platforms guide that comes with each release will list out the versions. Catalina would be 10.15 which is not certified even on the current 7.5 version. However, there is a community article on how to get the install to run on Catalina.
https://community.jaspersoft.com/wiki/how-run-bundled-installer-tibco-jasperreports-server-macos-1015-catalina
 

The error represents a connection problem to the postgres database. 
So it is essential to firstly know whether the postgres is running and on what port number (default port is 5432). 
Once you know this information, you can use this to force the connection with extra parameters passed with the pg_dump command :
-h host 
-p port
-U username
-W
You can use this postgres command line reference as a guide:
https://www.postgresql.org/docs/9.3/app-pgdump.html
If it is still an issue and the error that you are getting remains EXACTLY the same then probably there is an incorrect path to socket. Backup tried to connect to /var/run/postgresql/.s.PGSQL.5432 but it does not exist. You can check this article:
https://stackoverflow.com/questions/31645550/why-psql-cant-connect-to-server
to check for the location of the socket file and verify the config files  pg_hba.conf and postgresql.conf accordingly.
There are a few comments that mentions to check for unix_socket_directories parameter setting.
I also recommend to check the for this setting as well:
listen_addresses = '*'

There is the Horizontal LED widget under "Components Pro" but I think it is only available in Commercial editions. 

 

Not sure why your administrator is seeking another solution but PhantomJS is required.
https://community.jaspersoft.com/wiki/dashboard-renderer-not-found-or-failed-start-please-contact-your-system-administrator

In the Dataset and Query dialog of the main report there is the "Data preview" tab. 
You can test whether data is feeding into this report by clicking on Read Fields and then Refresh Preview Data. If you can see data, then revise the design. Or perhaps start a blank report again and simply add one field to the detail band and see if the report previews with data. 
 

Answer to title subject is No.
JasperReports Server 7.2 supports Tomcat 9.0.1 to 9.0.17.
If your issues occur on a certified combination then it is best to check the jasperserver log for details of error. 

The 7.2 commercial editions has this problem as well. No fix yet at this stage. Best to adapt (ignroe) until there is a fix.  

The sql query behind each report is part of the report design but upon publishing, there is no retyping of query but rather a selection of data source or query where either of these can be selected from the repository.  

Unfortunately there's no direct printing without viewing first.  There is an existing enhancement request but not part of any near future plans.

There are 2 errors here. For first error, ensure the owner of the table qrtz_fired_triggers is the username specified in the buildomatic default_master.properties file. You can determine the owner of the table by entering pgAdmin and looking at the table properties. The second error appears to relate to a permissions issue. Check whether the install is done under an admin account or whether the file to be copied or deleted is opened/in-use, locked etc. 

It is important the wiring of the parameter/s between main and subreport is correct and this includes case sensitivity. 
Here is an example for a department main report with employee sub report using just one common parameter, DEPT_ID:
Main report 
Query :
select * from department where department_id=$P{DEPT_ID}
parameter defined:
DEPT_ID (Is For Prompting = true)
Subreport tab:
Expression = "employeesub1.jasper"
Connection Expression = $P{REPORT_CONNECTION}
Edit Parameters button
Name = DEPT_ID
Expression=$P{DEPT_ID}

Sub report (employeesub1.jrxml)
Query:
select * from employee where department_id=$P{DEPT_ID}
parameter defined:
DEPT_ID
I attached the jrxml files as well. Good luck.

It may not appear in the drop down because the drop down references drivers that were bundled.. not custom ones. It can still work though. Check this : 
https://community.jaspersoft.com/wiki/how-add-custom-jdbc-driver-jaspersoft-studio
 
 

You can find it in the <js-install> dir eg. /opt/jasperreports-server-x.x.x directory
./ctlscript.sh start
If you are unable to locate the script then likely the install was not a bundled install so in which case you can then start the JR server as such:
<Tomcat>/bin/startup.sh
See the Installation guide for more information.

Not sure what your execution involves but if you are exporting to XLS format then the error can be due to a number of columns limitation in Excel 2003. Can try to export to XLSX instead.

Version 6.2.1 onwards for High Charts, 3D is supported. Works only on Pie, Column, and Bar Chart types
Check this article:
https://community.jaspersoft.com/wiki/advanced-chart-formatting

Can try setting:
com.jaspersoft.jrs.export.xls.paginated=false
in classes/jasperreports.properties and restart the JR server.

Please see this article which refers to the -Xmx parameter across 3 files.  
https://community.jaspersoft.com/wiki/how-fix-java-heap-space-error-may-occur-during-import-huge-repository-linux-os
 

I think this may be related to an open defect (ref JS-32296 Chart Hyperlinks not working for Date field) where the problem relates to data format passed from one dashlet to another. Sorry...unable to provide any further info re any workarounds.

If you are referring to the + and - clicks that you see in the adhoc editor to expand or collapse the rows or columns, then the adhoc report and the dashboard does not have this feature. But there is an enhancement request opened for it already (ref JS-32905). There's no further info on the ER at this stage.  

For existing tables, I suppose you mean tables that are already part of the Selected Tables pane in the Tables tab and Joins tab. I have added new test columns to an existing table in an existing domain and simply by clicking on "Edit with Domain Designer" and expand the table, the new columns appear immediately in the table that selected in the Selected Table and its reflected in the Joins tab. I am using JRS 6.3 though.  I wonder whether this is attributed the difference in JRS versions. 
Try doing a quick test on sample Foodmart database... Create a domain via use domain designer and use existing table, then add a column to the database table structure and then close out designer and reopen designer to see the new column reflected in the Tables and Joins tab. 

I believe this related to the following defect. It was reported for JRS 6.1 and 6.2 JS-32162: Access is denied when creating a Domain-based Ad Hoc view on Execute Only datasource A fix is scheduled for an upcoming release targeted at the end of the year. The workaround is what you have already done. nothing else is required...set read-only permission to the datasource