vchiem

Issue:A typical scenario is an upgrade of TIBCO JasperReports® Server from v7.5 to v8.0 where the user runs the following export command from the TIBCO JasperReports® Server v7.5 buildomatic directory: ./js-export.sh --everything --keyalias deprecatedImportExportEncSecret --output-zip /tmp/uat-7.5.2-01.zip or (for users only): ./js-export.sh --users --keyalias deprecatedImportExportEncSecret --output-zip /tmp/uat-users-7.5.2.zip Under the TIBCO JasperReports® Server v8.0 buildomatic, importing the catalog failed to complete with "Weak password": Buildfile: C:jasperreports-server-pro-8.0.2-binbuildomaticbuild.xml [exec] Result: 128 [echo] Back-End version: fatal: not a git repository (or any of the parent directories): .git-SNAPSHOT [echo] Front-End version: fatal: not a git repository (or any of the parent directories): .git-SNAPSHOT [echo] Maven settings: C:/jasperreports-server-pro-8.0.2-bin/buildomatic/build_conf/default/maven_settings.xmlimport: [echo] --- (import-export.xml:run-import-export) archiveArg = --input-zip=C:/jasperreports-server-pro-8.0.2-bin/buildomatic/uat-users-7.5.2.zip --- [echo] dbType = postgresql [echo] jdbcJar = postgresql-42.2.20.jar [echo] currentConf = C:/jasperreports-server-pro-8.0.2-bin/buildomatic/build_conf/default [echo] importExportConfig = C:/jasperreports-server-pro-8.0.2-bin/buildomatic/conf_source/iePro [echo] [echo] Validating JasperServer database connection at jdbc:postgresql://xxxxxxxxx:5432/<db>. Phase: [import-export-test][advanced-sql] Executing commands[advanced-sql] 1 of 1 SQL statements executed successfully [echo] Connection OK [java] First resource path: C:jasperreports-server-pro-8.0.2-binbuildomaticconf_sourceiePro [java] Loading configuration resources [java] Initialization complete [java] Using default importCommandBean command bean [java] Processing started [java] Using com.jaspersoft.jasperserver.export.io.ZipFileInputFactory input factory [java] Using importerPrototypePro importer prototype bean. [java] Invoking module com.jaspersoft.jasperserver.multipleTenancy.export.MultiTenancyAuthorityImporter@1b70e1bb [java] Updated user superuser [java] Weak password.BUILD FAILEDC:workjasperreports-server-pro-8.0.2-binbuildomaticbinimport-export.xml:235: The following error occurred while executing this line:C:workjasperreports-server-pro-8.0.2-binbuildomaticbinimport-export.xml:168: Java returned: -1[/code] Note: This error can occur even if users are internally defined users. The import can also fail if the import was done through the TIBCO JasperReports® Server Import page online. IMPORTANT: For other potential causes of the 'Weak Password' error please see this article: The Command Line Import Stops with a "Weak password" Error Solution: The cause of the problem is the export file content containing a bad/wrong encryption of users passwords. There are two different sets of keystore files (ks/ksp) referenced by buildomatic and by TIBCO JasperReports® Server which is likely to be due to having two different user accounts, one account for installing buildomatic (jasperadmin) and one for installing the TIBCO JasperReports® Server (tomcat): Buildomatic buildomatic/keystore.init.properties has entries: ks=/home/jasperadmin ksp=/home/jasperadmin TIBCO JasperReports® Server WEB-INF/classes/keystore.init.properties has entries: ks=/home/tomcat ksp=/home/tomcat If we take into account that TIBCO JasperReports® Server using one keystore, and buildomatic using another, here is how the export flow will look like: 1. TIBCO JasperReports® Server running - passwords inside repo db are encrypted using tomcat.passwordEncSecret 2. buildomatic export - uses buildomatic.passwordEncSecret and decrypts the user password from db into plain text 3. buildomatic export - uses deprecatedImportExportEncSecret and encrypts the user password, and puts it into export zip In step 2, buildomatic uses a totally different key to decrypt passwords and definitely can produce messed up strings and step 3 will add this string to the exported zip file Even if the import succeeds which can happen if the encrypted password passes the password-matching check, the imported password string stored in the repository will cause TIBCO JasperReports® Server users to fail to log in with password credentials failure because TIBCO JasperReports® Server uses a different set of keys. Steps: On the source server instance (for this scenario it is TIBCO JasperReports® Server v7.5): 1. Backup /home/jasperadmin/.jrsks and .jrsksp before deleting them 2. Confirm there is no environment variables set with ks and ksp 3. Edit buildomatic/keystore.init.properties and set ks and ksp to point to the JRS keystore files: ks=/home/tomcat ksp=/home/tomcat 4. chmod -R 644 .jrs* and confirm that the user which is used during export (ie. the user logged into linux, jasperadmin) can read these files 5. Perform the command line export using the deprecatedImportExportEncSecret key 6. Check that during export, keystore files were not created under /home/jasperadmin On the target server instance (for this scenario it is TIBCO JasperReports® Server v8.0): 7. Import the exported zip file using the deprecatedImportExportEncSecret key Note: Specific to TIBCO JasperReports® Server 7.5 only, there was an extra requirement to update the keystore files which details steps to base64 decode the .jrsksp file, modify the ksPath property and base64 encode the file back. Refer to "Updating Keystore files" from https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75. This extra step is no longer required from TIBCO JasperReports® Server 7.8 onwards. Note 2: One way of checking whether the keystore files between two locations are the same is to run an md5 checksum on the .jrsks files. ReferencesFor other potential causes of the 'Weak Password' error please see this article: The Command Line Import Stops with a "Weak password" Error

Sample Report: HTML5 ArcGauge Chart with property to increase the arc width (thickness). The arc in the Chart is rendered as a solid gauge with innerRadius set. An example jsfiddle is of this chart is : https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/plotoptions/solidgauge-radius/ The following property can be added to render the size of the arc which is by increasing or lowering the innerRadius. The lower the percentage, the greater the thickness of the arc. <hc:chartProperty name="series[0].data[0].innerRadius"><hc:propertyExpression><![CDATA["20%"]]></hc:propertyExpression></hc:chartProperty>[/code] Report template that can be opened in TIBCO Jaspersoft Studio is attached.

Issue:After exporting an Ad Hoc Report to PDF output, the title of the exported PDF has the name "Ad Hoc Report". How can this title be changed to a different name like "Any Name Report"? Solution:PDF document metadata properties including the Title can be changed with the following available properties: net.sf.jasperreports.export.pdf.metadata.author net.sf.jasperreports.export.pdf.metadata.creator net.sf.jasperreports.export.pdf.metadata.keywords net.sf.jasperreports.export.pdf.metadata.subject net.sf.jasperreports.export.pdf.metadata.title These properties correspond to the metadata information when you open the File -> Properties menu of the PDF document using Acrobat Reader. For report templates created in TIBCO Jaspersoft® Studio, you can add the following property to the report's main properties: <property name="net.sf.jasperreports.export.pdf.metadata.title" value="Any Name Report"/> This property also can be added globally to the TIBCO JasperReports® Server's jasperreports.properties file located in the WEB-INF/classes directory. However, if it is specified at the report level then the property at the report level will take precedence. In the case of exporting Ad Hoc Report to PDF, the ad hoc report template has this property pre-defined with: <property name="net.sf.jasperreports.export.pdf.metadata.title" value="Ad Hoc Report"/> but you can use TIBCO Jaspersoft® Studio to navigate to the TIBCO JasperReports® Server repository and open the Ad Hoc Report's report template named mainReportJrxml. Make the change to the property before saving the report and publishing the report to the server. After logging out of the TIBCO JasperReports® Server and logging back in to perform the next PDF export, the title change should be reflected in the PDF document properties.

Issue: For HTML5 Charts, when switching from "Use an expression to create your series" to "Define your series manually", a dialog box with the message "Pay attention you risk to lose previously set series expression. Do you want to proceed?" appears. When clicking on either the "Yes" or "No" buttons, the message prompt does not close and loops continuosly. The user has to manually kill the Jaspersoft® Studio process. The steps to reproduce this issue are as follows: 1. For a HTML5 Chart, click on "Edit chart properties" 2. Switch to the Data Configuration tab 3. Click on "Switch to simple configuration" 4. Change to "Use an expression to create your series" and enter a value for "Series Expression" 5. Switch to "Define your series manually" 6. A dialog box appears which will not close regardless of any button being clicked Solution:This is a UI defect in Jaspersoft® Studio 7.5.0 and was fixed in Jaspersoft® Studio 7.8.0 (and later). There is no fix for this issue in Jaspersoft® Studio 7.5.0 and when the issue surfaces, the user needs to kill Jaspersoft® Studio before starting it up again. If the user cannot switch to "Define your series manually" even after restart, then the only option would be to identify the relevant section in the source code (in the Source tab) and remove/modify it to break the looping effect. This is a cumbersome way around it and the problem can re-occur. The best solution is to upgrade Jaspersoft® Studio to the latest version (or to at least version 7.8.0). Related Articles: JSS-2744: Unable to navigate between the option to define the series as an expression and define the series manually once series expression provided

Issue:In Ad Hoc Editor, we have an Ad Hoc Crosstab with a filter that filters on the number of records to display. When running a large Ad Hoc Crosstab View, the crosstab displays all the rows in "Full Data" mode when the number of records is 99,999 or less but it displays nothing more than "Totals" when the number of records reaches 100,000. Working OK Not Working How can this be resolved so that the Crosstab displays the records for 100,000 or more ? Solution:The following DEBUG (or INFO) can be set under Server Settings -> Log Settings page: com.jaspersoft.commons.datarator.WorkingDataSet (Ad Hoc WorkingDataSet) to see whether the Ad Hoc Crosstab has reached the axis node limit. The following message may (or may not) be captured in the log file: "Axis node limit has been reached. Crosstab will show only totals instead of all nodes. Please increase axis node limit to see more data." The above the message is logged from TIBCO JasperReports® Server version 8.1 onwards. Increase the axisNodeLimit value in the ..WEB-INFapplicationContext-datarator.xml file (line 238) : <bean id="dimensionDataSetTemplate" parent="workingDataSetTemplate" class="com.jaspersoft.commons.dimengine.DimensionDataSetImpl" scope="prototype" > <property name="axisTransformerFactory" ref="axisTransformerFactory"/> <!-- absolute limit on how many nodes can be in any axis --> <property name="axisNodeLimit" value="100000"/> </bean> [/code] Note: The changes requires a restart of the TIBCO JasperReports® Server.

Issue:When a report is published to the TIBCO JasperReports® Server, it is published with the default report name as "main_jrxml". And when using TIBCO Jaspersoft® Studio to save this published report locally, it will prompt and save as "main_jrxml" by default but can manually be overridden. Is there any configuration that allows users to change the default report name and label ? Solution: The "main_jrxml" is the hardcoded default for the report name and label. When a report is published to the TIBCO JasperReports® Server, this is what is used as the report's name and label. Starting from TIBCO Jaspersoft® Studio 7.9+ we have an enhancement which allows users to specify the report name and label. We addressed this feature in: JSS-2899: Added option to rename main_jrxml file under report unit when deploying it to JasperReports Server. Under Windows -> Preferences -> Jaspersoft Studio -> JasperReports Server Settings, there are 2 extra text fields: Default Main Report Label Default Main Report Name and the user can specify a name and label for reports deployed to the TIBCO JasperReports® Server to override the default "main_jrxml". All reports published to the TIBCO JasperReports® Server will have this new name and label and when the user Save the report locally it will save with the new specified name.

Issue:tSendMail allows you to set the encoding, but it appears that this encoding setting only applies to the message. Looking at tSendMail_main.javajet, the "<%=encoding %>" setting is not applied to the subject. subjectmsg_<%=cid %>.setSubject(subject_<%=cid %>);messagembpText_<%=cid %>.setText(message_<%=cid %>,<%=encoding %>, "<%=mimesubtype %>");mp_<%=cid %>.addBodyPart(mbpText_<%=cid %>);[/code]How can the encoding be applied to the subject ? Solution:The "<%=encoding %>" setting is not in the code for subject and this was reported in Talend Defect/Enhancement incident system as: TDI-18853: When use tSendMail, "encoding" of Advanced setting isn't reflected to Subject and Sender's name. The issue has not been addressed but the following workaround can be used: Add to the startup (ini / bat file) when launching JETL Studio. -Dfile.encoding=UTF-8

Issue:We have modified the below configuration files to change the default date format and restarted the TIBCO JasperReports® Server : ..WEB-INFbundlesjasperserver_config.properties: from: date.format=yyyy-MM-dd to date.format= dd-MM-yyyy ..WEB-INFbundlesadhoc_masks.properties: added: ADH_100_MASK_date_3 = dd-MM-yyyy After logging into the TIBCO JasperReports® Server, we ran a dashboard containing an Ad Hoc view with a date filter in a dashlet. The date format from the date filter correctly displays dates in the format of dd-MM-yyyy. However, after running the same dashboard using visualize.js, the date format from the date filter incorrectly displays dates in the default format of yyyy-MM-dd. Solution: This is a known defect that has been fixed in the following cumulative hotfix: hotfix_JRSPro8.0.2_cumulative_20220609_1155.zip The specific defect incident is: JS-65763 [case #2099441,+1] Non Standard US Date format is not working with date field in JRS 7.9 cascading IC To resolve this issue, download the above mentioned hotfix (or a later hotfix) from: https://support.tibco.com/s/hotfixes and follow the instructions documented in the readme.txt (located under 'jasperserver-pro' sub-directory). It is important to follow the additional instructions at the end of the readme.txt file pertaining to this specific defect: Details for JS-65763 fix: The fix introduces ability for Input Controls to use configurable`date.format`, `time.format` and `datetime.format` formats declared in the `jasperserver_config.properties` file.To enable feature:1. Open `js.spring.properties` file2. Comment out `bean.calendarFormatProvider=isoCalendarFormatProvider` line3. And uncomment `bean.calendarFormatProvider=messagesCalendarFormatProvider` line[/code]Note: The defect was reported in TIBCO JasperReports® Server 7.9.0 and hence this issue should also be observed in 7.9.x which has it's own corresponding hotfix.

Issue:After running a HighCharts (HTML5) Bar Chart report on the TIBCO JasperReports® Server, the bars in the chart are displayed as expected on the report viewer UI. But after exporting the report to any output format (PDF, DOCX, PPT XLS etc), the length of the bar/s is either not visible or does not correspond to the same bar length as displayed on the report viewer. Similarly, when running the report in TIBCO Jaspersoft® Studio, only the HTML output displays the bars correctly but other output formats including the Java output, exhibits the same problem. The js.config.properties file was configured to use the chromium engine for graphical rendering of charts. Solution: The cause of the problem was determined to be because of a specific property, plotOptions.series.animation (true), in the report template. The setting of this property allowed the correct rendering of the bar chart only in HTML output or on the TIBCO JasperReports® Server report viewer. By disabling the animation property: <hc:chartProperty name="plotOptions.series.animation"> <hc:propertyExpression><![CDATA[false]]></hc:propertyExpression></hc:chartProperty> [/code]the chart should then work for all output formats.