Jump to content

swood_1

Members
  • Posts

    176
  • Joined

  • Last visited

 Content Type 

Forum

Downloads

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Security Advisories

Events

Profiles

Posts posted by swood_1

  1. Good that you worked out the page breaks.

    The key point in the stackoverflow post is creating a new Data Source object in the dataSourceExpression.

    You need to do something like: 

    dataSourceExpression><![CDATA[new JRBeanCollectionDataSource (fillList))]]></dataSourceExpression>

  2. Have a look at the video: Get step-by-step instructions on how to set up your first JasperReports IO project in JSS

    on https://community.jaspersoft.com/wiki/jasperreports-io-step-2

    You need to do a few things to make a Studio project = a JasperReports IO project.

    It is easier manage if, as Guilio says in the video, you have a subfolder in the project to be your repository root.

    Once you have a JasperReports IO project, the data adapter files in the "repository" (project)  will be accdo the ....ess relative to the repository root you set above. You wil not need to do the "../../data-adapters/DataAdapter.xml"

     

    Sherman

  3. Hi Kevin,

    I don't know how you received access to JasperReports Server commercial editions. Did your organization buy Jaspersoft:

    • directly from TIBCO Jaspersoft => Jaspersoft Support could help with this issuie
    • through software you provided by another vendor => contact the vendor

    From what I understand looking at the issue, you have set up a job with SAM OpCon that makes a REST call to the JasperReports Server.

    The 404 means that the job is not able to connect to the JasperReports Server. It can't find that endpoint.

    I can't see the actual URL you are using. That is the first thing to check.

    The JasperReports Server REST API to run a report is defined here: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-rest-api-reference/v750/reports-service

    http://<host>:<port>/jasperserver[-pro]/rest_v2/reports/path/to/report.<format>?<arguments>

     

    Sherman

  4. This is the relevant page in the 7.2 documentation: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v720/file-data-sources

    To get a data source type to appear in the Data Source maintenance screen, you have to comment out elements in the list with the "customDataSourcesToHide" bean ie.

    ..<!-- value> jsonDataSource</value -->..[/code]

    Did you restart the server after changing the file?

  5. A JasperReport is based on a fixed set of fields returned by a query. If the query can return variable columns, say:

    • make the column names abstract in the query - field1, field2
    • define the fields in the report to be the maximum number expected
    • if the query does not provide a particular column, the corresponding field in the report will be null
    • include logic in the report to manage field with content or null

    Sherman

  6. The JR library does not have a "compile as needed" feature.

    The JasperReports Server and JasperReports IO does. The first time after a report or subreport is published to JasperReports Server, the report is compiled and the bytecode is stored in the repository.

     

    Sherman

  7. Here is how you can use Attributes in Data Source definitions: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v750/attributes-data-source-definitions

    When you do something like "{attribute('host','Server')}" a value for the "host" attribute needs to be in the Server Attributes (Manage > Server Settings > Server Attributes) need to be set.

    "{attribute('someKey','User')}" implies a "someKey" needs to be in the User Atributes of the currently logged in user.

    "{attribute('someKey')}" implies that the Server will search for a "someKey" attribute in the following order: User (logged in user),  Organization hierarchy of logged in user, Server.

    Sherman

  8. When JasperReports Server authenticates via some form of single sign on, a user object is created or maintained in the repository.

    This exception comes from trying to save the user -> roles relationship.

    We have seen some race conditions where multiple users logging in at once cause contention.

    There should have been some cause mentioned in the stack trace about what the DataIntegrityViolation was.

  9. That exception comes from the web app not being able to access the keystore files.

    What directory did the keystore files end up in?

    Did the user running the web app process have access to those files?

    The encryption change in 7.5 has a major impact on deployment and operations. We are working to give folks the easiest path to adjust to this change. See https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75 

  10. You have options.

    1. Keep doing it as you are today with the servlet.

    • What APIs have been deprecated? Not on the JasperReports side.

    2. JasperReports Server

    • Has a REST API to run and export reports
    • Community version is AGPL licensed: not appropriate for embedding in your commercial application
    • Commercial Reporting Edition is the same as Community Server with some small extensions https://www.jaspersoft.com/editions

    3. JasperReports IO

     

    Sherman

  11. When you deployed the report to the JasperReports Server, what data source did you use for the Report Unit?

    A JasperReports Server data source is not a data adapter.

    You could try setting the report to use a data adapter on the server, as per https://community.jaspersoft.com/wiki/how-deploy-and-use-data-adapter-jasperreports-server-v56

×
×
  • Create New...