Jump to content

Gaby38

Members
  • Posts

    255
  • 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

Everything posted by Gaby38

  1. Hello Lee, I had a similar issue. I tell you how I fixed it : there are certainly other ways, this is mine : - I use a string parameter between parenthesis for my list of value : e.g "(1,2,3,4)" - in the report query I use the specific parameter expression "$X{}" : for instance in your case suppose that your parameter AA has been initialized with the string "(1,2,3,4)", then in the where clause you put something like that : "where $X{IN,table.value,AA}" if you want the field "value" of "table" to take its values in (1,2,3,4) You can do a search in jasperserver forum on "$X" to get more info about the use of this specific kind of parameter. To use a string instead of a collection allows to transmit it in a URL : it's why I chose this method Hope this will help you Gaby
  2. Hello, I have identified the problem. See the following post on jasperserver forum : jasperforge.org/plugins/espforum/view.php
  3. Shermann, Thanks taking care of my troubles! In order to know the truth, I did on the same server hardware a "fresh install" of jasperserver V3 by using the linux installer. After fixing some problems of cohabitation, I finally got this new installation working. And I tried to access it by using iReport V3 with the JSPlugin V3 and IT WORKED!! So, to resume, I have a first jasperver V3 obtained by upgrading according to the documentation an existing JS V2.1 and a second jasperserver V3 obtained by a fresh install from the downloaded Linux installer. If I create on iReport V3 with JSPlugin V3 a server link to the first JS, it doesn't work. If I create a server link to the second JS it works (I didn't test all features but I can browse the repository). It seems to me that there is something missing in the upgrade procedure from V2 to V3 which affects the Web services interface. I am thinking of some files in the lib(common/lib) directory of tomcat which are provided with the installer but not in the war file. For me I consider that the problem is fixed but don't you think it "smells" like a bug in the upgrade procedure ? Thanks for the time you spent on this problem!
  4. Hello, If you have wireshark installed I think that a capture of the real http dialog during error can help : one can see the exact origin of the "access denied" If wireshark not installed, it's free and not difficult to install. Just a suggestion to help!
  5. Hello everybody! Just to notice that in a previous post : www.jasperforge.org/plugins/espforum/view.php I get exactly the same kind of error in another context : use of iReportV3 with JSPlugin V3 and till now this problem is still pending for me though I did all tries suggested. So I am very interested by the future answers to this post.
  6. Thanks for your answer Shermann! I am surprised because I just had a glance to the jasperserver database, the JIUser table, and inside passwords are not encrypted. Is it normal or the migration sql script did not work or did I miss something? I tried to delete all serv er entries and to recreate : always the same error. I am going to investigate further on this way
  7. OK, I didn't catch what you exactly wanted to do. Of course, my "solution" in the query looks like yours in parameters, but I am more trained with SQL than with Java!! If I well understand, you want to use the same report and , according the "schedule type" (daily, monthly,weekly,..) calculate the right dates to be used as filtering. You must so have the capability to check the "periodicity" of your report. This periodicity is stored somewhere in one (or more) table(s) of the jasperserver database, which can be accessed through query and reports. So, for me, a possible way is to have a sub report , to which you give as parameters the right dates, and this subreport is inserted in a main report the query of which is searching in the jasperserver database the periodicity frequency (I think it can be discovered by parsing the "right" tables) and calculates the date parameters to be used by the subreport. You have to check if jasperserver allows to manage different datasources for main report and included subreports. I know! It's more easy to write on the forum than to realize!! I already used such a method in a kind of "dispatching" report which reads in the jasperserver database the "role" of the logged user and enables (or disables) a lot of hyperlinks to other reports. For your last question, it is possible to send by mail a scheduled report to a list of e-mail addresses separated by a comma
  8. hello, I got also the same message, but I think it's only a warning the first time you launch iReport after installation with reset of the default directory where iReport stores its files : (UserDesktop/.ireport in windows). As for me, it doesn't forbid me to work with iReport. As soon as you begin to edit some reports with iReport, this error shoudn't appear any more.
  9. hello, I had a similar problem : to send a daily mail to a list of people which was an extract for the day of operations registered in a diary table in the database. For that, I choosed to do that in the query, that is I don't use parameters from jasperserver but the date returned by the database : in my case (oracle) I have a where clause like that: "where Dat_Creation_Jou =(select to_number(to_char(sysdate,'YYYYMMDD')) from dual)" (In the database the date is a number "YYYYMMDD") It works fine It seemed to me to be the easyest way to solve this kind of problematic. Hope this will help you
  10. Hello, I post my problem on this forum after having posted it on Jasperserver forum. Already, with jasperserver V2.1, I tries tu use ireport V3 and JS PLugin V3. It didn't work and to get it worrking I was obliged to overide jspluginV3 .jar by the V2 one in the lib directory of iReport. This was not shocking for me as I worked with a Jasperserver V2. I migrated from JS V2 to JS V3 and I wanted to use the JS plugin V3 : I got the same error than previouly with the JS V2. Tony on JS forum said me that he tested from a fresh install and it worked. On the same forum two other guys got the same kind of trouble with KS plugin V3. To go further, I did wireshark captures of http traffic. Here after I paste the beginning of the content because I was not able to use the attachment fucntion of this new forum. I quote the first part of th TCP stream. It's enough to see the difference. For V3 plugin : POST /jasperserver/services/repository HTTP/1.1Content-Type: text/xml; charset=utf-8 SOAPAction: ""User-Agent: Axis/1.4Host: mairie:8080Transfer-Encoding: chunked00 HTTP/1.1 401 Full authentication is required to access this resourceServer: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B49650; Path=/jasperserverWWW-Authenticate: Basic realm="Protected Area"Content-Type: text/html;charset=utf-8 Content-Length: 1130Date: Fri, 25 Jul 2008 17:41:34 GMT <html><head><title>Apache Tomcat/6.0.16 - Rapport d'erreur</title><style> <!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>Etat HTTP 401 - Full authentication is required to access this resource</h1><HR size="1" noshade="noshade"><p><b>type</b> Rapport d'..tat</p><p><b>message</b> <u> Full authentication is required to access this resource</u></p><p> <b>description</b> <u>La requ..te n..cessite une authentification HTTP (Full authentication is required to access this resource).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.16</h3></body></html>POST /jasperserver/services/repository HTTP/1.1Content-Type: text/xml; charset=utf-8SOAPAction: ""User-Agent: Axis/1.4Transfer-Encoding: chunkedAuthorization: Basic amFzcGVyYWRtaW46cmFtYm8yHost: mairie:8080Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B4965000 HTTP/1.1 501 Le m.thode 0 POST n'est pas d.finie dans la RFC 2068 et n'est pas support.e par l'API ServletServer: Apache-Coyote/1.1Content-Type: text/html;charset=utf-8 For V2 plugin : POST /jasperserver/services/repository HTTP/1.0Content-Type: text/xml; charset=utf-8Accept: application/soap+xml, application/dime, multipart/related, text/*User-Agent: Axis/1.4Host: mairie:8080Cache-Control: no-cachePragma: no-cacheSOAPAction: ""Content-Length: 815Authorization: Basic amFzcGVyYWRtaW46cmFtYm8y<?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:list soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://axis2.ws.jasperserver.jaspersoft.com"><requestXmlString xsi:type="xsd:string"><?xml version="1.0" encoding="UTF-8"?> <request operationName="list" locale="fr"> .<resourceDescriptor name="" wsType="folder" uriString="/" isNew="false"> ..<label><![CDATA[null]]></label> .</resourceDescriptor> </request> </requestXmlString></ns1:list></soapenv:Body></soapenv:Envelope>HTTP/1.1 200 OKServer: Apache-Coyote/1.1Content-Type: text/xml;charset=utf-8Date: Fri, 25 Jul 2008 17:55:47 GMTConnection: close<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:listResponset You can see that the authentication behaviour is not the same in the 2 cases (between the 2, only changed the V2 .jar of the plugin by the V3 one). In V2 the first http dialog sends the basic authentication string. In V3 it seems to do the authentication in two steps. Is it normal or a bad work due to my context? Thanks for your help
  11. Hello, I give you MY method. It is not perhaps the better one but it works. In the properties of the field I want to use to drill-down, in the "hypertext link" tab, I select "Reference" as link type and I put : "/jasperserver/flow.html?_flowId=viewReportFlow&reportUnit=/reports/Concerto/Test1&Param1=val1 &Param2=val2&....." "Test1" is the name of the report in the repository and "/reports/Concerto" is the "Uri" path. Of course "val1" etc... may be in relation with the field itself or other parameters. Till now, this works. Perhaps with the V3 there is another way morre efficient? I don't know. Hope this will help you.
  12. No luck, or I don't know how to use the attachment fucntion of this new forum. I quote the first part of th TCP stream. It's enough to see the difference. For V3 plugin : POST /jasperserver/services/repository HTTP/1.1Content-Type: text/xml; charset=utf-8 SOAPAction: ""User-Agent: Axis/1.4Host: mairie:8080Transfer-Encoding: chunked00 HTTP/1.1 401 Full authentication is required to access this resourceServer: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B49650; Path=/jasperserverWWW-Authenticate: Basic realm="Protected Area"Content-Type: text/html;charset=utf-8 Content-Length: 1130Date: Fri, 25 Jul 2008 17:41:34 GMT <html><head><title>Apache Tomcat/6.0.16 - Rapport d'erreur</title><style> <!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>Etat HTTP 401 - Full authentication is required to access this resource</h1><HR size="1" noshade="noshade"><p><b>type</b> Rapport d'..tat</p><p><b>message</b> <u> Full authentication is required to access this resource</u></p><p> <b>description</b> <u>La requ..te n..cessite une authentification HTTP (Full authentication is required to access this resource).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.16</h3></body></html>POST /jasperserver/services/repository HTTP/1.1Content-Type: text/xml; charset=utf-8SOAPAction: ""User-Agent: Axis/1.4Transfer-Encoding: chunkedAuthorization: Basic amFzcGVyYWRtaW46cmFtYm8yHost: mairie:8080Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B4965000 HTTP/1.1 501 Le m.thode 0 POST n'est pas d.finie dans la RFC 2068 et n'est pas support.e par l'API ServletServer: Apache-Coyote/1.1Content-Type: text/html;charset=utf-8 For V2 plugin : POST /jasperserver/services/repository HTTP/1.0Content-Type: text/xml; charset=utf-8Accept: application/soap+xml, application/dime, multipart/related, text/*User-Agent: Axis/1.4Host: mairie:8080Cache-Control: no-cachePragma: no-cacheSOAPAction: ""Content-Length: 815Authorization: Basic amFzcGVyYWRtaW46cmFtYm8y<?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:list soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://axis2.ws.jasperserver.jaspersoft.com"><requestXmlString xsi:type="xsd:string"><?xml version="1.0" encoding="UTF-8"?> <request operationName="list" locale="fr"> .<resourceDescriptor name="" wsType="folder" uriString="/" isNew="false"> ..<label><![CDATA[null]]></label> .</resourceDescriptor> </request> </requestXmlString></ns1:list></soapenv:Body></soapenv:Envelope>HTTP/1.1 200 OKServer: Apache-Coyote/1.1Content-Type: text/xml;charset=utf-8Date: Fri, 25 Jul 2008 17:55:47 GMTConnection: close<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:listResponse
  13. The attachment function of the new forum didn't work. I Retry
  14. Here after the first attachment is a wireshark capture of the first tcp stream, when iReport authenticates to jasperserver. It's with plugin V3 which doesn't work. Then a secon attachment : a wireshark capture of the first http stream with the plugin V2, which works. Between the two, only the V3 ireport jar has been replaced by the V2 ireport jar. You can see that the behaviour of the plugin for authentication is not the same (that is perhaps normal). And in the first case, Tomcat server doesn't appreciate. Can you help me to fix this problem, without spending a lot of your time of course? Thanks a lot!
  15. Hello, I up this post because the last answer of Tony doesn't satisfy me.I tried again to have the Plugin 3.0 to work with my upgraded jasperserver and I didn't succeed. I uninstalled all previous releases of iReport. I installed the 3.0 iReport as it comes with the 3.0 plugin. I always get the same error. If I override in the iReport lib directory the "jasperserver-ireport-plugin-3.0.0.jar" by the previous "jasperserver-ireport-plugin-2.1.0.jar", nothing else, it works! If I connect from mozilla to "http://mairie:8080/jasperserver/services/repository?wsdl", I get the xml attached to this post. What do you suggest I should do for trying to go further in this problem? Thanks
  16. Hello, a suggestion : have a glance to the MaxWait parameter in the JNDI connection to your mysql database.
  17. I don't think that it comes from the fact you pacakged the plugin with jasperserver. In fact i never used the plugin loaded with jasperserver as it was included in ireport delivery. I think that it comes from the fact that I upgraded from 2.1 and didn't start from a fresh install of 3.0.
  18. It's not dramatic just unpleasant. If, instead of logging off, I click on "Home", it also works!
  19. Hello, I recently migrated to JS 3.0. With 2.1, I often got after long inactivity the error "cannot deactivate transaction". With 3.0, after 4/6 hours of inactivity from jasperserver point of view, I systematically get the repository tree display looping as if the web page was loading. If I logout and re-login, it's OK. Am I the one to get this kind of odd thing??
  20. Hello, Just to say that I already have a report like the one of Robert which runs a query on the meta database and I filter with the name of the user. I did exactly as Lucian said, that is : - create a 2nd parameter "$P{FullUserName}" initialized by defaut with "$P{LoggedInUser}.getFullName()" - and in my query I have : "where jasperserver.JIUser.fullname=$P{FullUserName}" and it works fine.
  21. Hello, Just to say that I already have a report like the one of Robert which runs a query on the meta database and I filter with the name of the user. I did exactly as Lucian said, that is : - create a 2nd parameter "$P{FullUserName}" initialized by defaut with "$P{LoggedInUser}.getFullName()" - and in my query I have : "where jasperserver.JIUser.fullname=$P{FullUserName}" and it works fine.
  22. I am using the same URL than for the 2.1 plugin, that is: "http://server:8080/jasperserver/services/repository" If I paste this URL in Mozilla I get a web page with: "Hi there, this is an AXIS service! Perhaps there will be a form for invoking the service here..."
  23. Hello, I migrated a few days ago from JS 2.1 to 3.0 without problem. I was already using iReport 3.0 but with JS plugin 2.1 because I got an error with JS plugin 3.0. But that seemed to me not abnormal because I was working with jasperserver 2.1. So after the migration I installed the plugin 3.0 and I got the same error that is (in an error window ): Code:"error: ;nested exception is : org.xml.sax.SAXException : bad envelope tag: html I uninstalled/re-installed iReport 3.0 with the 3.0 plugin and I always get the same error. With the 2.1 plugin, it works fine, even with jasperserver 3.0. Any idea?
  24. Hello, This afternoon I just migrated from 2.1 to 3.0. I have an environment very similar to yours. I followed step by step the install guide. I got my new install perfectly working and my previous analysis views were also working. In your post, I didn't see that you ran the update scripts on the mysql database. Did you forget to say that you did or did you forget to do it really? It could perhaps explain your problem.
  25. Hello Matt, As for me, the 1st time I wanted to use iReport 3.0 with jasperserver 2.1, just after downloading it and installing, I got a "strange" error (...nested exception from sax....) while trying to access to the jasperserver "tree" ( without doing anything I got back all ireport 2.0 configuration) through the plugin. But I noticed that I had the 3.0 jasperserver plugin. So, in iReport 3.0, I replaced the 2 jar files of the 3.0 jasperserver plugin by the 2.1 ones. After that, all was running OK and I could access and modify report units through iReport 3.0. Since that test, I didn't create new reports units and try to run them under jasperserver. This is my next step. Hope it will work !!
×
×
  • Create New...