kcollins

By default, any ad hoc chart that uses integers as chart data will show the aggregated integers as decimals in the tooltip. If you hover over a bar of a bar chart for example, and integer that you would expect to show a 5 will show 5.0. To fix this do the following: Edit the ad hoc view, and click on the gear icon above the chart and select "Chart Format... ". In this menu, select "Advanced" > "Add New Property". Set the property as follows: Property = tooltip.valueDecimals Value = 0 Then save the ad hoc view. The view will now show integers in the tooltip rather than decimals.

If using TIBCO Jaspersoft® Studio and trying to create a data adapter that uses an IPv6 address to connect to a database, you may receive an error: java socketexception: protocol family unavailable. By default, there is a setting that forces the use of IPv4. To fix this to allow for IPv6, look in your installation folder for a file called "Jaspersoft Studio Professional.ini". Edit this file, and remove the line: java.net.preferIPv4Stack=true Then restart the application. This should then allow the use of IPv6 addresses.

To set the global CSV record delimiter in Jaspersoft Server using net.sf.jasperreports.export.csv.record.delimiter, you need to modify the jasperreports.properties file. Here's how to do it: Locate the jasperreports.properties file: This file is typically found in the /WEB-INF/classes/ directory of your Jaspersoft Server installation. The exact path might vary slightly depending on your server's deployment, but common locations include: <jasperserver-install>/apache-tomcat/webapps/jasperserver/WEB-INF/classes/jasperreports.properties <jasperserver-install>/WEB-INF/classes/jasperreports.properties Edit the file: Open the jasperreports.properties file with a text editor. Add or modify the property: Add or modify the following line to set your desired record delimiter. For example, to use a Carriage Return and Line Feed (CRLF) for Windows-style line breaks, you would add: Properties net.sf.jasperreports.export.csv.record.delimiter=\r\n Important Notes: You need to use escaped characters for special delimiters. For example: \r\n for Windows (CRLF) \n for Unix/Linux (LF) \t for a tab | for a pipe If you're setting non-printing characters like \r or \n, make sure you use the backslash to escape them. Simply typing rn will result in the literal characters "r" and "n" in your CSV, not a carriage return and line feed. Some older community discussions suggest using XML entities (like &#x000D;&#x000A; for CRLF) within JRXML, but for global server-side configuration in jasperreports.properties, the escaped characters (\r\n) are the correct approach. Save the file. Restart Jaspersoft Server: After making changes to jasperreports.properties, you must restart your Jaspersoft Server for the changes to take effect. Hierarchy of Property Settings: Keep in mind that JasperReports uses a hierarchy for property settings: Report Level (JRXML): Properties set directly within a JRXML file (e.g., <property name="net.sf.jasperreports.export.csv.record.delimiter" value="\r\n"/>) will override any global settings for that specific report. Global Level (jasperreports.properties):This file provides server-wide default settings. Application Context (applicationContext.xml):In some older Jaspersoft Server versions or for specific exporter configurations, settings might also be present in applicationContext.xml. If a property is set here, it often overrides jasperreports.properties. However, for the CSV record delimiter, jasperreports.properties is generally the correct place for a global setting. By following these steps, you can successfully set the global CSV record delimiter for reports exported from your Jaspersoft Server.

There is a known defect in Java that causes a memory leak in the way TIBCO JasperReports® Server maintains and cleans up temorary files. This is related to File.deleteOnExit(). In versions of JasperReports® Server 7.5 and prior, this mechanism is used which can cause a memory leak for long running systems. JasperReports Server also has other mechanisms that clean temprorary files, so File.deleteOnExit() is actually not needed. In future versions of JasperReports Server, this funtion will be disabled. In versions 7.5 and prior, there is a way to turn this funtion off: Edit the /WEB-INF/classes/jasperreports.properties file and add this line (requires application server restart): net.sf.jasperreports.virtualizer.files.delete.on.exit=false

In some cases you may want to allow non-admin users to create domains and datasources. By default, only admins have this ability. There are some configuration changes that can be made to allow a user with a non-admin role to create domains and datasources. These instructions apply to 7.1, 7.2, and 7.5. These instructions show how to allow non-admin users with a role called ROLE_NEWROLE to create domains and datasources In all versions (7.1, 7.2, and 7.5), the following change needs to be made in actionModel-navigation.xml. You need to add the role you want to allow to the following xml. You sill see this in main_create_mutton, note the addition of ROLE_NEWROLE to the testArgs: <condition test="checkAuthenticationRoles" testArgs="ROLE_ADMINISTRATOR, ROLE_NEWROLE"> <option labelKey="NAV_056_DOMAIN" action="primaryNavModule.navigationOption" actionArgs="domain"/> <option labelKey="NAV_058_DATA_SOURCE" action="primaryNavModule.navigationOption" actionArgs="dataSource"/> </condition>There are a couple additional changes that need to be made depending on what version you are running (7.1 vs7.2 and 7.5) In 7.1, the ROLE_NEWROLE role needs to be added to createSLDatasourceFlow and addDataSourceFlow in the flowVoter bean inside of the /WEB-INF/applicationContext-security.xml file. See below: <bean id="flowVoter" class="com.jaspersoft.jasperserver.api.security.FlowRoleAccessVoter"> <property name="flowAccessAttribute" value="FLOW_ACCESS"/> <property name="flowDefinitionSource"> <value> repoAdminFlow=ROLE_ADMINISTRATOR userListFlow=ROLE_ADMINISTRATOR roleListFlow=ROLE_ADMINISTRATOR editFolderFlow=ROLE_ADMINISTRATOR fileResourceFlow=ROLE_USER,ROLE_ADMINISTRATOR listOfValuesFlow=ROLE_USER,ROLE_ADMINISTRATOR reportDataSourceFlow=ROLE_USER,ROLE_ADMINISTRATOR inputControlsFlow=ROLE_USER,ROLE_ADMINISTRATOR tenantFlow=ROLE_ADMINISTRATOR createSLDatasourceFlow=ROLE_ADMINISTRATOR, ROLE_NEWROLE addDataSourceFlow=ROLE_ADMINISTRATOR, ROLE_NEWROLE userEditFlow=ROLE_ADMINISTRATOR roleEditFlow=ROLE_ADMINISTRATOR queryReferenceFlow=ROLE_ADMINISTRATOR searchFlow=ROLE_USER,ROLE_ADMINISTRATOR *=ROLE_USER,ROLE_ADMINISTRATOR </value> </property> </bean>in 7.2 and 7.5, you need to add the new role to the addDataSourceFlow in /WEB-INF/applicationContext-security.xml file, however you’ll notice that createSLDatasourceFlow isn’t present in this file. This is what allows the user to create domains. You’ll see below that a change needs to be made in applicationContext-security-pro-web.xml to allow t his in 7.2 and 7.5. <bean id="flowVoter" class="com.jaspersoft.jasperserver.api.security.FlowRoleAccessVoter"> <property name="flowAccessAttribute" value="FLOW_ACCESS"/> <property name="flowDefinitionSource"> <value> repoAdminFlow=ROLE_ADMINISTRATOR userListFlow=ROLE_ADMINISTRATOR roleListFlow=ROLE_ADMINISTRATOR editFolderFlow=ROLE_ADMINISTRATOR fileResourceFlow=ROLE_USER,ROLE_ADMINISTRATOR listOfValuesFlow=ROLE_USER,ROLE_ADMINISTRATOR reportDataSourceFlow=ROLE_USER,ROLE_ADMINISTRATOR inputControlsFlow=ROLE_USER,ROLE_ADMINISTRATOR tenantFlow=ROLE_ADMINISTRATOR addDataSourceFlow=ROLE_ADMINISTRATOR, ROLE_NEWROLE userEditFlow=ROLE_ADMINISTRATOR roleEditFlow=ROLE_ADMINISTRATOR queryReferenceFlow=ROLE_ADMINISTRATOR searchFlow=ROLE_USER,ROLE_ADMINISTRATOR *=ROLE_USER,ROLE_ADMINISTRATOR </value> </property> </bean>Then in applicationContext-security-pro-web.xml, you need to add your role to this line: <security:intercept-url pattern="/domaindesigner.html" access="ROLE_ADMINISTRATOR, ROLE_NEWROLE" />

This video gives an overview of the REST API reports service. This service allows you to run and export reports on the JRS server, as well as check the status of a report run.

JasperReports Library contains many samples for design, component, datasource and export-specific scenarios. For easy access you can run them directly within Studio via a few easy steps. They can be useful during the early learning phases of your implementation or during later phases when you encounter advanced JasperReport usage issues.

Most elements in a report have properties that drive their design behavior. In TIBCO Jaspersoft® Studio 7.1 we've enhanced the editor of these properties to make their usage easier. You can view and search for all possible properties, see which properties already have been explicitly modified, view descriptions of each property, and use the expression editors.

In this video, we demonstrate how to get familiar with Context groups and variables. Introducing this functionality into your jobs is one of ETL job design 'best practices'. It allows you to seamlessly run and deploy ETL jobs in various environments in your infrastructure. Useful resources: https://help.talend.com/reader/Z_OsHBEO1WAwU4an0EwqsQ/f7s_UThy0mFBC0VrzgeSFw https://help.talend.com/reader/WEEgRoxIy_iUMxRK3bopPQ/LfylTT_T~tBTu0nTJkDvcg https://help.talend.com/reader/St~M252yz9qZ1qf9VbrV4A/LBUqX4E7aNLwUPRr2EU1fA

This video will show you how to create an AWS datasource in JasperReports Server. The database will be created in AWS, and then an AWS datasource object is created in JRS to be used when creating Jasper reports.

In this video, we demonstrate how to export JasperReportsIO report execution to PDF and encrypt the resulting PDF file using a Jaspersoft ETL job. The goal of this tutorial is to introduce encryption functionality to report execution using JasperReportsIO REST API and Jaspersoft ETL Studio job. reports_jrio_encrypt_context.zip

In this video, we will show you how to setup anonymous access to a dashboard. The three files you have to modify in this video are: applicationContext-security-web.xml applicationContext-security-pro-web.xml applicationContext-security.xml Link for dashboard: http://localhost:8080/jasperserver-pr...

This video will give an overview of authentication using the JRS REST API, including a demonstration on how to authenticate to get a session ID that can be used in subsequent requests.

In this video, we will show you how to apply a color to dashlet. This is the configuration we are using in our override_custom.css file:div[data-componentid=Store_Type_by_City] { background-color:red; }

This video demonstrates how the Ad Hoc Cache can be monitored by using JConsole, which is a JMX agent.