Gaby38

The post I was referencing is : http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=45792 In fact, I "clone" the viewReportFlow and I set the report to be launched at the beginning. In the jasperserver 4 release, it is the same basic principle but there are some changes in the files to be cloned and the way to do that. Swood said that my method was "cumbersome". It is probably true, but it works fine since one or two years. I think there are other ways to do the same thing in a more clever manner but I am not a guru of spring. Gaby

I already did that by modifying the jasper-servlet.xml file. The launched report is a report listing the /reports tree and showing to the user only the reports he is authorized to launch. I already posted about that somewhere in this forum one or two years ago.

I confirm what "blackgoose" said : - the first system on which jasperserver was not working with postgres included a 9.0 postgres release. - the second system on which jasperserver was working with postgres included a 8.6 postgres release. As suggested, I added "bytea_output = escape" in the postgres.conf of the first system, restarted postgres and jasperserver and all worked fine. Thanks to "blackgoose" for this information.

Thanks for your answer Matt !! I decided to re instal on another system and effectively it worked !! I don't know why on the previous system it didn't work in the right manner. Perhaps is it due to the fact that , on this previous system, I first installed jasperserver with the installer(including Tomcat) on a Mysql metadatabase and after I removed the jasperserver and work directories in Tomcat and I reinstalled from war file but with a postgres metadatabase. I tried twice with or without the samples and it was the same thing. Now it's working on the new system : perhaps I'll try to understand why it doesn't work on the previous. A lot of thanks !! Gaby

The Mysql metadatabase was an upgrade from JS 3.7. For the postgres metadatabase, it was a fresh install "from war file" with autoinstall scripts on a system with an installed tomcat and postgres database. Did you test and get a jasperserver 4 running through standard installation scripts for a postgres metadatabase. I precise that from tomcat point of view all is correct. No errors : the html page contents are all present but the display is crazy. It seems like that css files are not taken into account. Thanks for the time you spend on my problem. Edit : in fact I looked at the content of the databases : in Mysql or in postgresql, the data are all in binary. But when I want to get them from the hyperlink inside the html of the login welcome page, for Mysql it is converted to string but for postgres it remains in binary. Is there a parameter to change in the xml files for postgres??? Post Edited by Gaby38 at 04/19/2011 20:33

Hello, I was asked to install a jasperserver 4.0 with a postgres metadatabase. Ok : I saw that it was supported in the install guide and I followed the instructions. When I tried to first login, I got a "page" with no errors but which obviously had no "presentation". All the items were verlapping each other and nothing in relation with the "standard presentation of the welcome login page. I supposed it was due to the "themes" which were "misunderstood" and I had a glance to the source code of the html welcome page. At the beginning of this page, there are some hyperlinks to the css pages. If I click on a link in the source of the welcome page got from a Mysql metadatabase ( for instance /jasperserver/themes/themes.css) I get a classical css sheet with " /* theme.css intended scope: - global page styles - styles for the decorator - utility styles - typography - colors pods skin tim sheiner & christie rixford......................" If I do the same thing on the same hyperlink of the same page got from a postgres metadatabase I get : "F2a0d0a7468656d652e6373730d0a0d0a696e74656e6465642073636f7......................................" So I think there is a problem with the storage format of css sheets in a postgres database. Has anybody else got the same troubles with postgres ?? Thanks for yur help

I succeeded to run insert query in a Jasperreport by running this insert query inside a stored procedure/function. For instance you define a stored function which runs your insert query and after returns a value (no matters : logicaj, integer,...) and you can get this value in a field even if you don't care but jasper is happy and won't give an error. It was just a test and I never used that in production. (In fact, I wanted to update dynamically the list of recipients for a scheduled job by inserting their id in the right jasperdatabase table. But perhaps is it a little crazy ..!!) PS: just a precision my test was running under jasperserver and I didnot use a commit statement : but the inserted values were present inside the table. Post Edited by Gaby38 at 03/08/2011 19:36

I prefer do the test in the query, because I am more familiar with sql than java. select case when employee_sex = 'F' then 'Female' else 'Male' end as Sexe,....... but it is a "classical" test in java: ($F{employee_sex}.equals("F"))?$V{Sexe}="Female":$V{Sexe}="Male" (I am not sure about the exact syntax)

AS for me, I shoud try to get that in the sql query : if you search the net with "SQL last day of week" you will get a lot of solutions. Perhaps try also the same search with "java last day of week"

The way I choosed to implement that is a little complex. In fact, I use the repository tree as an organization tree starting from "/reports" and having : - level 1 directory : "Department" or equivalent - one mandatory level directory under this level1 with an id_name "Queries" (because I have other "themes" as scheduled jobs,..) - level2 directory: "Service" or equivalent - level3 directory : "Chapter" or equivalent All Reports are in the level3 directory Each user that can log in has "user rights" towards these 3 levels that allow him to "see" or not these levels and then the reports. To "see" level1 directory (= in the report acting as home page) user must have READONLY jasperserver right (real not inherited). To "see" level2 directory (= in the report acting as home page) user must have READ+DELETE jasperserver right. To "see" level3 directory (= in the report acting as home page) user must have READ+WRITE+DELETE jasperserver right. The first report acting as home page lists the level2 directory names that user can see grouped by level1 name. By clicking on level2 name (hyperlink), an other report is launched, that is the real report listing the reports the user can launch(hyperlink). In my implementation all reports of level3 directory are visible. One can change the strategy towards the hierarchical visibility of reports : it is linked to the query reading the report list prom the jasperserver database. In the following queries, the FullUserName parameter is obtained from jasperserver Code: firts query listing level 1 and 2 Code: for the query listing the reports Post Edited by Gaby38 at 02/23/2011 22:07 Post Edited by Gaby38 at 02/23/2011 22:10

I did what you want to do, in the same way you describe it. I created a report that is a "welcome report" listing all the reports that a user ca.n see. I define the allowed reports according to the "folder rights" set by jasperserver to the login user for these reports (Read-Only, write+delete,..) in redefining the rights coding as I want to use them. To "launch" that, I have modified in jasper-servlet.xml, the home page set for the "ROLE_USER" by "launching" the "welcome report" I previously spoke about. (you have to "clone" viewReportFlow.xml and modify it by forcing the path to your welcome report). You can complicate by mapping different "welcome reports" according to the "ROLE" assigned to the login. Post Edited by Gaby38 at 02/20/2011 22:28

About my performance problem, it seems that this morning all went back right : performances are "normal". I "rebooted" a switch in my home network and I think that it was involved in the lack of performances. So I apologize for the trouble and I am going on playing with the new release

Hello, I upgraded his evening a 3.7.1 existing jasperserver with the new release 4.0. The upgrade script (upgrading the war) worked perfectly Sorry to say that, but I am disappointed by the performances. The new release seems to run twice or three times slower than the 3.7.1 release. In my case, it is on the same server with the same reports accessing the same databases. I just upgraded the .war. Is the new release needing more hardware resources?? Am I the one to have such a feeling ??

In fact you cannot write : where tab.col = '$P{LoggedInUser}.getFullName()' You have to define another parameter $P{FullName} initialized through its default value to $P{LoggedInUser}.getFullName()' and use it in where clause

I think there is a good explanation of "loggedinuser properties" in the tutorial about cascading input controls. It seems to me that you can get not only the fullname but other properties like the user id. If you have the user id, you can get all other fields in the JIUser table in the metadatabase jasperserver