joepmo

We recently switch from the old iReport Designer to JasperSoft Studio and I am struggling with what it seems should be a simple issue that has me flummoxed. When I open a .jrxml file from the file system it opens it in studio and append an "_1" to the file name. For example if I open ABC.jrxml in studio it comes in as ABC_1.jrmxl. I am sure this is a setting somewhere that I have incorrect by I cannot seem to figure out how to prevent this. Basically I want to open ABC.jrmxl, make my edits and save it as the same file name. Just not sure why Studio keeps wanting to make it a new file name. Thanks. Joe

We are currently using Jasper Server 3.71 with a MySql database. I am in the process of updating to Jasper Server 6.3. In reading the documentation it appears that Jasper has switched from MySql to PostgresSQL as the preferred database. I am at the point where I have exported/backed up the server and the respository and I am at the stage of configuring the buildomatic scripts. I am trying to find out if the buildomatic script will handle migrating to the new database during the upgrade or if the proper order would be be to upgrade to the MySql version 6.3 and then from there switch to the PostgresSQL version. Thanks.

I am really struggling to wrap my hands around a query I am trying to execute in iReport 4.5, I cannot seem to get the right combination of options set in iReport to get the correct data set returned for my query. Report Query is as follows SELECT AccountNo, CustomerNo, ApplyToInvoiceNo, SUM(Amount) AS Balance,Min(EffectiveDate)as InvoiceDate FROM ARDetail WHERE EffectiveDate<=$P{CutoffDate} GROUP BY AccountNo, CustomerNo, ApplyToInvoiceNo HAVING SUM(Amount) <> 0 ISSUE When prompted I enter 12/31/2011-- no time prompt included. Yet when the report completes and and I print the prompt on the report it is showing a date of 12/30/2011 with a time of 22:30:00 and correspondingly it is excluding 12/31/2011 records. Somehow I think this date/time shift is related to the fact the under Tools-> Options->Compilation and Execution->Report Time Zone I have it set to Central Standard Time which is the time zone that I am in. I am also not sure if my local time settings on my computer can affect the report. ****** Question 1 - What should my Report Time Zone be set to so that this date shift does not occur and it just uses the exact date I enter for the prompt? Question 2 - Currently if I want to make a query against a SQL datetime field I have been using parameter field with a Parameter Class of java.util.date such as shown in the query above - $P{CutoffDate}. The problem is that when the issue I described above occurs, I am not getting the correct records returned. What I really would like is the ability to either always have the time for this date parameter default to 11:59 PM or have the ability to input a time with the parameter prompt. Can this be done with the parameter class of java.util.date or do I need to change my parameter class? As a less desirable alternative, can I modify my SQL query to accomplish this same goal, of course I assuming that the parameter does not shift the date to start with? Sorry if this is a basic question, but I am somewhat confused because I can get the queries to run perfectly when run directly in the SQL Manager and I am just missing something in the iReport / JasperReport settings.

This has been fixed in the latest release. I took the advice and added it to the tracker. Thanks much to all who offered information and suggestions.

I am having an odd issue when using a Date field in iReport 3.7.6. I am accesing a SQL Server 2005 database using a JTDS driver. Whenever I attempt to place a SQL date time field on my report, it is rounding the time down by 30 minutes. For example, in the SQL table I have a field storing an EstimatedComletionDate which is populated as 2011-05-15 00:35:01.000 On iReport the date does not report as recorded in the SQL table. If I set the field type as java.sql.Timestamp it shows - 15/05/2011 12:05 AM If I set the field type as java.sql.Date it shows - 14/05/2011 11:30 PM *********** I am not sure if I am having an issue with some type java conversion or with the jtds driver or something else. Any help would be appreciated. Thanks, JOe

Could someone on Development team please incorporate this fix into a release? It is still an ongoing issue as of version 4.01. Or if there is an alternate solution, please let us know what to do. Thank you.

I finally made the leap from iReport 3.0 to 3.7.x. Now for a completely silly question. Is there any way to get the Properties line back on the right click menu when you select a field, instead of having to select the field and do a Ctrl-Shift-7 or leaving the properties window docked and open? Thanks, Joe

Tony, Thanks again for all your answers, they have been very helpful. I decided to go with the MySql 5.1 to be safe. I also went with Tomcat 6.0 I installed MySql and Tomcat separately before doing the upgrade, so I could install them each in their own directory and run as services on startup. I made some notes as I went along to keep handy for future upgrades. Hopefully they might help others down the road. ******* Jasper Server Upgrade Notes ******* Installer -The Jasper Server .msi installer is 32 bit only. To install on a 64 bit machine you have run it in compatibility mode. Java JDK and JRE- To run the js-ant Buildomatic scripts, you must have the JDK version of Java installed, not just the JRE version. Repository- Exporting the repository is the same as exporting the whole JasperServer database. Repository=JasperServer database. It is exported to a zip file which can then be imported to the new version using js-ant. Java_Home- The Java_Home environmental variable needs to be set to the directory containing the JDK and the JRE, for example c:\Program Files\Java Buildomatic- When configuring the default master properties file for the Buildomatic scripts you have to use a double slash (//) to indicate an actual slash in the path. For example c:\Tomcat6_0 would be entered in the file as c:\\Tomcat6_0 JTDS - If you are using the JTDS JDBC driver it should be installed in one of the following directories: (a) -$TOMCAT/webapps/jasperserver/WEB-INF/lib or (b) -$TOMCAT/common/lib Java Commons Lang - If you are using an updated version of the Java Commons Lang jar on your development machine where you write reports, don't forget to update the jar on the JasperServer computer as well JasperServer Startup - If after loading everything JasperServer will not come up, check the Tomcat Catalina logs for errors, particularly the default Tomcat stop port 8005 being in use. The solution for this is to change the port in the server.xml file to another port such as 8006.

Thanks again. I managed to figure it out after my posts, using some guidance you had left on the forum for someone else trying to do the same thing. I used the js-export script with everything option, copied the file to the new machine and then used the js-ant import upgrade process to get it to the new server. Unfortunately for us non-programmer types, understanding the terminology is sometimes a challenge.

Thanks, that did the trick.

Can you help me understand the difference between the repository and the JasperServer database? Are they the same thing? In reading the documentation, the upgrade path calls for a backup/mysqldump of the whole JasperServer database, but says to export the repository data. I am trying to take the JasperServer 3.0 data from one machine and bring it on to a new machine as version 3.5. Thanks, Joe

Hi All, When I am trying to run the Buildomatic scripts to upgrade Jasperserver to 3.5, the build is failing with a message that the app server root directory cannot be found? I am running Tomcat 6 in the following path C:Tomcat6_0 I have configured my default master properties file as follows: appServerType=tomcat 6 appServerDir=C:Tomcat6_0 dbUsername=root dbPassword=password dbHost=localhost Error occurs when executing setup.xml line 230 - Error app server root directory C:Tomcat6_0 not found. I can positively confirm that the directory indeed exists. Any help appreciated. Joe Post Edited by joepmo at 11/27/2010 22:00

Follow on to this question - would I complicate anything to go to the 5.5.6 version of MySQL?

Hello All, In reading through the documentation for the upgrade from version 3.0 to version 3.5, I am following the steps in Chapter 7 which show how to do the upgrade from the WAR file. However when I go to the chapter on the WAR file buildomatic, the directions seem to imply that the user already had MySQL and Tomcat installed. For reference, when I installed version 3.0 I just used the bundled versions of MySQL and Tomcat. Question 1 When configuring the Buildomatic scripts for the upgrade, do I just point back to installation directory where MySQL and Tomcat were originally installed? Question 2 Do I need to do anything to upgrade the versions of MySQL and Tomcat that were installed when I originally installed Jasper Server version 3.0? Thanks, Joe

I do not believe this is correct or the behavior is erratic. Again I am trying to confirm that using subreport variables to populate main report variables is stil NOT supported, correct? At least when I have tried this I get a "null" return.