suedonne123

I just installed 3.7 version and used Oracle instead of mySQL as the jasper repository... Follow the installation guide for stand-alone WAR installation...in other words, do NOT download the installers... The installation guide also contains information on using ddl files/scripts to create jasperserver schema in oracle... Best thing to do would be to review the entire install guide and figure out what pieces you will need...depending on 1) backend database used for repository 2) app server that you are deploying (if different than Tomcat)

UPDATE: I was able to export from 3.0.2 and import to 3.7 version... The biggest problem I ran into was setting up my datasource as JNDI entry... For some reason Glassfish/JNDI kept some entry with the name I was attempting to create and so I could never "bind" to it...after a few hours of pulling my hair out...I punted and just renamed the darn thing and waaalahhh! all is working... NOTE: I had a hunch that the export/import would NOT be a problem since the reports that I currently have are extremely simple...SQL and maybe a chart here or there... Post Edited by suedonne123 at 01/15/2010 02:38

In my current JasperServer-pro 3.0.2 instance installed on GlassfishV2.1 app server...I have jdbc/wcsReports JDBC Resource configured and then I changed (JASPER)/WEB-INF/web.xml and sun-web.xml to add JNDI reference to this resource...Then my reports all reference the JNDI reference. Connection pooling is done by Glassfish and the connection settings can be easily changed via the Glassfish admin console... I am working on installing the JasperServer-Pro3.7 instance and the above scenario does not work...I tried adding resource-ref entries in WEB-INF/ web.xml and sun-web.xml but still is not working... anyone else encounter problem with this...????

JasperServer 3.7 buildomatic scripts assume that you are installed JasperServer onto the default "domain1" instance using the admin port 4848... To install jasperserver somewhere else, the following steps were needed: 1) stop all other domains except the one where you want jasper installed... this should cause failure of the js-ant build if it attempts to put js somewhere that you did not intend...(like domain1 for me...) 2) edit GLASSFISH/config/asadminenv.conf and add the following AS_ADMIN_PORT=37048 AS_ADMIN_USER=admin AS_ADMIN_PASSWORD=adminadmin So that asadmin will run against 37048 without asking for user/password test that this is working ./asadmin list-jndi-entries should give you some output... 3) edit jasperserver-3.7-bin/buildomatic files: setup.xml install.xml change all occurrences of "domain1" to "your_domain" 4) now you can use the js-ant deploy-webapp-pro target... Note: this took about 15 minutes to copy all files out...

I would like to clarify something... Installation Guide has section that says to upgrade 3.0.2 to 3.7, I would first need to upgrade to 3.5, then to 3.7... My question is this: Rather than "upgrading" the database, can I simply start with a "new"/fresh 3.7 database instance and the export from 3.0.2 and import to 3.7 ???? Will the import work?

I was able to do this for liferay running under Glassfish app server but I had to add "instanceable" tag to the liferay-portlet.xml file for each...See code below... Code: Post Edited by suedonne123 at 01/01/2010 18:15

What app server are you deploying on...Tomcat, Glassfish, JBoss??? I am using Glassfish and had to update the web.xml and sun-web.xml files within the JasperServer-pro.war file that is deployed...I had to add resource ref entries so that Jasper could find the JNDI entries web.xml: I added <resource-ref> <description>WCS database</description> <res-ref-name>jdbc/wcsReports</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> sun-web.xml: I added <resource-ref> <res-ref-name>jdbc/wcsReports</res-ref-name> <jndi-name>jdbc/wcsReports</jndi-name> </resource-ref>

Obviously, my memory is not so good...I took a look at report that I have: Always prompt is OFF There is a single input control: Mandatory is OFF input control also has a default so when I run the report with no params on the URL, it will display the report with the default value when I run the report with the &paramName=something on the URL, it will display the report with the value "something" The report will show the little "clicky" button to return to the parm input popup... Also, I am using the popup input controls window NOT the top of Page controls... Hope this helps... You will have to make sure all input controls are set similarly if you have multiple controls...

I think what you want to do is set "Always prompt" to No, then set 1 or more of the individual parameters in the jrxml to Mandatory...that way, when URL has the param already set, it will pass right through...otherwise, it should prompt..At least, that is what I remember...

jasperserver uses log4j ... google this up to find a little bit about it... WEB-INF/log4j.properties edit this file and find the axis2.ManagementServer entry...it is probably commented out "#" at beginning is comment... so uncomment, set Log Level to "DEBUG", then restart tomcat or redeploy jasperserver.... This 404 Not found error is bugging me since I remember getting it but obviously cannot remember what solution was... Do you have PORTLET_ROLE or ROLE_PORTLET defined in jasperserver...I think the portlet code does auto-login with this role or some such...I did muck things up at one point by not having this role in jasperserver... Sorry, I do not seem to be giving much help here... :(

Can you hit the jasper web service directly from your web browser...see url below this is the setting that you have in your portlet.xml file...Be careful about the jasperserver-pro part (this is for professional verion ONLY...if community edition, use whatever it is there "jasperserver ???" http://yourMachineHere:8080/jasperserver-pro/services/repository This should ask for login (use jasperadmin login or some such that has permission) You should see: ------------------------------------------------------------ repository Hi there, this is an AXIS service! Perhaps there will be a form for invoking the service here... ----------------------------------------------------------- Then you know that your jasper web services are running...you could also turn on debugging on the jasper side... edit the WEB-INF/log4j.properties (this might be in WEB-INF/classes...???) and set DEBUG for axis things and whatever... you should see web service attempts in the jasperserver.log file then... Remember to turn this off though since it really makes the web services run slow...This bit me last month...

Okay...here is link to issue I logged with all problems I had to fix to deploy under Glassfish App Server... http://jasperforge.org/projects/jasperserver/tracker/view.php?id=4304 your issues may or may not be the same (I am assuming that you are deploying on Apache Tomcat)... Apache Tomcat is the web app that is in Sun's Glassfish product so the issues may be same or similar I had to make a few changes for successful deployment of portlet war on Liferay running on Glassfish v2.1 * servlet.jar removed * commons-logging added * updated portal.xml file (xml was in bad format) * edit jsp files so that <script> is <script type="text/javascript"> I am just guessing that the jsp files may be causing your problem... REGARDING LOG files... Regarding where your log files are...it has been a long time since I have worked with Tomcat...so google this to find out where log files are...individual web applications that are deployed on tomcat should have stuff in <TomcatInstall>/webapps/<portlet-war>/logs or perhaps in WEB-INF/logs ??? For glassfish, look in <Glassfish>/domains/domain1/logs/server.log hope this is helpful...

YES...sorry I was not clear...but the portlet.xml file that is in the jasper-portlet.war from JasperSoft...

JasperServer portlet should display "Jasper Reports" in the add application menu... It probably failed to deploy...check the log files for your application/web server... I had to edit portlet.xml file within the jasper-portlet war file since this did not pass xml validation phase of deployment...Of course I am using glassfish application server instead of tomcat but depending on your version, I think you will get same error... See the following topic for details: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=67454

nope...no other changes should be needed... the intent of the custom jsp is really to customize the default jasper viewer jsp...which I did at our company to eliminate some of the menus/paging etc... but I realized that this could also be used to expose any jsp as if it was a jasper report...

Just an idea... Create your feedback form using straight jsp code...Put this jsp into <jasperserver>/WEB-INF/jsp. Then, configure to serve this up as a JasperServer report , by creating a new report... you will have to use jrxml file since this is required even though you will not be doing anything with it...Then at the Customization screen "Custom Report View", you can put your own .jsp file... I have tested this and this works under JasperServer 3.0.2 See original idea at: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=66014

I am running this portal on Liferay deployed on Glassfish and had the same error due to bad xml...The ordering of the xml tags is incorrect and fails XML validation... in the portlet.xml file... Use the xsd/schema to determine correct xml format or you can look at my piece of xml... NOTE: My code below has changed the names and such which you probably do not want...so just look and copy the ordering of the xml tags... <portlet> <!-- remove this comment for default report to show <portlet-preferences> <preference> <name>full_resource_path</name> <value>/reports/samples/EmployeeAccounts</value> <modifiable>1</modifiable> </preference> <preference> <name>resource_type</name> <value>report</value> <modifiable>1</modifiable> </preference> <preference> <name>number_of_parameters</name> <value>1</value> <modifiable>1</modifiable> </preference> <preference> <name>js_resource_parameter_EmployeeID</name> <value>beth_id</value> <modifiable>1</modifiable> </preference> </portlet-preferences> --> <description>JasperSoft Corporation</description> <portlet-name>WCSPortal</portlet-name> <portlet-class>org.springframework.web.portlet.DispatcherPortlet</portlet-class> <init-param> <name>jasperserver_repository_ws_url</name> <value>http://localhost:8080/jasperserver-pro/services/repository</value> </init-param> <init-param> <name>portal_server</name> <value>liferay</value> </init-param> <init-param> <name>show_logo</name> <value>false</value> </init-param> <init-param> <name>show_return_to_report_list_icon</name> <value>false</value> </init-param> <init-param> <name>show_return_to_parameter_icon</name> <value>true</value> </init-param> <init-param> <name>company_logo</name> <value>jaspersoft-logo.png</value> </init-param> <init-param> <name>company_logo_hyper_link</name> <value>http://www.jaspersoft.com</value> </init-param> <init-param> <name>report_directory</name> <value>/Reports</value> </init-param> <init-param> <name>number_of_reports_per_page</name> <value>15</value> </init-param> <expiration-cache>0</expiration-cache> <supports> <mime-type>text/html</mime-type> <portlet-mode>view</portlet-mode> <portlet-mode>edit</portlet-mode> <portlet-mode>help</portlet-mode> </supports> <supported-locale>en</supported-locale> <resource-bundle>com.jaspersoft.jasperserver.portlet.PortletResourceBundle</resource-bundle> <portlet-info> <title>WCSPortal</title> <short-title>WCSPortal</short-title> <keywords>JasperPortlet, JasperServer, JasperReport, JasperSoft, WCSPortal</keywords> </portlet-info> <supported-publishing-event xmlns:x="http://fortna.com"> <qname>x:wcsportal</qname> </supported-publishing-event> </portlet>

I believe you will find <session-timeout> value in <jasperserver>/WEB-INF/web.xml... Default web session timeout is 20 minutes...Setting this to 0 should never timeout...

Make sure you do not have debugging level logs turned on for JasperServer...This one bit me last week...I could not figure out why my web service calls were taking so long to return the report structures, etc...I had turned on debug level in the log4j.properties file to debug something else and forgot to set it back...duh... :('

Sorry for butting into your posting but I think this is somewhat related... I would like to output plain old HTML tables (without all the embedded images, etc for pixel perfect print that the JRHtmlExporter outputs...) I really just sometimes want to output the result set to a plain html table and then use javascript or some such to have clickable columns for sorting...I have tried to modify JRHtmlExporter and make sense of the JRPrint object...without much success (I get close but still get offsets in the results that are unexpected) Is there a way to get just the results of the report/query INSTEAD of getting a JRPrint object?

Possible solution: (this is just an idea...I have not tried it...) A wrapper jsp that would use the jasperserver HTTP api and simply just keep looping through each individual report with a next button to go to next view with new input parameters...of course how to expose this jsp would be an issue... Here is an idea for exposing this wrapper as a jasperserver report (I just quick tested and this should work!!! Now I just need to find somewhere where this could be useful...) I am wondering if you could "fool" jasperserver into serving up this jsp by doing the following...create jasperserver report (which always requires the jrxml, this jrxml would not be used...) Then edit the report and click "Customization" on left hand menu... enter your new wrapper jsp...

I have done some kludgey things in the where clause like having a parameter that is a pull down list of option values... then use these options in your where clause... WHERE ($P{paramOption} = 1 AND database_column=1 ...) OR ($P{paramOption} = 2 AND database_column=2 ...) etc not the best SQL ever...but gets the job done... I think I have also used Case statements with stuff like that too...

Dashboard creation also does not working in Firefox (3.5.5) but does work in Internet Explorer (7.x)...I was poking around trying to figure out why "Create Dashboard" was not working...it has been a while since I have done any report development... Thank goodness that I read this forum posting or I would have been poking around trying to find the problem and wasting my time! I will log case with JasperSoft as I have professional version...

Just include the following request params on the url... &j_username=<YOUR_LOGIN>&j_password=<YOUR_PASSWORD> This would be visible then on the URL...which is usually not desirable... I resolved this by using hidden input fields to post out to this url...

Edit expression and use java syntax... ( $F{bottomNumber} == 0 ? 0 : $F{topNumber} / ${bottomNumber} ) or some such...