vchiem
-
Posts
443 -
Joined
-
Last visited
Content Type
Profiles
Forum
Events
Featured Visualizations
Knowledge Base
Documentation (PDF Downloads)
Blog
Documentation (Test Area)
Documentation
Dr. Jaspersoft Webinar Series
Downloads
Posts posted by vchiem
-
-
If the version it is not listed in the Platform Support Guide then it means it has not been certified for that version. Whether the error is because of the of the incompatibility between the JasperReports Server and the version of Red Hat is another matter. It does look like an OS error and it might be worthy to google the error for situations where such errors can occur.
-
The Access Denied exception is because the permissions assigned to the Audit Domain for ROLE_USER is "No Access". If you allow more permissions to this (eg Administer permission) as well as the data sources that the Audit Domain is built upon, then a non Admin user should be able create the Ad Hoc view off the Audit Domain.
But as per page: https://www.jaspersoft.com/editions Professional Editions do not have Audit Logging license, although I think this would generate a different error message or even if there is no error message then the feature wouldn't work. The "About TIBCO JasperReports Server" link dialog shows AUD feature code for Audit Logging feature and if you have this code then you have the enabled feature.
-
net.sf.jasperreports.engine.JRDataSource is inside jasperreports-6.20.0.jar so it is not picking up the jar. Not sure what lib folder you are referring to but maybe it is not the correct lib folder.
-
Try using an oracle jdbc driver that is compatible with both oracle database versions.
-
-
The error is generic. It is best to open the jasperserver.log under WEB-INF/logs and inspect the error associated to the UID.
You can check this article for gmail setup:
-
You can follow the same approach as this:
https://community.jaspersoft.com/wiki/upgrading-jasperreports-server-710-711
-
404 means the tomcat did not start up properly. Check the Tomcat log files to see the exceptions and work from there.
-
Best to check the application server log for any errors. eg catalina.out for Tomcat.
-
Maybe this can help :
https://community.jaspersoft.com/questions/1111616/unable-connect-remote-mongodb-data-source
Further you can test in Studio with the test button to test the URL. This is step 2.
https://community.jaspersoft.com/wiki/mongodb-japserstudio-connection
-
Please refer to the Studio user guide on how to create font set. Then export to PDF will pick up the font.
-
Please Refer to the Installation guide as it contains all the steps needed to install on Linux.
-
You need default_master.properties for the install. Please refer to the Install guide for steps.
-
It connects fine..just failed to upload. Probably a permissions related issue preventing the putting of the file in the location.
If you want to see the PUT operations with the actual path then enable the logger component:
com.jaspersoft.jasperserver.api.engine.common.util.impl.FTPUtil
in the Server Settings -> Log Settings page (need superuser account)
More information on debugging FTP can be found in this wiki article:
https://community.jaspersoft.com/wiki/debugging-ftp-connection-scheduled-report-jobs
The putFile method has following code:
private static void putFile(FTPClient ftpClient, String fileName, InputStream inputData) throws Exception { if (ftpClient == null) { throw new JSException("Please connect to FTP server first before changing directory!"); } if (log.isDebugEnabled()) { log.debug("START: FUT FILE = " + fileName); } ftpClient.setFileType(2); boolean state = ftpClient.storeFile(ftpClient.printWorkingDirectory() + "/" + fileName, inputData); if (log.isDebugEnabled()) { log.debug("END: FUT FILE = " + fileName + " STATE = " + state); } if (!state) { throw new JSException("Fail to upload file " + fileName); } }[/code]
-
There is already an internally defined user. If you want to log in as this user as an external LDAP user, then the internal user must not exist because it will sychronize the external user and mark it as 'externally defined'. The admin user or superuser can manage users.
-
The service pack can be applied on top of 8.0.0 in the same way as that of the hotfix application...and the instructions are in the readme.txt under the subdir "jasperserver". You can see the file size difference. The bin zip version contains the buildomatic files and the jasperserver.war and is there for users to do full install using the install scripts or actual upgrade using upgrade scripts. The instructions for install and upgrade should be in the actual install and upgrade guides. If your upgrade involves just extracting the bin version zip on top of existing 8.0.0 then that is incorrect...the service pack does this...much more quick and easy.
-
It looks like a problem with the jasperserver.tld. But usually we do not get this error upon boot unless something changed in the Tomcat context.xml that triggers the check.
But you can try to manually rectify the file. The <info> should come after the <bodycontent> so that it confirms to the matching pattern that it expects. So you can try to shift the <info> down and this is should be done to the xssNonce tag name as well.
<tag> <name>out</name> <info>Tag surrounds JSP code in which EL expressions should not be XML-escaped.</info> <tagclass>com.jaspersoft.jasperserver.war.tags.JasperOutTag</tagclass> <bodycontent>JSP</bodycontent> <attribute> <!-- Determines whether characters < > ( ) ; ' " in EL expression values will be converted to their corresponding character entity codes. Default value is false. --> <name>escapeScript</name> <required>false</required> </attribute> <attribute> <!-- When true, escapes the contents with UTF-8 versus entity codes Default value is false. --> <name>javaScriptEscape</name> <required>false</required> </attribute> </tag>[/code]
-
-
The reports service call format is:
http://<host>:<port>/jasperserver[-pro]/rest_v2/reports/path/to/report.<format>?<arguments>
Best thing to do is to log in to the JR Server as 'jasperadmin' and determine the exact path by looking at the properties of the report which can then the path to use for the REST call.
-
The location specified is under 'jasperserver-pro' but I believe the community edition has a different webapp name of 'jasperserver'. The main file is resource.add.files.js so if you search the whole directory and can find it then likely that is the one to edit.
-
If you mean single select input controls then they return a single value and cannot be a collection type ($X), rather the $P be used.
-
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.
-
Depending on the version of JR Server, it should already come bundled in. The AutoRest driver looks like this "TIautorest-6.0.0.004291.jar" and resides in the WEB-INF/lib directory. That is the version bundled in with the latest v8.0.0. Previous releases may have earlier versions of AutoRest driver.
For JS Studio, do a search for TI*.jar and it should be there amongst the other drivers. (mine is in C:Program FilesTIBCOJaspersoft Studio Professional-8.0.0configurationorg.eclipse.osgi41.cplib)
-
The closest configuration matching this would be to set autoCompleteLoginForm to false. Refer to the Security Guide Chapter 5. When false, the server sets autocomplete="off"
on the login page and browsers will not fill in or prompt to save Jaspersoft passwords
Print to screen based on value
in Products
Posted
Static text cannot be changed. Use a text field with reference to the DB field using $F{U_Tipo_AT} in the expression. The Title can be a text field.