elizam

Maps Pro uses Google Maps.  TIBCO Maps uses TIBCO GeoAnalytics Maps, which you need a separate license for.

You need to define roles in the application context file and set the rules that map information from your LDAP to  roles JRS.  The role will be created the first time a user with that role logs in. It's a  good idea to create test users for each role first so that you can set up the role permissions and make sure they are working as expected before going live. Role permissions can't be set in the application context file.

We don't have the resources to test every possible upgrade path, so we limit the officially supported upgrades.  This bug indicates that the direct upgrade likely no longer works:
https://community.jaspersoft.com/questions/1114551/migration-jasperreports-server-5-7

If you're running them as different users, or from different servers, or from different organizations, you can use a data source defined with an attribute:
https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v71/attributes-data-source-definitions
I don't know if there's any way to just pass an attribute using REST, with the same user/org/server setup.

In Jaspersoft Studio, select the field. 
Go to the Properties window, select the Text Field tab. Find the Pattern entry box and click "..."
In the pattern dialog, select the pattern you want -- in your case: Currency.  
 

For the first one, you could try advanced chart formatting:
https://community.jaspersoft.com/wiki/advanced-chart-formatting
see if setting
tooltip.valueDecimals to 0 works.
Documentation for that option is here: https://api.highcharts.com/highcharts/tooltip.valueDecimals
Note that not all HighCharts options will work, but they often will.

One way might be to containerize the jasperdb separate from the server image.  Then you could update the database container image by exporting/importing the latest db and then deploy both.

No.  An Ad Hoc view is not a report & is about the design of the data, not the content. You can create a report from an Ad Hoc view & schedule the report. 
Scheduling and Ad Hoc views are not part of the iReport Designer. Have you labelled this wrong?

There were some changes to font extensions since that was written. This might help:
https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v640/fonts

If you want two independent reports in the same file, one after the other, take a look at report books:
https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v640/report-books

The answer depends on how you want to create your dashboards and what you want them to do.  Overall, Jaspersoft Studio is a report-building tool and Jaspersoft Server is a web application that lets you display and share reports.  Frequently, you use them together. So you can:
Create a report in Jaspersoft Studio that looks like a dashboard. Then you still have to display it somehow. This could be in your own application. Use a commercial version of JasperReports Server to reports into a simple dashboard.  I believe this supports reports uploaded from Jaspersoft Studio as well as Ad Hoc reports built in the server.  Use visualize.js to create dashboards. This requires a commercial version of the server. Again, I believe the reports can be created directly on the server or uploaded from Jaspersoft Studio to the server. In general, you are more limited in scope in the reports you create directly on the server. You can create more elaborate reports in Jaspersoft Studio and upload them to the server. Once you have reports on the server, wherever they come from, you can display them in a dashboard using the simple dashboarding mechansim built into commercial versions of the server, or using visualize.js.
The visualize.js manual is here:
https://community.jaspersoft.com/documentation/tibco-jasperreports-server-visualizejs-guide/v640/api-reference-visualizejs

The whole purpose of the server is to act as a repository for reports. If you don't want to use that functionality, you'd probably be better off writing your own application directly on JasperReports.

"Data PreSorted" means that Jasper can assume that you have sorted the data already in your database. (This allows Jasper to omit some processing steps & optimizes performance.)  So it's going through assuming that Question 1 comes first, and once it sees Question 2, it ignores all Question 1s after that. Kind of the opposite of what you want.
You can sort in a couple of  ways:
In the query: Select * from orders where shipcountry = $P{country} order by shipcity
In the dataset: Select the root node of the report in Outline view and open the Dataset and Query dialog (or open the subdataset if you are using one). Use the Sorting tab to pick a field to sort by.

No you cannot create an ad hoc view from multiple Domains.  You can include multiple tables from the same data source in a single Domain, but to usefields from different tables in the same ad hoc view, those tables have to be connected via joins in the Domain.  So if you have tables A, B, C & D in a Domain, & you join A to B and B to C in the Domain, but have no joins to D, then you can use fields from A, B, & C in a single ad hoc view, but you can't add any tables from D.

I believe they have updated the JSON and XML data adapters to work similar to how the plug-in used to.  

Frames are now dynamic, not sure exactly when that happened (6.1?).  The size you make the frame on your canvas is the minimum size the frame will be when you run the report. What you need to do is position everything and then shrink the frame up. For example, if you make the frame only as tall as your first line, it will expand when it needs to.

(I'm afraid I'm too lazy to watch videos, so I hope this is right.)
You can join tables in a database to put them in a domain in JRS.  So if you have five tables in your database, and there is a way to join them all up, you can put them all in the same domain and then use them in ad hoc.  (Databases don't normally have domains so I'm guessing you mean tables).
The fields don't have to have matching *names*, but they have to make sense to match on. For example, if I have LAST in one table, and SURNAME in another table, then I can still make a join, because that makes sense.  But if I have a table that has NAME and it means Last Name, and another table with NAME and it means First Name, then making that join doesn't make sense.  So you are looking for a field that between the two tables functions as some kind of key field, whether or not it has the same name.
If you have tables in your domain and you have set it up so they are not connected to each other in any way (for example, you have A joined to B, and C joined to D, but no other connections), you can't use the disconnected chunks (sometimes called islands) in the same ad hoc. (So you have to choose between A&B vs. C&D.)   But if there is a field that it makes sense to join on (so say, A has Last and D has Surname), you can go in the domain and modify and make the join and then you can get all of them into the same ad hoc view. 
 

Yeah, it's the JSS manual:
http://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v630/user-interface-and-design-tab
Eclipse Interface
In Eclipse terminology, the initial layout of the Jaspersoft Studio interface is called a perspective. The default Jaspersoft Studio perspective contains an editor area and views. Some views appear by themselves, while others are stacked together in tabbed notebooks. You can open and close views and drag them to different positions in the Eclipse workbench.
 •To open a window you have closed, select Window > Open View from the menu. Select the window you want to open from the drop-down list. •To reset the interface to the default perspective, select Window > Reset Perspective. •To save a perspective, select Window > Save Perspective As and enter a name for your perspective. 

You can't do this directly in JasperReports Server.  I believe you could change the action when the report is opened and create an extra dialog that takes the info you want and then uses the REST API to set the datasource. That would take some programming.
You can instead attributes to set up a data source that takes information about the server/organization/user and selects the actual database based on those settings. That means that a user will only be able to access one database for that report, but that is the most common use case. (And the user won't have to know their database info.) 
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v630/attributes-data-source-definitions
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v630/managing-attributes

dashboards are only supported in the commercial version.

If this is in the server, you might be able to use attributes:
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v630/managing-attributes
However, you can't use report parameters in the query, because the datasource is loaded before parameters.

The screenshots and descriptions from the user guide are for the professional edition.  The Create option is not available in community because the only thing you can create directly in the community edition is a Data Source. Ad Hoc views, reports from ad hoc, Dashboards, and Domains are all pro only.  However, you can create reports in Jaspersoft Studio and upload them to the server. 

What you have is weekly (every sunday). If you really want monthly, you should select Dates in Month.

There seems to be a broken link in the page you sent.  Sorry about that, we sometimes have trouble with putting the doc on the web.  looking at the PDF version, I see it is in the Uploading Files section of this page:
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-rest-api-reference/v630/working-file-resources

You may be able to do this using attributes.  Look at these pages in the documentation:
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v630/managing-attributes
http://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v630/attributes-data-source-definitions