tkavanagh

Yes, this is a little confusing. The ctlscript.sh *only* applies to the binary installer (which puts a DB and a tomcat and jasperserver into tomcat automatically on a linux instance). However, for the installation that you did with your existing DB and existing tomcat - using the buildomatic/js-install.sh script you did everything right! Since your DB seems to already be running, all you have to do is startup your Tomcat instance. If tomcat was already included in your linux distribution then the usual startup command might be something like the following: become the root user (or use sudo command) run: sudo /etc/init.d/tomcat6 start *However* there is a bug that I am fixing for the next version of JasperServer. Hopefully you are not hitting this bug. The bug is: when a tomcat6 is included (ie standard RPM package) in linux it is typically broken out into two folder: /usr/share/tomcat6 (will find bin folder and lib folder here) /var/lib/tomcat6 (will find the correct webapps folder here) The buildomatic/js-install.sh script only expects one folder structure. So, there can be an error where the jdbc driver or the jasperserver webapp does not get copied to the right location. So, here is what you can double-check (assuming the apt-get/rpm style of tomcat6 instance): /usr/share/tomcat6/bin (should see the *.sh scripts) /usr/share/tomcat6/lib (the postgresql/mysql jdbc driver should be copied here) (../lib/postgresql-9.0-801.jdbc3.jar) /var/lib/tomcat6/webapps (jaserserver war file folder should go here) So, my bug fix needs to be handling two separate folder for tomcat and allowing jasperserver user to specify two env variables that match these two folders: CATALINA_HOME=/usr/share/tomcat6 CATALINA_BASE=/var/lib/tomcat6[/code] Here is a somewhat related discussion: http://stackoverflow.com/questions/3446803/tomcat-is-installed-with-catalina-home-in-usr-share-tomcat6-and-catalina-base-i

Yes, this seems very odd. Because if you run the: js-export --everthing --output-zip testexport.zip You should see all reports and other resources (but if you poke around in the zip file you should see the reports under the "resources" folder (something like: resources/reports/ and resources/power). So, perhaps there is a problem with the configuration and you are not pointing to the DB that you are expecting? Try looking at: <path>/buildomatic/build_conf/default/js.jdbc.properties In mine looks like this (clipped): $ cat js.jdbc.properties # Property that determines the Hibernate dialect metadata.hibernate.dialect=com.jaspersoft.hibernate.dialect.PostgresqlNoBlobDialect # jasperserver repo db settings metadata.jdbc.driverClassName=org.postgresql.Driver metadata.jdbc.url=jdbc:postgresql://localhost:5432/jasperserver metadata.jdbc.username=postgres metadata.jdbc.password=postgres So, we can see that the DB I'm pointing to is on "localhost" (ie my own developer machine)

I think that this will be a problem because Adhoc really is a pro-only (ie commercial-only) feature. So, CE (community edition) would not be able to open the adhoc facility. So, the CE product would not be able to open the adhoc report. The only exception is scheduled reports generated from the adhoc report (which are saved as pdf, html, etc) would be viewable.

Attaching reboot script and instructions.

Hmm, that's odd that it is not shutting down cleanly (at least getting rid of the pid). Did you get a chance to check and see if there were any unusual ownership or permission problems within the <tomcat>/temp folder? I assume that you are running a flavor of linux. By the way ... I just made an example script that is intended to be used for starting and stopping on system reboot. I also created instructions which are in a readme.txt file. How did you setup your "auto-restart" on reboot? Using /etc/init.d script? I checked in my changes to the most current trunk code: jasperserver/scripts/linux/ readme.txt jasperserver (this is the sample script) I tested under Ubuntu. I didn't finish fully testing under Redhat/CentOS. I'll see if I can attach to this thread for people to look at.

Hmm, unfortunately Auditing is a feature of the Commercial product (and has granular logging on all the different actions and feature areas). However, I am thinking that you could turn on INFO or DEBUG in the WEB-INF/logs/jasperserver.log and then later parse for certain actions within the log. The logging levels can be changed via WEB-INF/log4j.properties. And the trick would be to find the right classes or packages to enable more log output. I wonder if anyone else on the forums has tried this yet ...

Hi Randy, There is actually a JasperForge.org project so support PL/SQL. I don't think there is any actual code required, it is just configuration.

Also, you can put the JDBC driver in the <tomcat>/lib folder if you are seeing a ClassNotFound error for the jdbc driver.

Regarding Java version. As of Release 4.5.0, Java 1.6 or higher is required. Java 1.5 is no longer supported. (Once Oracle/Sun officially released Java 7 and end-of-lifed Java 5 - we switched and did the same. And the first release that dropped 1.5 was 4.5.0). Regarding the "split" tomcat - you have definitely found a bug here. The JasperServer "auto-install" script (buildomatic/js-install.sh) does not handle the split tomcat properly. Because the CATALINA_HOME and CATALINA_BASE are two different folders - the script needs to be updated to expect these two folders. And users who are installing will need to specify both these locations in the buildomatic/default_master.properties file. I will be updating/fixing for the 4.7.0 release. Until then, the work around is to manually copy the JDBC driver the the /usr/share/tomcat6/lib folder. (The JDBC driver can be found here: <js-install>/buildomatic/conf_source/db/postgresql/jdbc)

Also I am taking a look at the attached log ;-) There seem to be two errors getting displayed: 1) java.io.FileNotFoundException: /var/lib/tomcat7/webapps/jasperserver/WEB-INF/logs/jasperserver.log (Permission denied) 2) Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver Let's take the second error first. There can be some confusion about tomcat6 and tomcat7 when installed with via rpm and/or apt-get or if the package is already present in your linux distribution. Unfortunately, there is a bug with the "auto-install" script (buildomatic/js-install.sh) for JasperServer. Tomcat doesn't have the key folders under the same folder structure. Using Ubuntu tomcat6 as an example we see that the webapp "deploy" folder is here: /var/lib/tomcat6/webapps But the folder where the jdbc driver should go is here: /usr/share/tomcat6/lib So, I think you should check to see if you have a folder /usr/share/tomcat7/lib. And if you do, this is where the postgresql jdbc driver should go. (you can copy the postgresql jdbc driver from here: <js-install>/buildomatic/conf_source/db/postgresql/jdbc) For the second problem, I think this might be a general issue with permissions that can happen under linux/unix. Say you install JasperServer as user "tony". And everything runs fine and starts up fine. Then, later, you run JasperServer as user "root". Temp files such as WEB-INF/logs/jasperserver.log will be recreated as user "root". Then, later, you run JasperServer as user "tony" again. On startup, user "tony" will not be able to overwrite the jasperserver.log file because it is owned by "root". Oh Darn! So, you can run these commands as root to set all ownership back to "tony". (will need to be user "root" or "sudo to root" to run these): cd /var/lib/tomcat7 chown -R tony webapps (change ownership to tony) chgrp -R tony webapps (change group to tony) But please check with your Sys Admin before you run such commands. Because I am just guessing at the problem.

There really shouldn't be anything different about installing to Solaris (ie once you have the bash shell in place, which you mentioned that you do). Particularly because you have your already installed tomcat in place and postgresql in place. One thing that can be a problem is how tomcat is installed as a package for some unix/linux distributions. The example I have is under linux ubuntu and installing the tomcat6 package using "apt-get". The tomcat is "broken out" across a couple of locations: /var/lib/tomcat6 /usr/share/tomcat6 The js-install.sh script (which uses ant based scripts behind the scenes - in the buildomatic folder) actually expects the both the <tomcat>/webapps folder (for jasperserver deploy) and the <tomcat>/lib folder (for the jdbc driver) to be in the same parent directory. So, in this case, the workaround is to deploy to /var/lib/tomcat6 and then manually copy the jdbc driver. However, it does not sound like this is the issue in your case (but probably best to check the webapps location and the location of the jdbc driver). In your case the base error seems to be the NoClassDefFoundError. One thing you might try as a workaround to see that you can get up and running is: - check the Java version you are running. Should be Sun/Oracle Java 1.6 (or 1.7) - Don't use the existing tomcat5.5. It looks like there is some kind of bad deploy or mis-configuration of sometype. Try getting a new tomcat and use tomcat 6. I would recommend downloading the tomcat 6 zip file or tar.gz so that you have a little more control on the tomcat so that it will be easier to see what might be wrong. - install the tomcat by unpacking into your home folder (or similar location). Then in your buildomatic/default_master.properties you can point to the tomcat6 path location. - You won't need to run the js-install.sh because you already have your jasperserver database created and populated with data/resources. - you can simply run: ./js-ant deploy-webapp-ce - this will deploy jasperserver into your tomcat 6 (the js-install.sh does this behind the scenes) - The NoClassDefFoundError is the real issue here. If we see this error again then we can drill down and see why this is occuring. - Ie by looking in the <tomcat>/logs/catalina.out and attaching the whole log file to this thread

Is it possible to get the entire log output from the application server (example tomcat)? And better yet would be to delete the logs and let the problem happen and then grab that whole log file. <tomcat>/logs/catalina.out - is usually the best one to grab Also, you can attache <tomcat>/webapps/jasperserver/WEB-INF/logs/jasperserver.log Sometimes there are long java Stack Traces and the cause of the problem can be seen somewhere in the stack trace. Logs can be attached to this forum thread.

Fusion operates by using flash. There are .swf format files generated. So I think the answer is no. There is also jfreechart support which is not flash based. You can take a look at the JasperReports documentation so find out more about jfreechart.

And the next release should be out around early May.

Do you know if the postgresql jdbc driver .jar is included in the correct location for the workbench? It might be pre-configured for mysql ...

The very first one should do the trick: jasperreports-server-cp-4.5.0/apache-tomcat/lib/mysql-connector-java-5.1.10.jar But just to double-check, you should see the postgresql jdbc driver already in that same folder. Can you post the error message when you try and connect? You can find the error message in tomcat: jasperreports-server-cp-4.5.0/apache-tomcat/logs/catalina.out or perhaps jasperreports-server-cp-4.5.0/apache-tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log

I do see the default setting for the tempFolderUri. This found in jasperserver/WEB-INF/applicationContext.xml. And the value is set like this: <property name="tempFolderUri" value="/temp"/> But I don't see a similar one for /reports

The commands that you were running with "js-ant" are "buildomatic" commands. buildomatic needs to have a default_master.properties in place (see the import-export chapter in the Install Guide for more info) - that is where the js-path env variable comes from. But instead of buildomatic you can use the shell script based import and export commands. Try this: cd <js-install>/buildomatic ./js-export.sh --help This should hopefully give you something useful. Then something like: ./js-export.sh --everything --output-zip js-catalog-my-export-files.zip

I know this is kind of clunky but you can do an "export" out of the jasperserver repository (database where all resources are stored). Go to the buildomatic folder. cd <js-install>/buildomatic Try running: js-export.sh --help (or js-export.bat --help) To make it easy to export resources (for the first time), probably you can just do: ./js-export.sh --everything --output-dir js-catalog-my-export This should create a directory: "js-catalog-my-export" Then you can look inside the export xml and .data files to find your jar. You jar will be stored as a .data file. There should be also be an .xml file the same name as your jar. All resources are stored under the "resources" folder

Might be just a syntax error in the web.xml file: Mar 13, 2012 1:24:57 PM org.apache.catalina.startup.ContextConfig applicationWebConfig SEVERE: Parse error in application web.xml file at jndi:/localhost/jasperserver/WEB-INF/web.xml org.xml.sax.SAXParseException: The element type "resource-ref" must be terminated by the matching end-tag "</resource-ref>". at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1269) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561) at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:351) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1041)

Duce, You can take a look at the <unpacked-dir>/docs/JasperReports-Server-Install-Guide.pdf. There is Chapter 5 "Installing from the WAR File Distribution ZIP". There is a script <unpacked-folder>/buildomatic/js-install.sh which will do the install once you have created a properties file with the name buildomatic/default_master.properties. And assumes you have a Tomcat and a PostgreSQL or MySQL instances available. However, the trick is that this script is a bash script, and I don't think that FreeBSD includes the bash shell by default. So, it is required that you install the bash shell and then run the js-install.sh script. *Also* jgh has been maintaining a FreeBSD ported install of JasperReports Server. So, that would probably be way easier!

You should be able to do the same with a Java based Web Services client. There is some sample code to look at. And also there is a JasperReports Server Web Services Guide PDF that you can look at. (Look in the <js-install>/docs folder). The sample code is found here: <js-install>/samples/java-webapp-sample and java-webapp-sample-pro

Yes, you can look in <tomcat>/logs. Or also <tomcat>/webapps/jasperserver/WEB-INF/logs/jasperserver.log But if there is an error at App Server startup then the second log probably won't get created.

Yes, Fedora 9 should work fine. One thing to look out for is an old version of (I think) OpenJDK. If you intend to have Sun/Oracle Java in place then might as well remove any OpenJDK binaries so that there is no possibilty of a conflict. But if you type: java -version and you see the Sun/Oracle version info displayed then you should be fine. I would also set the JAVA_HOME variable. Since you are installing to the Oracle database, then you should use the War File Distribution ZIP release package to handle your installation. Once the zip is unpacked, you can find the script <js-install-unpacked>/buildomatic/js-install.sh You will create a default_master.properties file (from the sample_conf/oracle_master.properties template) which will have your local settings for App Server, DB user, DB pass, etc. Take a look at Chapter 5 "Installing the WAR File Distribution" of the JasperReports Server Install Guide pdf found here <js-install-unpacked>/docs for complete information. For instance, you will want to increase your default JAVA_OPTS setting because JasperServer is a large application and running large reports takes, of course, even more memory. See Section 6.2 for JAVA_OPTS settings. Also, if you want to get JasperServer up and running quickly, you could use the Binary installer which will put everything in place for you to run: tomcat, java, postgresql database. Just take all the defaults suggested by the installer. And when you are done you can uninstall by running the uninstall binary. So, maybe get a test env running first and then your production Oracle version afterward. Regarding Fedora support, we test with the more current versions because this makes sense for "certification". But old versions of Fedora are fine also.

Yes, this sounds like a bug to me. If you can add a bug/tracker item for this that would be great. Also, I am wondering if you see the same issue if you create a new folder and give it read-only permissions for your users, then can users navigate there and view the reports there?