gdmoreno

ok, it's good that you're familiar with the iReport tool. When you open up the JRXML file in the Designer Mode, you should "Designer", "XML", and "Preview" - click on the button that's right next to the "Preview" button, it looks like a cylinder with an arrow coming out of it. When you click on that button, do you see a query? If you do, I'm thinking you could add a WHERE clause to exclude the companies you don't want to see.

Do you know if those reports were developed using iReport? If so, then what you can do is connect to the server using iReport (using the repository navigator), browse to the report's location in the repository, and then open it up using iReport. Then, you can modify the query that the report is using, and you can add the necessary filter to the query itself. Once you're satisfied with the report data, you can upload the report back to the server.

I think you have some possibilities here. Here's one way, it has a lot of steps. The first thing to do is to back up your current Postgres repository, which you will then import later to another MySQL database. - Make sure you've shutdown your Tomcat server - Go to the buildomatic directory and do this from the command line: ./js-export.sh --everything --output-zip postgresbackup.zip That zip file will contain everything (organizations, users, reports, schedules, etc) that JRS needs to run. Once you have the MySQL database ready to go, you'll use another script to import it to your new database. I'm assuming that you don't want to redeploy your JRS web application, and that all you want to do is migrate over to a different database. - Next, in the buildomatic directory, modify the default_master.properties file This file will contain information about what database you're using. The easiest thing to do is to copy the mysql_master.properties file in the sample_conf directory, copy it to the buildomatic directory, and rename it default_master.properties, to replace the other file. Next edit that file, and put the specific details about your MySQL database in there. - Next, run the buildomatic scripts to create the MySQL repository These steps are the ones that you find in the installation guide. You only need to run those steps that deal with the database, so that means all of them except the last one that actually deploys the web application ./js-ant create-js-db ./js-ant create-sugarcrm-db ./js-ant create-foodmart-db ./js-ant load-sugarcrm-db ./js-ant load-foodmart-db ./js-ant update-foodmart-db ./js-ant init-js-db-pro ./js-ant import-minimal-pro ./js-ant import-sample-data-pro Only the commands in bold are absolutely necessary; the others load sample databases and reports. It's up to you whether you want them or not. - Next, run the import script to populate your MySQL database From the same buildomatic directory, do this from the command line: ./js-import.sh --input-zip postgresbackup.zip The script now uses your modified default_master.properties file, and imports the backup file to - Next, modify your context.xml file Your context.xml file, which is under [TOMCAT_HOME]/webapps/jasperserver/META-INF, will contain JNDI entries that point to the old Postgres database. You'll need to modify the entries there with the right JDBC URL's, and the right username/password. Also, make sure to delete the [TOMCAT_HOME]/conf/Catalina/localhost/jasperserver.xml file (if it's there), because Tomcat will check for the existence of this file before reading in the context.xml file you just modified. - Start up your Tomcat server - Log in (Hopefully this works) - Modify JDBC datasources where necessary If you used the Postgres database as a datasource as well as a repository, you'll need to modify JDBC datasources and modify them so that they point to your MySQL databases. As you can see, it's a lot of manual steps, with potential room for mistakes

1. Hi, my servlet class definition looks slightly different, try this and see what you get: <servlet> <servlet-name>Axis2Servlet</servlet-name> <!--display-name>Apache-Axis2 Servlet</display-name--> <servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class> <!--<init-param> <param-name>repository</param-name> <param-value>/WEB-INF</param-value> </init-param>--> <load-on-startup>1</load-on-startup> </servlet> 2. Yup, those JAR files look fine 3. No, you don't need to activated Axis at the Tomcat level to get it working. I only have it activated at the jasperserver level. 4. You don't need to deploy Axis as a separate web application. And yes, Axis is part of the JasperReports Server application, so you don't need an extra deployment like that.

Regarding the JNDI problems you're having: I would suggest that you check to see if there's a duplicate of the context.xml in one of Tomcat's other directories. I say this because I know that Tomcat sometimes keeps a duplicate of the context.xml in this directory: [TOMCAT_HOME]/conf/Catalina/localhost You'll often see a set of XML files in there, including one called jasperserver.xml or jasperserver-pro.xml. If it's there's then delete it. When Tomcat starts up, it first checks in that directory for the existence of an application context file. If it finds it there, then it won't look in the [TOMCAT_HOME]/webapps/jasperserver/META-INF directory for context.xml, even if you've modified it. After you delete the XML file in that localhost directory, start Tomcat. Tomcat will then look for the application context file in the localhost directory and not find it. It will then look for the context file in the META-INF directory, find it, and then make a copy of it and put the copy in the localhost directory. Tomcat 6 seems to do this by default, and Tomcat 7 seems to go directly to the META-INF directory.

Interesting, I'm wondering if there's something wrong with your web.xml file. Your URL says http://localhost:8080/jasperserver-pro/services/repository, but your message says "Servlet Axis2Servlet is not available." So that means that the servlet mapping is right. It then looks up the servlet class associated with the servlet name "Axis2Servlet". I'm wondering if perhaps your servlet class is incorrect? Mine is org.apache.axis.transport.http.AxisServlet, and it's in axis-1.3.jar under WEB-INF/lib. That's all I can think of.

Really strange, your chart element is entirely within the band! Hmm...What happens if you use a slightly older version of iReport? Maybe iReport 4.5.1?

Hmmm, interesting. Could it be the version of the software you're using to open the ODT file? I was able to export a report with a graphic to the ODT format, and then I tried opening it in different environments: - This works: Windows 7, Open Office 3.4 - This doesn't work: Ubuntu 12.04, Open Office 3.5 Also, I saw that Flash-based charts won't export and will leave a big gray area in the document.

Hi, you get the " Warning: Element bottom reaches outside band area" message when the chart element is bigger than the dimensions of the band. So try stretching down the summary band so that the line chart element fits inside the Summary band. You can make the Summary band bigger by pulling down the bottom edge of Summary band. Or you could select the Summary band in the Report Inspector, and set the "band height" property to a higher value.

What band are you putting the line chart in? Is it the Detail band? What happens when you put it in the Summary band?

Happy to see that you're considering JasperReports Server! I think you could download and install the product on your PC (it comes with an installer), and then start poking around in there. The installer will set up JasperReports Server and the components it needs: the Tomcat application server, the Postgres database and Java. That'll give you a better sense of the how it works. To answer your questions: 1. Yes. JasperReports is a web application that runs on an application server. The application server itself can run on your PC, a hosted server, or somewhere in the Cloud. Tomcat is the most commonly used application server, and it's the one that the installer sets up for you. End users log into JasperReports Server via a browser. 2. I'm not sure I understand your question. With JasperReports Server, you'll always need to run it within an application server, there's no way around that. If you decide to use a hosted server, you'll need to make sure it has Java, you'll need to set up Tomcat on it, and install a database. 3. JasperReports Server needs Java to run. You'll need JDK 1.6 at least. If your hosted server doesn't have Java available, then you'll need to set it up there somehow, or find a host server that has it.

The way to disable serializing session is to modify the context.xml at the Tomcat level. If you look at the [TOMCAT_HOME]/conf/context.xml file, you'll see: <!-- Uncomment this to disable session persistence across Tomcat restarts --> <!-- <Manager pathname="" /> --> When you uncomment it, you'll stop getting those stack traces when you restart Tomcat.

It's interesting that you're getting this error in your stack trace: "com.jaspersoft.jasperserver.api.JSException: jsexception.report.resource.already.exists.no.overwrite" In the output settings screen (the second step when scheduling jobs), did you activate the "sequential file names" option? I would try that, and leave the default value, which appears as "(default)". The error suggests that the server is trying to write a report but then doesn't because it found the same report name already there. By adding the sequential file names option, you're at least getting rid of that possibility.

After you start Tomcat, do you see an error in your browser, when logging into JasperReports Server? Do you see the normal login screen? I ask because Tomcat's default behavior when it shuts down is to persist the contents of user sessions, so that when it restarts, the sessions are re-established. JasperReports Server doesn't serialize its user sessions, which is why you get the stack traces you see. That is not a problem since new sessions will be created when users start interacting with the system via the browser.

I think there's a bug in there, so I can offer you two workarounds: - Create a JNDI entry for your database connection (create another Resource entry in context.xml, which is under the META-INF directory). This will allow you to reference the driverClassName you need for your connection, and JasperReports Server won't do a check on the driver class name. Then when you restart the server, all you need to do is create a JNDI datasource, where you reference the JNDI entry. - if you really do need a JDBC datasource, find the security.properties file (it's under WEB-INF/classes/esapi), and find the line that starts with: reportDataSource.driverClass - then change it to: reportDataSource.driverClass=AlphaDot,AlphaNumUnderscore,5000,true,driverClass-addDataSourceFlow_context the second parameter is the rule that gets enforced when filling in a value for that driver class field. You can see those rules in the validation.properties file (same directory as security.properties). You'll see that they're based on regular expression patterns. By changing the rule to AlphaNumUnderscore, you're telling the system to accept alpha-numerics and underscores for that field. - after you've made the change, restart the server. - This is where you might see the bug. If you CREATE the entry with the underscore, then it might complain again, even though you just modified the rule. But, if you're MODIFYING a previously created datasource, it won't complain when you change the driver classname to include an underscore. I would suggest that you go for the JNDI solution, because the other big benefit you get is that Tomcat will then manage the database connection pool instead of JasperReports Server. App servers like Tomcat are much better at managing DB connection pools.

I'm not familiar with Oracle apps, but the way you describe it, it sounds like there's a front-end (via a browser?), with a server backend, where users can use the various Oracle applications. It also sounds like you have a reporting requirement that you're trying to fulfill with Jaspersoft products. First of all, you're taking the right approach by using iReport to design your reports. You'll have to connect it to an Oracle datasource. iReport is only a desktop application; you use it to design reports, and once you're satisfied with the reports (how they look and their contents), you need to deploy the report to a server environment. In your server environment, you won't need iReport. At the server level, you have a couple of choices. You can either deploy the JasperReports library to the server, and your server will use the library to fill and output the reports. You would be responsible for building the report functionality and using the JasperReports APIs to compile the reports you built in iReport, filling them with data, and returning the finished report in the right format to the user. Your other choice is to simply set up JasperReports Server, which is a standard Java web application, and integrate your Oracle apps with JasperReports Server. You can do this in many ways (such as web services or IFrame integration), and you get the advantage of getting server functionality (such as scheduling reports, OLAP, email integration, etc) in addition to the JasperReports library.

I'm assuming that you want you use iReport to develop reports that use Oracle as a datasource. For that, you will need to use the professional edition of the product, which has certified support for Oracle as a datasource. The community edition of iReport doesn't officially support Oracle, only PostgreSQL. To test drive the commercial version of iReport, I suggest you download the commercial server edition (which comes contains the professional version of iReport) from http://www.jaspersoft.com/jaspersoft-business-intelligence-software-trial.

It could be a couple of things: - not enough memory for iReport - you can configure how much memory the JVM for it uses by editing the ireport.conf file, which you can find under the etc directory. Edit the default_options parameter, and modify the -Xms and -Xmx values to something higher, like 1024m. The MaxPermSize could be lower too, maybe just 128m. - Windows 7 - I also have a Windows 7 machine, it's 64-bit. I used to have problems with iReport too, until I changed the JDK. If your system is also 64-bit, I would suggest downloading JDK 1.7 (there's a specific 64-bit version), and modify the jdkhome variable in ireport.conf to point at JDK 1.7.

Using the report inspector, select the top node, which is the report name. What you need to do next is modify the "Columns" property, and change it from the default value of 1. Change it to 3. At this point, your detail band will be divided into three areas. Next, drag the fields you want in your report to the left-most area in the details band. There's another property called "Print Order," which you can set to either "Horizontal" or "Vertical". If you set it to "Horizontal", then the results get printed left-to-right and top-to-bottom; "Vertical" prints it out top-to-bottom, left-to-right. Test it out with your data to see which one you prefer. From the way you describe your problem, it sounds like you want "Horizontal."

Hmm. Interesting. When you try to add a Database JDBC connection, and when you look at the drop-down list of JDBC drivers, does the entry for net.sourceforge.jtds.jdbc.Driver appear in black text or red text? (Red means it can't find it in the classpath). Also, how did you add the JAR file to the classpath? I added that JAR file using Tools->Options->Classpath and then I added the JAR there, and that works for me. Is this what you did too? (I tested this on Ubuntu 12.04, iReport 4.6, using the jtds-1.2.5.jar on the Sourceforge.)

I remember getting a similar error when I zipped up the theme files incorrectly. I would check that the zip file with your theme files is properly structured. Extract your ZIP file to a temp directory, and make sure that there isn't a folder at the root level of the ZIP file. At the root level, you should see CSS files, and if it exists, an images subfolder.

Welcome! JasperReports Server will run on your Windows SP3 machine, so if you start by running the installer, it will install the other components it needs (Java 1.6, MySQL on the Community edition or Postgres on the commercial edition, Tomcat 6). Make sure to install the sample data (which will let you see finished reports) and iReport as well. You mentioned doing dashboards, which is functionality that's only available in the commercial edition, so take a look at that one too. Once you've set up your server environment, you can start experimenting with it. We have articles in the Jasperforge site about how to get started. There's also some handy videos that give you an overview of what JasperReports Server can do: http://jasperforge.org/website/jasperserverwebsite/JSJA%20Website/jasperserver_getting_started.html?header=project&target=jasperserver - gives overview of what you can do http://www.youtube.com/user/JaspersoftBISuite - our YouTube channel - A video on creating a report with iReport

Using a database client like Squirrel, have you made sure that the query executes properly? What errors does iReport return? Another possibility would be to create a stored procedure. Then in iReport, you would just call the stored procedure. What database are you using?

You'll find the ireportpro.conf file under [ireport_install_directory]\etc\ireportpro.conf. If you installed iReport with the installer, there's an ireport folder in the folder where you installed JasperReports Server. There are two lines in that file that I would change: Uncomment out the jdk home setting, and point it explicity to where you've installed th 64-bit JDK 1.7. Change it from: #jdkhome="/path/to/jdk" To something like what you see below: jdkhome="C:\Program Files\Java\jdk1.7.0" I would also change the "default_options" line from: default_options="-J-Xms24m -J-Xmx512m -J-Dorg.netbeans.ProxyClassLoader.level=1000 -J-XX:MaxPermSize=256m" to something that gives the JVM running iReport more memory and a lower MaxPermSize value. An default_options="-J-Xms1024m -J-Xmx1024m -J-Dorg.netbeans.ProxyClassLoader.level=1000 -J-XX:MaxPermSize=128m"

The community edition doesn't have ad hoc reporting functionality. You get ad hoc reporting (all the items you mentioned), dashboards and multi-tenancy in the commercial edition of the product. You can download a trial version of the commercial edition, it comes with a 30-day trial license.