Using HTML5 charts in JasperReports version 5.x., how do I color my chart series based upon the values in my dataset without ordering my query?   For example, an answer of "no" should be RED, "yes" should be green, like:

Resolution:

You can set series color as an axis level property, then in the Advanced Properties of your measure, add a Series Property Contributor with the name "color", which is the highcharts series property name, and specify a bucket property value of [axis level name].[property name].

See the attached example, hc_series_color.jrxml, suitable for version 5.1 or higher, and reference our sample "foodmart" database as your datasource.

hc_series_color.jrxml.txt

Ref. Case #00034523

hc_series_color.jrxml

In this article I want to describe how to customize the standard behavior of Multi Axis chart.

Example 1:

We have a Multi Axis chart which in turn contains a stacked area chart and a couple of line charts in the order that is shown on the picture below:

You may ask - so what? What kind of issue may cause such disposition of the sub charts in Multi Axis chart?

Lets execute this report and check the results of this execution:

As you can see from the picture below some parts of Stacked Area chart overlap the Line charts, but you can still clearly interpret the information that was shown in the chart.

Example 2:

Stacked area charts are filled in with the values that are very close to the maximum values and they fill almost all the space in the chart:

Such visualization of the data is not so convenient becuse it's not possible to analyze the information that was represented with the Line Charts.

What can we do to change the behavior of the Line Charts in this situation?

One of the possible solutions is to write the Java code that implements the Customizer class that should change the behavior of the Line Charts(I mean show them infront of Stacked Area chart).

Below I quote the source code of such class (MultiAxisOrderCustomizer.java) which was kindly provided to me by one of our leading developers:

import org.jfree.chart.JFreeChart;
import org.jfree.chart.plot.CategoryPlot;
import org.jfree.chart.plot.DatasetRenderingOrder;
import org.jfree.chart.plot.Plot;
import org.jfree.chart.plot.XYPlot;

import net.sf.jasperreports.engine.JRAbstractChartCustomizer;
import net.sf.jasperreports.engine.JRChart;

public class MultiAxisOrderCustomizer extends JRAbstractChartCustomizer {
    @Override
    public void customize(JFreeChart chart, JRChart jasperChart) {
        Plot plot = chart.getPlot();
        if (plot instanceof CategoryPlot) {
            ((CategoryPlot) plot).setDatasetRenderingOrder(DatasetRenderingOrder.FORWARD);
        } else if (plot instanceof XYPlot) {
            ((XYPlot) plot).setDatasetRenderingOrder(DatasetRenderingOrder.FORWARD);
        }
    }
}

To use this Customizer Class in the report

1. give the path to this class in iReport designer

2. fill in the name of this class in the Multi Axis chart/Customizer Class property

   

Let's check the behavior of the charts after the we have applied the adjustmens that should integrate the MultiAxisOrderCustomizer in our report:

In the picture above the two line charts are shown in front of Stacked Area chart.

How to compile the source code (Windows 7)

1. Download Java JDK from the Oracle site

2. Run the windows console by executing the cmd command

3. In the windows command line, define the JAVA_HOME variable. You can do this by executing the command that I quote below

   set JAVA_HOME=c:<path to Java JDK>java
   

4. Add JAVA_HOME variable to the windows PATH variable

   set PATH=%JAVA_HOME%bin
   

5. Compile the MultiAxisOrderCustomizer (to compile this file you need two Java libraries: jfreechart.jar and jasperreports.jar)

   In my test environment was installed JasperReports Server v5.0. This distribution contains both libraries in its lib folder.

   I gave the path to these libraries in javac compiler via the -classpath key as shown below:

   javac -classpath C:jaspersjrs_500apache-tomcatwebappsjasperserver-proWEB-INFlibjfreechart-1.0.12.jar;C:jaspersjrs_500apache-tomcatwebappsjasperserver-proWEB-INFlibjasperreports-5.0.0.jar MultiAxisOrderCustomizer.java
   

   

   If everything is ok you should find MultiAxisOrderCustomizer.class file in the same directory with MultiAxisOrderCustomizer.java file.

Please find in the attachment, files.zip:

• MultipleAxisChartReport.jrxml report (this report is based on Sugarcrm database that is supplied with JasperReports Server)
• MultiAxisOrderCustomizer.java
• MultiAxisOrderCustomizer.class
• jfreechart-1.0.12.jar
• jasperreports-5.0.0.jar

Thats all. Thank you for your attention to this article :).

files.zip

Issue:

In some use cases default aggregation function in domain designer is set to "None". In some rare cases, if you need to edit many fields, you may want to change the default aggregation function selected in UI:

Resolution:

In order to change it, find file /domain.designer.display.js. Locate the lines:

if (!item.isParent()) {
    metanode.extra['dataType'] = item.param.extra.JavaType,
    metanode.extra['defaultAgg'] = 'none',
    metanode.extra['defaultMask'] = 'none'
}

Change metanode.extra['defaultAgg'], for example, to this:

metanode.extra['defaultAgg'] = 'Average',

You will need to refresh your page.

Note that this is only a UI setting, and won't change your domain. It is relevant only when selecting Measures.

As a new developer who is on a learning curve of using Jasper Reports in web applications, you will discover that there is very limited information about more advanced features of Jasper Reports like calling stored procedures and using ORACLE_REF_CURSOR sa result set.

And the above linked article does a great job in describing how you go about building report which calls stored procedure and uses ref cursor.

However once you take this report and deploy it to your web application - you will learn that it will not work in the web application environment.

This article is the result of hours of research and trial and error attempts to make it work. And I share it with the hope that it will save time and trouble for others going the same route.

Here are the steps you need to take to make Jasper report work in your web application:

1. Download JasperReports Library from http://sourceforge.net/projects/jasperreports/files/jasperreports/

2. Copy jasperreports-{version}.jar, iText-{version}.js1.jar, commons-digester-{version}.jar and groovy-all-{version}.jar under your web application lib folder (WEB-INF/lib).

3. Download JasperReports Extension Library from http://www.java2s.com/Code/Jar/j/Downloadjasperreportsextensions353jar.htm;

Then unzip and copy jasperreports-extensions-3.5.3.jar under your web application lib folder (WEB-INF/lib).

NOTE: You will need this extension library in order to execute plsql calls to stored procedure and without this extension your report which calls stored procedure will not work.

Then as an example of web application code to create and return PDF report will look something like this:

try {
   // Custom code to get DB Connection
   Connection conn = getDataSource().getConnection();

   // This will be output PDF stream
   ByteArrayOutputStream outputStream = new ByteArrayOutputStream();

   // You will need to specify relative path to your Jasper report:
   URL fileUrl = getClass().getClassLoader().getResource("path to report.jasper");

   JasperReport jasperReport = (JasperReport) JRLoader.loadObject(fileUrl);

   /* This line sets correct factory to parse and process PLSQL procedure calls.
      The PlSqlQueryExecuterFactory class is located in jasperreports-extensions-3.5.3.jar */

   jasperReport.setProperty( "net.sf.jasperreports.query.executer.factory.plsql"
                            ,"com.jaspersoft.jrx.query.PlSqlQueryExecuterFactory");

   /* You may need to execute following line just once in your application.
     You can try to move it into initialization or static code block.
     Also you may notice that line below is marked as deprecated. 
     However in my case the export to pdf fails without this line being executed. */

   JRProperties.setProperty( JRQueryExecuterFactory.QUERY_EXECUTER_FACTORY_PREFIX+"plsql"
                           ,"com.jaspersoft.jrx.query.PlSqlQueryExecuterFactory");

   /* Prepare Jasper print and exporter objects in lines below */

   JasperPrint print = JasperFillManager.fillReport(jasperReport, params, conn);
   JRExporter exporter = new JRPdfExporter();
   exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, outputStream);
   exporter.setParameter(JRExporterParameter.JASPER_PRINT, print);
   exporter.exportReport();     // Generate PDF report
   return outputStream;         // Return stream result to your application code
                                // to wrap in response object.
}
catch (Exception ex) {
   log.severe("Exception loading pdf: " + ex.getMessage());
}

This should be all you need. If you find this article useful - please mark it as such.

- Eugene Luzgin (eluzgin@gmail.com)

Premise:

You have a functioning JasperResports Server. You want to access content from it without using the JasperResports Server web UI.

Possibilities:

To run a report with just a url and not using web services, you can do something like this:

http://gazelle.jaspersoft.com:8090/jasperserver-pro/flow.html?_flowId=viewReportFlow&reportUnit=/reports/Heartbeat/DatasourceDatabases

http://localhost:8080/jasperserver-pro/flow.html?_flowId=viewReportFlow&reportUnit=/reports/samples/myreport¶m1=value1¶m2=value2

http://localhost:8080/jasperserver-pro/flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=/supermart/SupermartDashboard30

To access previously generated content, you can use something like this:

http://localhost:8080/jasperserver-pro/fileview/fileview/contents/AllAccounts.pdf

(that's right, "fileview" is in the url twice)

Anonymous Access:

The urls above will of course only work for a logged in user. It's somewhat common to want to expose some set of reports to anonymous users. A page detailing how to do this can be found at:  Allow Anonymous Access to Reports

I want to put domains as a default value when i create an adhoc report and choose its data source, but presently a topic has this default value.

Resolution:

modify <js-install>/scripts/adhoc.start.js

In the initialize section of adhocStart(), there is a switch statement that specifies the default  behavior:

    /**
     * This is for the initialization of ad Hoc's start page
     */
    initialize : function(){
        dialogs.popup.show($("sourceDialog"), true);
        //get the topic path
        var options;
        var UNSPECIFIED_TOPIC ="unspecifiedTopic";
        if(!defaultTopic){
            this.DefaultTopicsPath = defaultTopicDir + UNSPECIFIED_TOPIC;
        }else{
            this.DefaultTopicsPath = defaultTopicDir + defaultTopic;
        }

        if(!isNotNullORUndefined(this.TopicsTreeContainerId)){
            return;
        }

        switch (window.launchType) {
            case this.DOMAIN_LAUNCH_TYPE:
                this.hideRealmTree(this.DOMAIN);
                this.getDomains();
            break;
            case this.OLAP_CONNECTION_LAUNCH_TYPE:
                this.hideRealmTree(this.OLAP_CONNECTION);
                this.getOlapConnections();
            break;
            default:
                // Fall back to Adhoc Topic
                this.getTopics();
        }
        this.initializeHandlers();
    },

Modify the switch statement to look like this:

        switch (window.launchType) {
            case this.DOMAIN_LAUNCH_TYPE:
                this.hideRealmTree(this.DOMAIN);
                this.getDomains();
            break;
            case this.OLAP_CONNECTION_LAUNCH_TYPE:
                this.hideRealmTree(this.OLAP_CONNECTION);
                this.getOlapConnections();
            break;
            default:
                // Fall back to Adhoc Topic
                // this.getTopics();
                this.hideRealmTree(this.DOMAIN);
                this.getDomains();
        }

Restart JasperReports Server

Ref. Case #00032221

Introduction

The problems we're addressing are:

• How to create a custom authentication filter
• How to create profile attributes with the custom filter
• How to call up the profile attribute when creating a custom data source - when we pull up the attribute values, then we'll be able to take those values and do any extra processing.

Overview of Solution

• Create the custom authentication filter
  • Have it read the request parameters from the URL
  • Add the profile attribute values for the parameters used in the User DTO objects
• Execute the report
  • Call the report via a URL
  • Have the custom data source use the profile attribute values to do extra processing

Create the custom authentication filter class

• Have it implement javax.servlet.Filter and org.springframework.beans.factory.InitializingBean
• Implement the doFilter method
• Have it create the profile attributes based on the request parameters
  • Check if the parameter contains values necessary for a User DTO object
  • If so, then create a profile attribute based on that key-value pair

     

  package example.cds.auth;
  
     import org.apache.commons.logging.Log;
     import org.apache.commons.logging.LogFactory;
     import java.io.IOException;
     import java.util.Iterator;
     import java.util.Map;
     import java.util.Set;
     
     import javax.servlet.Filter;
     import javax.servlet.FilterChain;
     import javax.servlet.FilterConfig;
     import javax.servlet.ServletException;
     import javax.servlet.ServletRequest;
     import javax.servlet.ServletResponse;
     import javax.servlet.http.HttpServletRequest;
     import javax.servlet.http.HttpServletResponse;
     
     import org.springframework.beans.factory.InitializingBean;
     import org.springframework.security.Authentication;
     import org.springframework.security.context.SecurityContextHolder;
     
     import com.jaspersoft.jasperserver.api.metadata.user.domain.ProfileAttribute;
     import com.jaspersoft.jasperserver.api.metadata.user.domain.impl.client.MetadataUserDetails;
     import com.jaspersoft.jasperserver.api.metadata.user.service.ProfileAttributeService;
     import com.jaspersoft.jasperserver.api.metadata.user.service.impl.ProfileAttributeServiceImpl;
     
     public class SimpleAuthFilter implements Filter, InitializingBean {
     
         private static Log log = LogFactory.getLog(SimpleAuthFilter.class);
         private static final String [] userAttribs = {"teacherId", "userType","schoolId", "districtId"};
         private ProfileAttributeService profileAttributeService;
     
         public ProfileAttributeService getProfileAttributeService() {
             return profileAttributeService;
         }
     
         public void setProfileAttributeService(
             ProfileAttributeService profileAttributeService) {
             this.profileAttributeService = profileAttributeService;
         }
     
         @Override
         public void afterPropertiesSet() throws Exception {
             // TODO Auto-generated method stub
         }
     
         @Override
         public void destroy() {
             // TODO Auto-generated method stub
         }
     
         @Override
         public void doFilter(ServletRequest request,
                              ServletResponse response,
                              FilterChain chain)
                throws IOException, ServletException {
             // TODO Auto-generated method stub
     
             HttpServletRequest req = (HttpServletRequest) request;
             HttpServletResponse res = (HttpServletResponse) response;
     
             MetadataUserDetails user = null;
             Authentication auth = SecurityContextHolder.getContext().getAuthentication();
             if (auth != null && auth.getPrincipal() != null) {
                 if (auth.getPrincipal() instanceof MetadataUserDetails) {
                     user = (MetadataUserDetails) auth.getPrincipal();
                     Map<String, String[]> map = req.getParameterMap();
     
                     // if teacherId, userType, schoolType or districtId in param map
                     // then add them to profile attribute
                     processReqParams(map, user);
                 } else {
                     log.debug("The authentication object was not of the correct type: "
                               + auth.getPrincipal().getClass().getName());
                 }
             }
     
             chain.doFilter(req, res);
         }
     
         @Override
         public void init(FilterConfig arg0) throws ServletException {
             // TODO Auto-generated method stub
         }
     
         // This particular method could be greatly improved; for example it could
         // first check for the existence of those attributes before trying to
         // create them, but this is meant as an example
         private void processReqParams(Map<String, String[]> map, MetadataUserDetails user) {
             Set keys = map.keySet();
             Iterator i = keys.iterator();
             while (i.hasNext()) {
                 Object o = i.next();
                 String key = (String) o;
                 String value = (String) map.get(o)[0];
                 log.debug("key = " + key + ", value = " + value);
                 if (isFromUserDTO(key) == true && value != null) {
     
                     // Create the profile attribute
                     if (profileAttributeService == null) {
                         log.debug("profileAttributeService is null :(");
                     } else {
                         log.debug("profileAttributeService is not null");
                     }
                     ProfileAttribute attrib = profileAttributeService.newProfileAttribute(null);
                     attrib.setPrincipal(user);
                     attrib.setAttrName(key);
                     attrib.setAttrValue(value);
                     profileAttributeService.putProfileAttribute(null, attrib);
     
                 } else {
                     log.debug("The key is not in the UserDTO or the value is null");
                 }
             }
         }
     
         private boolean isFromUserDTO(String key) {
             boolean isFromUserDTO = false;
     
             for (String s : userAttribs) {
                 if (key.equals(s)) {
                     isFromUserDTO = true;
                     break;
                 }
             }
             return isFromUserDTO;
         }
     }
  

Modify the Spring configuration file

Modify the applicationContext-security-web.xml file in the /jasperserver-pro/WEB-INF directory. Add the bean definition and add the bean id to the filterChainProxy. For example, the bean ID definition will look like this:

<bean id="SimpleAuthFilter" class="example.cds.auth.SimpleAuthFilter">
    <property name="profileAttributeService">
        <ref bean="profileAttributeService" />
    </property>
</bean>

Adding the bean ID to the filterChainProxy will look like this:

/**=httpSessionContextIntegrationFilter
    , ${bean.loggingFilter}
    , ${bean.userPreferencesFilter}
    , ${bean.authenticationProcessingFilter}
    , ${bean.userPreferencesFilter}
    , SimpleAuthFilter,${bean.basicProcessingFilter}
    , requestParameterAuthenticationFilter
    , JIAuthenticationSynchronizer
    , anonymousProcessingFilter
    , exceptionTranslationFilter
    , filterInvocationInterceptor
    , switchUserProcessingFilter

How to add profile attributes

I added profile attributes in the processReqParams method above, and it's an example of how to programmatically add profile attributes for a logged-in user. The method calls up the profileAttributeService that was defined for the SimpleAuthFilter bean, which allows us to manipulate profile attributes via the engine. You can verify that the attributes have been written to the database by consulting the jiprofileattributes table.

How to pull up the profile attributes

Once the profile attributes are stored, we can go ahead and pull them up when creating the custom data source object. The process is to:

• Call up the data source constructor
• Within the constructor, call up the current user object
• Get that user's profile attributes
• Do any extra processing at this point with the profile attribute values
• Below you'll find an example of how to pull up the profile attributes data. It's a modified version of the CustomDataSource class that our products ships with, which you can find in the samples directory.

   

  public CustomDataSource() {
      MetadataUserDetails user = null;
      Authentication auth = SecurityContextHolder.getContext().getAuthentication();
      if (auth != null && auth.getPrincipal() != null) {
          if (auth.getPrincipal() instanceof MetadataUserDetails) {
              user = (MetadataUserDetails) auth.getPrincipal();
              // if teacherId, userType, schoolType or districtId in param map
              // then add them to profile attribute
              List attribs = user.getAttributes();
              int size = attribs.size();
              if (size > 0) {
                  Iterator i = attribs.iterator();
                  while (i.hasNext()) {
                      //String attrib = (String) i.next();
                      ProfileAttributeImpl attrib = (ProfileAttributeImpl) i.next();
                      String attribName = attrib.getAttrName();
                      String attribValue = attrib.getAttrValue();
                      LOG.debug("Attrib: Name = " + attribName + ", Value = " +
                                attribValue);
                  }
              }
          } else {
              LOG.debug("The authentication object was not of the correct type: " +
                        auth.getPrincipal().getClass().getName());
          }
      }
  }
  

How to call the report via a URL

You can construct a URL such as the one below:

http://localhost:8080/jasperserver-pro/flow.html?_flowId=viewReportFlow&standAlone=true&the_city_distinct=Dallas&userType=teacher&_flowId=viewReportFlow&ParentFolderUri=%2Fpublic&reportUnit=%2Fpublic%2FsampleCDS_Report

This URL is based on the Custom data source example that ships with the product:

• "the_city_distinct" is a value that gets fed into an input control. I changed the input control to "not mandatory" and the report executes without bringing up the pop-up window asking the user to populate a value for this parameter
• "userType" is a parameter key I used to simulate an attribute we wish to work with
• You can also add j_username and j_password parameters to perform the authentication as well.

1. Navigate to

   <jrs_install>/jasperreports-server-<version>/apache-tomcat/bin/
   

2. Locate the 'tomcat6w.exe' file and rename it to jasperreportsTomcat.exe.  This needs to match the name of the service.

3. Now simply double click and run the file (you may need to right-click > 'Run as administrator').  This will bring up the Tomcat properties page.

4. Java options can be added/modified/removed in the 'Java' tab.  Once done, restart the service and the settings should take effect.

In versions 5.0.1 and later, you can log in as superuser and run the diagnostic report in /Public/Diagnostic as a quick way to see the current java options and confirm they've taken effect.

NOTE:  The 32 bit JVM is limited to 2GB total memory.  If you are running the 32 bit version, you will have to be sure your heap and permgen memory do not exceed 2GB.

Introduction

This tutorial covers basic performance diagnostic and tuning techniques for IBM JVM garbage collection. The tutorial focuses on basic memory problems and present command line settings that act as a starting point for improving garbage collection performance when running JasperReports Server.

Product Version

The tutorial works with any version that works with Java 5.0 or later.

Objectives

This guide will enable you to:

• Diagnose memory problems
• Add/Modify JVM command line options to improve garbage collection performance
• Increase heap space and perm gen space as needed

Pre-Requisites

• Basic administration of common J2EE web or application servers (tomcat, JBoss, GlassFish)
• Required permissions to shutdown and restart the server and edit config files

Assumption: Use of bundled Tomcat included with JasperReports Server. Adapt as needed for other application servers and platforms.

Diagnosing Memory Problems

Overview of diagnosing memory problems:

• Launch JConsole
• Have users use JasperReports Server or simulate load with QA tool
• Watch memory usage

Adding/Modifying JVM Command Line Options

Change garbage collection algorithm in use:

• Add/Modify JVM settings
• Restart JasperReports Server
• Watch memory usage

Increasing Heap Space and Perm Gen Space

Change JVM Heap and Perm Gen Settings:

• Add/Modify JVM settings
• Restart JasperReports Server
• Watch memory usage

What's Next?

For additional information, refer to the following:

• JasperReports Server Ultimate Guide
• JasperReports Server Pro Admin Guide, located in the <js-install>docs folder.
• Using JConsole

Written by

This tutorial was written by Steve Park, Professional Services Consultant, June 2009

In this article I want to describe how to compile the JasperReports library 5.0.0 and a couple of complex moments that may interrupt this process.

The most important moment related to the version of the Sun Java JDK that should be used to compile the library and then the samples that are supplied with it(I needed to compile htmlcomponent (<jasperreports-pro-5.0.0>jasperreportsdemosampleshtmlcomponent)).

In my first test I tried to compile JasperReports 5.0.0 commercial library with the Sun Java 1.6 Jdk (output of the java -version command is shown below)

java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

but this process was interrupted with the error that is shown on the picture below:

The full text of the error message:

[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] jasperssourcesjasperreports-pro-5.0.0jasperreportssrcnetsfjasperreportsrepoFileRepositoryPersistenceServiceFactory.java:[89,30] type parameters of M cannot be determined; no unique maximal instance exists for type variable M with upper bounds M,net.sf.jasperreports.repo.PersistenceService

[ERROR] jasperssourcesjasperreports-pro-5.0.0jasperreportssrcnetsfjasperreportsrepoDefaultRepositoryPersistenceServiceFactory.java:[86,30] type parameters of M cannot be determined; no unique maximal instance exists for type variable M with upper bounds M,net.sf.jasperreports.repo.PersistenceService
[INFO] 2 errors

This error is related to the bug that exists in this version of Sun Java JDK (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6302954) and according to the information from their site it was fixed in 1.6.0_43.

To solve the issue related to this bug I downloaded the latest version of the Sun Java.

Below I quote the output of the java -version command:

java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

With this version of the Sun Java JasperReports 5.0.0 commercial library and htmlcomponent.jar was compiled without any errors.

Let's do all these steps in the "sources" folder

Below I list the steps that should be done to compile the JasperReports 5.0.0 commercial library from the Windows 7 command line:

1. download JasperReports 5.0.0 commercial library from the support portal
2. unzip it into the sources folder c:jasperssourcesjasperreports-pro-5.0.0
3. download and install Java JDK from the Oracle site (Java Platform (JDK) 7u17 is the most modern version for the moment of this arcticle creation).
   http://www.oracle.com/technetwork/java/javase/downloads/index.html
4. download apache-maven build tool from the http://maven.apache.org/download.cgi url (I've downloaded 3.0.5 version of this program)

We need it to build JasperReports library

1. unzip apache-maven in the sources folder c:jasperssourcesapache-maven-3.0.5
2. download apache-ant build tool from the http://ant.apache.org/bindownload.cgi (I've downloaded 1.8.4 version of this program)

We need apache-ant to build the samples in the c:jasperssourcesjasperreports-pro-5.0.0jasperreportsdemosamples folder

1. unzip apache-ant in the sources folder c:jasperssourcesapache-ant-1.8.4
2. run Windows command line by executing the cmd.exe program
3. define the system variables that should describe the path to the binaries of the javac, mvn, ant and cmd programs and allocate some memory for apache-maven build tool:

set JAVA_HOME=C:Program FilesJavajdk1.7.0_17
set ANT_HOME=c:jasperssourcesapache-ant-1.8.4
set M2_HOME=c:jasperssourcesapache-maven-3.0.5
set MAVEN_OPTS=-XX:PermSize=512m -XX:MaxPermSize=512m -Xms512m -Xmx512m
set PATH=%JAVA_HOME%bin;%M2_HOME%bin;%ANT_HOME%bin;C:WindowsSystem32

and check that these programs(I mean java, mvn, ant and cmd) are available from the command line.

You can do this by typing the commands that I list below from the command line where the system variables that I list below have been executed:

java -version
mvn -version
ant -version

Each command should produce the output that desribes its version

After we confirmed that our environment has been successfully configured let's try to compile the JasperReports library:

1. navigate to the jasperreports subfolder and compile the community version of the JasperReports library

cd jasperreports
mvn clean install

This builds and installs the JasperReports Community Edition JAR into your local Maven repository and makes it available to the
subsequent build steps, which require it as a build dependency. The resulting JasperReports Community Edition JAR file can be found
under the <jasperreports-install>/jasperreports/target folder.

2. return to the main folder of the library distribution and compile the license-related dependencies that are shipped with
JasperReports Professional and Developer editions.

cd ..
mvn clean install

3. the third step in building JasperReports Professional or Developer editions is the creation of the JasperReports Fusion Component JAR file.

cd jasperreports-fusion
mvn clean install

This creates and installs (into the local Maven repository) the JasperReports Fusion JAR file that you can also find under the /jasperreports-fusion/target folder of the current package.

4. the last step in building JasperReports Professional or Developer editions is the creation of the JasperReports HighCharts Component JAR file.

This is achieved by launching the following Maven build command in the /jasperreports-highcharts subfolder

cd ..
cd jasperreports-highcharts

This creates and installs (into the local Maven repository) the JasperReports HighCharts JAR file that you can also find under the
/jasperreports-highcharts/target folder of the current package.

5. Let's try to compile the htmlcomponent library(this compoment may be useful in your report)

cd ..
cd jasperreports/demo/samples/htmlcomponent
ant clean jar

As you can see from the screenshot below the htmlcomponent.jar file has been successfully compiled

In this article we configured the build environment and compiled JasperReports 5.0.0 commercial library and one of the components that is supplied together with library in the jasperreports/demo/samples folder. You can also find the steps that were described in this article in the readme that is supplied with the JasperReports 5.0.0 library.

I've attached the readme file to this how-to.

Thank you for your attention to this article.

readme.txt

[toc on_off::hide=1]

While downloading an Excel sheet using JExcelApiExporter object. We are able to get the data in text format.

Is there any way to get the data in number format so that it can be used in excel sheet formula?

Resolution:

In JasperReports Server's file:

WEB-INF/applicationContext.xml

There is a bean named "xlsExportParameters", please

1. change the "detectCellType" property's value to "true",
2. save the file and
3. restart JasperReports Server.

Ref. Case #00020702 -- 14:33, 22 June 2011 (UTC)  

Advanced formatting with new HTML5 charts. Jaspersoft’s new HTML5 Pro charts allow you to create dynamic, visually appealing interactive content.

Advanced options can help you get the most out of them.

iReport Professional version5.0 introduced Jaspersoft’s new HTML5 charting library.

This entirely new set of interactive charts is not only visually attractive, it combines advanced chart capabilities with a rich set of supported user interactions including the ability to change the chart type on the fly. Let’s take a look at some of these new features as they appear when creating your content in iReport and when rendered on the JasperReports Server.

Below is an example of a simple and rather plain HTML5 chart.

The standard default settings provide a clean and readable, if not exciting, default set of visual settings. The most commonly used settings and rendering options can be accessed through the Chart Settings menu. This setting dialog can be access via the HTML5 Chart context menu (right click on the chart while it’s the active component in the designer). While these cover most of the settings required to customize the look and feel of many charts there are more sophisticated settings that can only be configured using the Advanced Options dialog.

Click the Show Advanced Options button located to the lower right of the Chart Setting dialog.

For a list of the available options, consult the Highcharts API reference at http://api.highcharts.com/highcharts. By expanding the available options, the hierarchy of settings can be viewed. When setting a Property Name, access a nested setting using the “.” character.

Another example modifies the yAxis label for a chart:

When entering an advanced setting, be sure to differentiate between a value and an expression. In general, a numeric setting can be considered a value and other types, an expression. Setting parameters must be either be of a native Java type or explicitly cast to a Java language construct. Note the setting in the example below: the gradient definition is explicitly cast to an array and returned as a list.

Currently iReport does not allow a Javascript function as a setting. Functions are first class constructs in Javascript without an analog in Java. As a result, they will be interpreted as strings and surrounded with quotes.

As an example, when setting a plot area a gradient resulting in the background in the chart to the left.

Note the JSON formatted settings in the Javascript constructor.

To configure the same settings using iReport, two settings must be added via the Advanced Options dialog. The first is featured in next example dialog. The gradient setting is nested within the chart and background color settings and is therefore defined as chart.backgroundColor.linearGradient. As noted previously, all settings must be cast, either explicitly or implicitly to a Java data type. The gradient takes an array as a parameter and therefore must explicitly be returned as a list, using the static java.util.Arrays.asList method.

To render the gradient, a second setting must be added to define stops - chart.backgroundColor.stops. This setting requires an array of arrays and is expressed through the nested use of java.util.Arrays.

Boolean values must also be explicitly returned as a Java Boolean class using the static field Boolean.TRUE (or Boolean.FALSE).

Below is the finished chart, customized through the use of advanced options followed by the source JRXML.

<!--?xml version="1.0" encoding="UTF-8"?-->
<jasperreport bottommargin="20" columnwidth="984" leftmargin="20"
              name="ChartingNumber1" pageheight="842" pagewidth="1024"
              rightmargin="20" topmargin="20"
              uuid="b805407a-9ca3-4b37-945a-37e767cd090f"
              xmlns="http://jasperreports.sourceforge.net/jasperreports"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemalocation="http://jasperreports.sourceforge.net/jasperreports
                                  http://jasperreports.sourceforge.net/xsd/jasperreport.xsd">
    <property name="ireport.zoom" value="1.0" />
    <property name="ireport.x" value="0" />
    <property name="ireport.y" value="0" />
    <querystring>
        <!--[CDATA[
            SELECT sum(store_sales) store_sales, sum(store_cost) store_cost,  store_type
              FROM "public"."sales_fact_1998" sales
              JOIN "public"."store" store  ON (sales.store_id = store.store_id)
             GROUP BY store_type]]-->
    </querystring>
    <field class="java.math.BigDecimal" name="store_sales" />
    <field class="java.math.BigDecimal" name="store_cost" />
    <field class="java.lang.String" name="store_type" />
    <title />

    <summary>
        <band height="300" splittype="Stretch">
            <componentelement>
                <reportelement height="300"
                               uuid="2b74e453-cd88-476e-ae4b-786bd34d8383" width="800" x="0" y="0" />
                <hc:chart type="Column" xmlns:hc="http://jaspersoft.com/highcharts"
                          xsi:schemalocation="http://jaspersoft.com/highcharts
                                              http://jaspersoft.com/schema/highcharts.xsd">
                <hc:chartsetting name="default">
                    <hc:chartproperty name="xAxis.labels.rotation" value="45" />
                    <hc:chartproperty name="credits.href" value="http://www.jaspersoft.com" />
                    <hc:chartproperty name="credits.text" value="Jaspersoft" />
                    <hc:chartproperty name="chart.shadow">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="chart.showAxes">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="chart.borderRadius">
                        <hc:propertyexpression>
                            <!--[CDATA[3]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="chart.zoomType" value="xy" />
                    <hc:chartproperty name="chart.plotShadow">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="subtitle.style.color" value="#FFFFFF" />
                    <hc:chartproperty name="legend.borderRadius">
                        <hc:propertyexpression>
                            <!--[CDATA[3]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="tooltip.useHTML">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="plotOptions.column.selected">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="tooltip.borderColor" value="#006666" />
                    <hc:chartproperty name="chart.backgroundColor.linearGradient">
                        <hc:propertyexpression>
                            <!--[CDATA[java.util.Arrays.asList(0,0,500,500)]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="chart.backgroundColor.stops">
                        <hc:propertyexpression>
                            <!--[CDATA[java.util.Arrays.asList(
                                            java.util.Arrays.asList(0, "#b5bdc8"),
                                            java.util.Arrays.asList(0.36,"#828c95"),
                                            java.util.Arrays.asList(1,"#28343b"))]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="xAxis.labels.style.color">
                        <hc:propertyexpression>
                            <!--[CDATA["#FFFFFF"]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="legend.floating">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="legend.align">
                        <hc:propertyexpression>
                            <!--[CDATA["center"]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="legend.shadow">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="legend.y">
                        <hc:propertyexpression>
                            <!--[CDATA[-200]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="colors">
                        <hc:propertyexpression>
                            <!--[CDATA[java.util.Arrays.asList(
                                               "#AA4643","#89A54E","#3D96AE",
                                               "#80699B","#4572A7","#DB843D",
                                               "#92A8CD","#A47D7C","#B5CA92")]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="title.style.color" value="#CCCCCC" />
                    <hc:chartproperty name="title.text" value="A More Sophisticated and Interesting Chart" />
                    <hc:chartproperty name="tooltip.shared">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="legend.backgroundColor" value="#FFFFFF" />
                    <hc:chartproperty name="exporting.enabled">
                        <hc:propertyexpression>
                            <!--[CDATA[Boolean.TRUE]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <hc:chartproperty name="xAxis.labels.style.fontSize" value="11" />
                    <hc:chartproperty name="yAxis.title.text">
                        <hc:propertyexpression>
                            <!--[CDATA["Dollars"]]-->
                        </hc:propertyexpression>
                    </hc:chartproperty>
                    <multiaxisdata>
                        <multiaxisdataset>
                            <dataaxis axis="Rows">
                                <axislevel name="Store Type">
                                    <labelexpression>
                                        <!--[CDATA["Store32Type"]]-->
                                    </labelexpression>
                                    <axislevelbucket class="java.lang.Comparable">
                                        <bucketexpression>
                                            <!--[CDATA[$F{store_type}]]-->
                                        </bucketexpression>
                                    </axislevelbucket>
                                </axislevel>
                            </dataaxis>
                            <dataaxis axis="Columns">
                                <multiaxismeasure calculation="Nothing"
                                                  class="java.lang.Number"
                                                  name="Store Sales">
                                    <labelexpression>
                                        <!--[CDATA["Sales"]]-->
                                    </labelexpression>
                                    <valueexpression>
                                        <!--[CDATA[$F{store_sales}]]-->
                                    </valueexpression>
                                </multiaxismeasure>
                                <multiaxismeasure calculation="Nothing"
                                                  class="java.lang.Number"
                                                  name="Cost">
                                    <labelexpression>
                                        <!--[CDATA["Cost"]]-->
                                    </labelexpression>
                                    <valueexpression>
                                        <!--[CDATA[$F{store_cost}]]-->
                                    </valueexpression>
                                </multiaxismeasure>
                            </dataaxis>
                        </multiaxisdataset>
                    </multiaxisdata>
                    <hc:series name="f" />
                    <hc:series name="S" />
                    <hc:series name="St" />
                    <hc:series name="Sto" />
                    <hc:series name="Stor" />
                    <hc:series name="Store" />
                    <hc:series name="Store " />
                    <hc:series name="Store s" />
                    <hc:series name="Store sa" />
                    <hc:series name="Store sal" />
                    <hc:series name="Store sale" />
                    <hc:series name="Store sales" />
                    <hc:series name="Store ales" />
                    <hc:series name="Store Sales" />
                </hc:chartsetting>
            </hc:chart>
        </componentelement>
    </band>
</summary>

Below I quote a short description of this feature from JasperReports Server User Guide -> Advanced Domain Features -> The DomEL Syntax -> Profile Attributes :

'A profile attribute is a name-value pair inserted in a user object, such as a user or role. It is ordinarily used to extend the object’s standard access grants, but it has other uses, as well. It can be added to objects by database tools or custom code'

The field length of this attribute in JasperReports Server Repository and JasperReports Server user interface is restricted to 255 characters. Some of the solutions require the length of this field that is longer then the length that is adjusted by default.

To increase the length of the Profile Attribute field three steps should be done (JasperReports Server v5.0.1):

1. The length of this field should be increased in the JasperReports Server Repository
2. The length of this field should be increased in <jasperserver-pro>WEB-INFapplicationContext-rest-services.xml
3. The length of this field should be increased in <jasperserver-pro>scriptsattributes.model.js

Below I provide the detailed description that shows how to do this:

1. I use PostgreSQL as the JasperReports Repository. The value related to the Profile Attribute field is stored in jiprofileattribute table and is named attrvalue.

   Plese refer to the screenshot below on which is shown sequense of commands that was used to increase the length of the attrvalue field.

   

2. Open the file, <jasperserver-pro>WEB-INFapplicationContext-rest-services.xml, and change the numeric value according to the changes that were done in the jiprofileattribute table

   <property name="maxLengthAttrValue">
       <value type="int">7000</value>
   </property>

3. Open the file, <jasperserver-pro>scriptsattributes.model.js, and change the value MAX_LENGTH_OF_VALUE to the value that you want.

   exports.settings = {
       MAX_LENGTH_OF_NAME: 255,
       MAX_LENGTH_OF_VALUE: 7000
   }

To apply the changes that have been done the application server should be restarted.

Thank you for your attention to this article.

Alex

Introduction

Using import/export scripts allows you to export and import content from the JasperServer repository. This tutorial utilizes import and export scripts to mass upload reports from a development environment to a production environment.

Additionally, it showcases how to take advantage of the JasperServer plugin for iReport. This tutorial can be used in any development and production environment; especially in situations where both development and production environments are using different technologies.

Objectives

This tutorial will enable you to:

• Locate and configure js-import / js-export scripts
• Export your reports
• Import your reports into a production environment for the same organization
• Import your reports into a production environment for a different organization

Locating and Configuring js-import and js-export Scripts

First, we need to configure the js-import and js-export scripts to connect to the JasperServer repository. The scripts are located in the /scripts directory.

Exporting Reports

Assumption: The demo samples that are provided with the installer are deployed on the development server. The production server is installed without the samples.

Best Practice: Maintain the same folder tree structure between production and other environments (for instance development or test).

By maintaining the same folder structure, you will avoid having to perform one-offs to upload reports.

Example: Export all reports within the organization_1/reports/samples folder

Importing Reports into Production Within the Same Organization

Reports and dependencies are now safely stored in a zip file. Next, re-import them. The easiest import scenario is categorized by having the same folder structure in development and production environments. First, create the organization in the production environment then upload your reports.

Note: If you wish to test import/export in a single JasperServer instance reinitialize the repository prior to this step. The initialization scripts are located in the scripts folder.

Example: For MySQL, run the scriptsMySQLjasper_init.bat (Download here), and then continue with the steps listed below.

Create the organization in the production environment.

Note: organization_1 is an organization that is created by default.

Once we have our organization correctly configured, then we can upload the reports using the js-import tool.

Example: In our example, make sure you have copied organization_1_reports_samples.zip into the scripts directory

Importing Reports into Production Environment for a Different Organization

Assumption: You already have an organization within your production environment, which differs from the development (in our example you do not have an organization using organization_1 as id).

In our example, the organization id we wish to upload our reports to is demo. This is not a best practice but a common case where development and production do not share same organization structure.

Js-Import and Js-Export scripts don’t provide a mechanism for specifying the organization id. Essentially, this limitation requires that you perform the transformation manually.

Below are the steps for defining the transformation.

Best Practice: Use a text editor such as Notepad++ to find and replace characters strings from multiple files at the same time.

Notepad ++ is a free text editor that can be downloaded here.

Written by

This tutorial was written by Guillaume Autier, Sales Engineer, June 2009.

Charting data that have widely differing values can be difficult using a single data axis. By using two or more axes, the data can be more easily understood. iReport Designer includes built-in support for multi-axis charts through the use of the JFreeChart package.

Product Versions

iReport Designer Professional 3.5.0 was used to create this tutorial.nIt should work identically in later versions of iReport Designer Professional and iReport Designer Community Edition. The concepts apply to older versions of iReport Designer, but the user interface differs.

Objectives

This guide will enable you to:

• Create a new report
• Create a simple line chart
• Create a more useful multi-axis chart
• Combine a bar chart with a line chart

Pre-Requisites

Familiarity with iReport Designer is helpful.

Creating a New Report

Creating a Simple Line Chart

Follow these steps to create a simple line chart.

Step	Action
1	Drag the Chart tool into the report.
2	Select the Line chart style Resize the chart to cover the full area
3	Right-click the chart and select Chart Data
4	Add 3 Series: Sales, Issues, and Bugs
5	The definition of each series should follow this model:
6	In preview mode the report now looks like this: Note: Line charts do have limitations: While the line chart looks reasonably good for the sales numbers, the issues are harder to read. The bug count is too small to read at all. The problem is that the number of bugs filed is roughly 1000 times smaller. This discrepancy in scale makes the chart less useful.

Creating a Multi-Axis Chart

Follow these steps to create a multi-axis chart.

Step	Action
1	To avoid having to re-type the series information, open the Chart Data dialog again and copy all three series http://www.jaspersoft.com/sites/default/files/images/JEM_MultiAxisChart_5.png
2	Delete the Line chart Drag the Chart tool into the report again Select the Multi Axis chart type
3	You are immediately prompted to choose a chart for the primary axis Choose Line chart
4	In the Report Inspector panel find the Multi Axis chart and set the Chart Data for the child Line Chart
5	On the Details tab paste in the series that were previously copied
6	If you run the report now it should look exactly as before
7	Remove the Issues and Bugs series Copy them first so you don't need to retype in the next step
8	Right-click the Multi Axis chart and choose Add Axis chart Choose another Line chart
9	Paste the Issues and Bugs series into this new line chart Previewing the report now shows the sales axis on the left with the issues and bugs axis on the right. The fact that new issues are increasing more quickly than new sales is now readily apparent.

Combining a Bar Chart with a Line Chart

The use of two different axes makes it easier to see the trends. However, the lines have a tendency to overlap since both charts will rise to the same height. Combining a bar chart with a line chart is a good solution to this issue.

What's Next?

These sample charts may be improved in many ways:

• The axes should be labeled more clearly
• A chart title makes it easier for a viewer to understand it quickly

The report can now be deployed to JasperReports Server for use in a dashboard or to be scheduled for regular delivery.

This tutorial covers basic performance diagnostic and tuning techniques for Sun and OpenJDK JVM garbage collection. The tutorial focuses on basic memory problems and command line settings for improving garbage collection performance when running JasperReports Server.

Objectives

This guide will enable you to:

• Diagnose memory problems
• Add/Modify JVM command line options to improve garbage collection performance
• Increase heap space and perm gen space as needed

Pre-Requisites

• Basic administration of common J2EE web or application servers ( Tomcat, JBoss, GlassFish )
• Required permissions to shutdown and restart the server and edit config files
• Java 5.0 or later

Assumption: Use of bundled Tomcat included with JasperReports Server

Diagnosing Memory Problems

Steps for diagnosing memory problems and monitoring memory usage:

• Launch JConsole
• Ask users to use JasperReports Server or simulate load with QA tool
• Watch memory usage

Adding and Modifying JVM Command Line Options

Overview to change garbage collection algorithm in use:

• Add or Modify JVM settings
• Restart JasperReports Server
• Watch memory usage

Increase Heap Space And Perm Gen Space

What's Next?

For additional information, refer to the following:

• JasperReports Server Ultimate Guide
• JasperReports Server Professional Administrator Guide, located in the docs folder
• Tuning Garbage Collection with the Java 5.0 Virtual Machine

Written By

This tutorial was written by Steve Park, Professional Services Consultant, June 2009.

Adding JRQueryExecuterFactory

To add a custom JRQueryExecuterFactory to JasperReports Server all you have to do is add it into jasperreports.properties file under the /Jasperserver-pro/WEB-INF/classes/ folder as follows:

net.sf.jasperreports.query.executer.factory.sql=
com.jaspersoft.commons.util.JSControlledJdbcQueryExecuterFactory

where last part of the key - sql - is a language your executer is going to understand.  

Issue Description:

[toc on_off::hide=1]

What is involved with stopping a Sub-Report displaying data on an excluded band? We have tried both of the below without success:

<property name="net.sf.jasperreports.export.csv.exclude.origin.subreport.repo:sub1-myreport.jrxml" value="detail"/>

<property name="net.sf.jasperreports.export.csv.exclude.origin.subreport.sub1-myreport.jrxml" value="detail"/>

Resolution:

Please find below a sample on having a subreport named "AddressReport" have its two bands, columnHeader and detail, excluded from the CSV export. In addition, please note the "AddressReport" is the name of the subreport in its own JRXML, independent of the name/subreport expression in the master report.

<property name="net.sf.jasperreports.export.csv.exclude.origin.report.mysubreport0" value="AddressReport"/>

<property name="net.sf.jasperreports.export.csv.exclude.origin.band.mysubreport0" value="columnHeader"/>

<property name="net.sf.jasperreports.export.csv.exclude.origin.report.mysubreport1" value="AddressReport"/>

<property name="net.sf.jasperreports.export.csv.exclude.origin.band.mysubreport1" value="detail"/>

Ref. Case #00027832 -- 06:06, 10 August 2012 (UTC)

[toc on_off::hide=1]

Take a look at your log4j.properties file (located in /jasperserver-pro/WEB-INF directory), and make sure that the log4j.rootLogger property isn't accidentally set to DEBUG; when it's set to DEBUG, the application will slow down significantly as it logs debugging statements to the /jasperserver-pro/WEB-INF/logs/jasperserver.log file (file I/O is notoriously slow).

See Also

• How to Produce Clean Log Files for Troubleshooting
• Log4j.properties - JasperReports Server

Below is a commonly used validation rule which ensures only sanctioned, secure SQL statements are allowed into the application for execution.
Validator.ValidSQL=^s*((?i)select)s+[^;]+$ 

To test via the regexplanet.com site, enter your expression into the "Regular Expression:" field.   When you enter the string, you must exclude any escaping backslashs which are present because these are strings passed to our java application, so try:
^s*((?i)select)s+[^;]+$

Next list various inputs, sql statements in this case, which you feel are potentially problematic.  These can be things you want to ensure are excluded, or they can be input values from your legacy system that you want to ensure match our validation rules:

Lastly, hit the test button to find your results.  If your required input value does not match, then you need to modify the regular expression.   Our example here uses SQL statements, but this applies to any of the validation rules used throughout our validation.properties configuration file.   Note that the results page outputs the "Java string" as it would need to be formatted in the valiation.properties file.

For more information on the security framework see article: Jaspersoft 4.5.0 Security Changes and Configuration

Ref. Case #00029994

Issue Description:

How can we control the justification of the barcode (left/right etc) or the position within the cell.

Resolution:

Barcodes use the font from the style associated to the report element. Note though that fonts from font extensions will not work, you need to use a font that's installed in the system/JVM. That's due to a limitation of the Barcode4J API.

Setting the horizontal alignment in the style associated to the element affects the position of the barcode.

Ref. Case #00027903

Issue Description:

[toc on_off::hide=1]

I've created a topic following these steps:
1. Add new report
2. Select the event manager domain in the event manager folder.
3. Selected the 'events' which are now under 'Selected fields'.
4. Click on 'save as topic' and put it in the myfolder/manager-topics/ folder.
5. I then clicked table, added a few fields, and then saved.

I can see the topic in the folder of type 'Domain Topic'. It's not showing up when I want to create 'Add new Report' and select topics. I've done it even as superuser in case it was a permissions issue.

What makes a topic appear in this list?

Resolution:

for topics to be considered topics they should be put into Adhoc Components/topics folder of the repository. In all other location they'll be considered ordinary reports (since they are a simple JRXML).

The folder where topics are to be stored to be considered as topics is defined as a search pattern. By default everything with the path %/adhoc/topics will be used. If you want to modify this you need to change these configurations:

file: applicationContext-adhoc.xml
bean: adhocEngineService
properties: realmsURI, realmsURIParentSQLPatternList

If they should be allowed to save their domain topics in the home folder then you'd need to extend

file: applicationContext-semanticLayer.xml
bean: slConfig
properties: saveTopicURIPatternList

Ref. Case #00028126

• Free Jaspersoft Tutorials

Video tutorials (iReport 3.5.x)

• iReport and TEIID Teiid is part of JBoss. It's a data virtualization system that allows applications to use data from multiple, heterogenous data stores. This demo shows a single report created in iReport accessing data in MySQL and Oracle.

Community provided tutorials

Tutorials in Spanish provided by Alfonso Blanco Criado about iReport 3.0 (old version)

1. Subinformes con iReport
2. Gráficos con iReport
3. Exportar PDF multiidioma con iReport
4. Informes con código HTML
5. Usar un DataSource XML para crear informes con iReport
6. Informes con fuente de datos ODBC

Tutorial in Brazilian Portuguese provided by Flávio Araújo about iReports 3.5.0 and NetBeans 6.5

• Gerando Relatórios Com JasperReports e iReports no Netbeans

The problem

[toc on_off::hide=1]

If you are on this page that probably means that you have implemented a custom query executor and that you may have an error like this doing your import from the Buildomatic (using the js-export.bat):

2012-06-25 06:26:28,761 ERROR BaseExportImportCommand:45 - com.jaspersoft.jasperserver.api.JSExceptionWrapper:

net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'XXX' language. com.jaspersoft.jasperserver.api.JSExceptionWrapper:

net.sf.jasperreports.engine.JRException: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'XXX' language. at

net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:247) at

net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:230) at

net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:218)

where XXX is the custom query language.

The Solution

Prior to run js-export.bat you need to add the customization in the Buildomatic's sub-folder conf_source/iePro so that the query executor language can be identified. It should also include jasperreports.properties where it needs to be configured to use soap query executor language.

Issue:

[toc on_off::hide=1]

If the Excel export layout does not align correctly, you can try changing the default properties.

The default properties are set to a more data centric view.

Resolution:

Try these properties for a more layout centric Excel export of a report.

<property name="net.sf.jasperreports.export.xls.collapse.row.span" value="false"></property>

<property name="net.sf.jasperreports.export.xls.create.custom.palette" value="true"></property>

<property name="net.sf.jasperreports.export.xls.detect.cell.type" value="true"></property>

<property name="net.sf.jasperreports.export.xls.font.size.fix.enabled" value="true"></property>

<property name="net.sf.jasperreports.export.xls.ignore.cell.background" value="false"></property>

<property name="net.sf.jasperreports.export.xls.ignore.cell.border" value="false"></property>

<property name="net.sf.jasperreports.export.xls.ignore.graphics" value="false"></property>

<property name="net.sf.jasperreports.export.xls.image.border.fix.enabled" value="true"></property>

<property name="net.sf.jasperreports.export.xls.remove.empty.space.between.columns" value="false"></property>

<property name="net.sf.jasperreports.export.xls.remove.empty.space.between.rows" value="false"></property>

<property name="net.sf.jasperreports.export.xls.white.page.background" value="true"> </property>

Ref. Case #00020803 -- 14:15, 1 September 2011 (UTC)