-
Posts
49 -
Joined
-
Last visited
Jivan Phadtare's Achievements
-
buildomatic commands for export and import the repository data in dockerized environment
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
In the JRS Docker environment, we often encounter situations where we need to export repository data without encryption to avoid decoding errors. Here are the alternative export and import commands that can be used in a Dockerized environment: Command to export repository data: ./js-ant export-everything -DexportFile=js-catalog-exp.zip -DexportArgs=\"--keyalias deprecatedImportExportEncSecret\" Command to import the repository data : ./js-ant import -DimportFile=JRS_802_Dashboard_Export_legacy_Key.zip -DimportArgs=\"--keyalias deprecatedImportExportEncSecret\" For more details, please refer to the following URL. https://community.jaspersoft.com/documentation/jasperreports-server/tibco-jasperreports-server-upgrade-guide/v900/jrs-upgrade-guide-_-upgrading/#upgrading_562921741_1127020 -
Setps to configure external db authentication for external user to login to the jasperserver.
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
External users not within the 'jasperserver' database can be authenticated to access Jasperserver. Below are the configuration steps to enable external database authentication: 1) Create an external database with any name to store external user details. Attached are sample tables created for user details, user roles, and organizations in "DB_Queries.txt". 2) Copy the "sample-applicationContext-externalAuth-db-mt.xml" file from ...\jasperreports-server-8.2.0\samples\externalAuth-sample-config\ and rename it as "applicationContext-externalAuth-db-mt.xml". 3) After renaming the file, edit the necessary bean to configure LDAP authentication. We have provided the working configured "applicationContext-externalAuth-db-mt.xml" file for Jasperserver version 8.2.0. To understand the changes, compare this file with the default "sample-applicationContext-externalAuth-db-mt.xml". 4) Place the edited "applicationContext-externalAuth-db-mt.xml" file in the location: ...\webapps\jasperserver-pro\WEB-INF. 5) Restart Jasperserver. 6) After the restart, log in using the external user ID and password, and specify the organization name during login. applicationContext-externalAuth-db-mt.xml sample-applicationContext-externalAuth-db-mt.xml DB_Queries.txt -
Date & Time are not consistent across all exported format
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
Issue : A report have parameter in footer called "CurrentDate" of "java.util.Date" type and default Value Expression is configured as "new Date()" (attached : "02243220.PNG") When this report published on JRS and tried to export into .xlsx then Date & Time are not consistent but while exporting into .pdf and .csv is shows exactly same as of GUI. Attached jrxml ("02243220_casetest_dev.jrxml") which contains below datetime format in footer section. "Report created on : "+new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format($P{CurrentDate}) Resolution : Exporting to unpaginated Excel involves regenerating the report in unpaginated format, which also implies reevaluating parameters/expressions/etc If you want to preserve the value of the parameter from the initial report generation, you can set the "net.sf.jasperreports.data.cache.included" property to true on the parameter <parameter name="CurrentDate" class="java.util.Date" isForPrompting="false"> <property name="net.sf.jasperreports.data.cache.included" value="true"/> <defaultValueExpression><![CDATA[new Date()]]></defaultValueExpression> </parameter> We have tested in local with above property and time is now consistent across all format. Case Reference : #02243220 -
In JRS 9.0 newly added input control value not updating in Dashboad.
Jivan Phadtare posted an entry in Troubleshooting
Jivan Phadtare posted an entry in Troubleshooting
Issue : Create Dashboard with multiselect query input control and try to add new input control value in the database table. Post adding input control into table, refresh the dashboard, newly added input control not visible immediately. Resolution : In JRS 9.0 version, It looks like, we introduced the cache for Input Controls, So Input Control values now are cached. To make dashboard IC visible immediately after chane in database, kindly turn off the below property from file : ...\webapps\jasperserver-pro\WEB-INF\applicationContext-cascade.xml Currently property value is by default set to "true" as below ------------------- <bean id="inputControlsCachingEnabled" class="java.lang.Boolean"> <constructor-arg value="true"/> </bean> ------------------- Kindly turn it off and set to "false" ------------------- <bean id="inputControlsCachingEnabled" class="java.lang.Boolean"> <constructor-arg value="false"/> </bean> ------------------- Please note that, restart of Jasperserver is required to make the changes reflected. We have tested this and IC in dashboard appearing immediately. -
How to turn off/hide the Alerts feature in JRS 9.0.0 from "Schedules and Alerts" screen.
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
Alerts feature from "Schedules and Alerts" screen can be turn off/hide by removing below property <simpleAction id="alerts" labelKey="server.monitoring.tab.alerts"/> from file : ...\webapps\jasperserver-pro\WEB-INF\actionModel-schedulesAndAlertsTabs.xml Note that - Jasperserver restart is required after updating the file. -
Hello, By looking to error it seems that the issue is in SMTP configuration. Check the SMTP server configuration in JasperReports Server to ensure that it is properly configured and accessible. Verify the SMTP server address, port, authentication credentials, and any other relevant settings. The error also suggest that invalid email adress. Could you please make sure email address is valid, you can test by directly putting email id without vairable.
-
Conncetion to Sybase SQL Anywhere 17
Jivan Phadtare replied to senhadji.lotfi's topic in Connectors and Platforms
Hello, Could you please try to check by selecting "Sybase (com.sybase.jdbc4.jdbc.SybDriver)" driver name without driver jar file and see if it works. If you still get classnot found exception, kindly kindly try to copy the driver jar file at studio installed location : ...\jrio\jrio\WEB-INF\lib\ -
How to change the oracle JDBC driver jar file name and version in JRS 9.0.0
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
During upgrade to JRS 9.0.0, customers encountered below error : ------------------------ [echo] Validating administrative database connection at jdbc:oracle:thin:@rk624932-ewo44:1521:mdb. Phase: [test] [echo] Specified JDBC driver jar not found on this path: [echo] C:/js-jrs_9.0.0_bin/jasperreports-server-pro-9.0.0-bin/buildomatic/conf_source/db/oracle/jdbc/ojdbc8-23.2.0.0.jar ------------------------ As per this error, it is looking for "ojdbc8-23.2.0.0.jar" jar file of version 23.2.0.0. From oracle website using below URL navigate to "23.2.0.0" version and download the jar file for this version and need to rename as "ojdbc8-23.2.0.0.jar". https://www.oracle.com/database/technologies/appdev/jdbc-drivers-archive.html The name of jar file is coming from "db.properties" file located at : ...\jasperreports-server-pro-9.0.0-bin\buildomatic\conf_source\db\oracle\ by default it's configured to the latest ojdbc8 version. ----------------- # for maven: artifact info so unit tests can get to the correct jdbc driver maven.jdbc.groupId=com.oracle.database.jdbc maven.jdbc.artifactId=ojdbc8 maven.jdbc.version=23.2.0.0 ----------------- If you wish to modify it, you can make changes to the properties mentioned above in the "db.properties" file. -
How to turn off/hide the Alerts feature in JRS 9.0.0 from "Schedules and Alerts" screen.
Jivan Phadtare posted an entry in How-To
Jivan Phadtare posted an entry in How-To
Alerts feature from "Schedules and Alerts" screen can be turn off/hide by removing below property <simpleAction id="alerts" labelKey="server.monitoring.tab.alerts"/> from file : ...\webapps\jasperserver-pro\WEB-INF\actionModel-schedulesAndAlertsTabs.xml Post removing this property Jasperserver restart is required in order by reflect the modified changes. -
Hello, If you are using war installation of community version then kindly make sure that you have file "keystore.init.properties" at location : "...\jasperreports-server-pro-9.0.0-bin\buildomatic\" which contains path of keystore files like .jrsks and .jrsksp. Keystore file "keystore.init.properties" by default contains below home directory where keystore files are generated during installation. #ks=C\:\\Users\\<usern_name> #ksp=C\:\\Users\\<usern_name>
-
Hello, Could you please raise this as an enhancement request to upgrade the postgres version on below URL https://jaspersoftideas.tibco.com/ This URL is managed by product team and they will consider this as an enhancement. As per the platform support guide document from : https://community.jaspersoft.com/documentation/?version=v8.2.0 we could see that for 8.2.0 version supported postgres versions are : 12, 13, 14 Hope this finds you useful.
-
Hello, This information is typically generated when a Java application crashes due to a segmentation fault (SIGSEGV) or other critical issues. It includes details about the error, Java version, problematic frame, stack trace, and more. If you need assistance in troubleshooting or understanding this error, you may want to analyze the provided log (/home/oas/hs_err_pid1793143.log) or seek help from your development team or Java support community. This error is more in context to Java than jasperserver.
-
Hello, The "Parameter REPORT_CONTEXT does not exist" message in the log is coming from the JRS server monitoring process and should not cause any issue for report execution. This annoying but harmless message has been reported internal and will get fixed later in upcoming release (no ETA available for the actual date yet).
-
The attached screenshot shows Tomcat has started but don't see any error in screenshot. could you please check first tomcat is up and running. You can use below URL to check Tomcat is up or not. http://<host>:<port>/ If tomcat you get error, then good idea to check the Tomcat error log in catalina.out file. <Tomcat_Installed_Path>\logs\ Log file : catalina*.out
-
Hello, Could you please attach the jrxml file of the report you tested. We will check in our intenal studio.
