Jump to content
Changes to the Jaspersoft community edition download ×

Jitendra Mandalia

Jaspersoft Staff
  • Posts

    20
  • Joined

  • Last visited

  • Days Won

    1

Jitendra Mandalia last won the day on December 19 2023

Jitendra Mandalia had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jitendra Mandalia's Achievements

Apprentice

Apprentice (3/14)

  • Dedicated Rare
  • First Post Rare
  • Week One Done
  • One Month Later
  • Collaborator Rare

Recent Badges

1

Reputation

  1. Hi @sowmya.nallapati The Jaspersoft Studio 6.x officially supports Java 1.7. The Studio 7.2 onwards it supports Java 1.8. Though required java comes packaged with JSS installation. The reports might work with higher version of Java but it's not guaranteed. Thanks.
  2. There are no out of the box options in Jaspersoft to convert the Cognos reports to Jasper reports. Reports need to be created manually per report design. There is an option in Cognos where user can export the report design out in XML format. Jaspersoft reports supports JRXML. So one can also use XML from Cognos and manually convert those elements to JRXML.
  3. Hi, Can you share your JRXML file? Based on the output, it should be doable with headers in the column header and fields in the detail section. The screenshot shows two headers, that doesn't seem right. Thanks.
  4. Hi, I also like to suggest that Plugin is no longer available in the marketplace. We strongly suggest to use the full installation of Jaspersoft Studio. Sorry for the inconvenience. Thanks, Jitendra
  5. 1. Not sure. This seems something environment specific, where you seems to have some restriction with non-root user. Do you have SELinux enabled? That might be adding more restrictions to non-root user, and if so, you can try disabling the same. 2. Ideally this error shouldn't have anything to do with sample data, but if without that you are getting different error, it could be still related to permission issue. If not, did you try the solution provided in the referred article by adding kestore.init.properties file in the buildomatic folder? If it's there, it will be copied over to WEB-INF/classes and will use that to refer to keystore files. This is only needed if you have existing kestore file and installation isn't creating the same.
  6. Not sure otherwise. That should have worked, I don't see any other reason for this error. Can you check below article and see if changing the driver class, based on which Oracle version you have, removes this error? https://stackoverflow.com/questions/6202653/difference-between-oracle-jdbc-driver-classes
  7. Hi @katarzyna.wawer Which driver are you using? Can you check below article and modify your URL to see if that works? https://stackoverflow.com/questions/1054105/url-string-format-for-connecting-to-oracle-database-with-jdbc
  8. Hi So you have a JasperReports Server where you have the chromium installed and set up the path in the js.config.properties. Is that right? Where do you have the Studio? Is it on the same system? Do you have chromium installed on the machine where you have the Studio? As you are running the report in the Studio (Jaspersoft Studio, desktop app), you need to also make sure Studio is able to find the chromium. What is the OS you are using? To set the Chrome path in Studio... Navigate to Window > Preferences (or Jaspersoft Studio > Preferences on macOS). Go to Jaspersoft Studio option --> Select Properties. Find the property named net.sf.jasperreports.chrome.executable.path Provide full path to the Chrome executable on your system. Example: On Windows, it might be C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Save the updated path. Restart Jaspersoft Studio. Thanks.
  9. Hi You need to login as non-root jasper user to your instance and make sure the user has rights to install the software and access to the folders where software is installed i.e. /opt or /local and other required folders for installation. Refer to below article. The error you are seeing is related to permission, and if you have correct permission for the jasper user, you should be able to install the same. Thanks.
  10. Hi Can you provide more details? Which user you are using when logging in? Is this happening with superuser and jasperadmin user too?
  11. This article is obsolete. Below article is latest one in this series.
  12. Hi @hhom72 Yes, this option is only available for Commercial version from the newer JasperReports Server. The older version used to support the Log Collector for Community Edition.
  13. Hi @sugreevu.teja findFields is used to restrict the fields you want in the response. Are you trying to filter out the data using the date filter? Then you need to use findQuery option. i.e. { collectionName:'Employee', findQuery : { 'field1': 'value1', 'leave_period' : { $gt: "2021-11-16T00:00:00.000Z", $lt: "2021-11-18T00:00:00.000Z"} } } 'status_date' : { '$gte' : $P{StartDate}, $lt: $P{EndDate} } Please see the post below where I recently provided an example for date filter. Also check the MongoDB Query Language article specific to Jaspersoft shared before for more examples on how to filter using date fields.
  14. Hi @Jet_lag Please see below. 1. MongoDB connection: For this issue, there are a few things to check. Hard to say exact reason per your environment setup. 1.1 Verify server is available at the ip:port. As you suggested, it seems you are able to connect with MongoDB Compass UI. If so, also see firewall rules blocking such connection from Studio. 1.2 You can disable certificate validation for testing purposes. mongodb://xx.xx.xxx.xx:27017/[database] OR mongodb://xx.xx.xxx.xx:27017/[database]?authSource=xxx&readPreference=primary&directConnection=true&tls=false And see if one of these work to test the connection. 1.3 Check the MongoDB server logs for any more specific errors related to SSL connections or certificate validation. 2. There isn't direct match to elemMatch syntax but you can use similar to what is in the below example. $elemMatch: db.survey.find( { results: { $elemMatch: { product: "xyz" } } } ) Date Example without elemMatch: 'findQuery' : {'status_date' : { '$gte' : $P{StartDate}, $lt: $P{EndDate} }, 'name' : { '$regex' : '^N', '$options' : '' } } OR your example below. { collectionName:'Products', findQuery : { 'value.items.segment.departure.dateTime' : { $gt: "2021-11-16T00:00:00.000Z" }} } Thanks.
×
×
  • Create New...