Depending on the third-party software you use and the locales you support, you may also have to configure JasperReports Server and its host. The steps described in this section are necessary only under certain circumstances, such as if you plan to use a character encoding form that UTF-8 cannot handle.
To use a character encoding form other than UTF-8, you must configure JasperReports Server, your application server, and your database server.
Configuring JasperReports Server
To specify a different character encoding:
| 1. | Open the .../WEB-INF/applicationContext.xml file and locate the following bean. It's configured for UTF-8: |
| 2. | Change "UTF-8" to the encoding type your database server and application server use. For example: |
| 3. | Save the file. |
| 4. | Restart JasperReports Server. |
Configuring the Application Server and Database Server
If you want to use a character encoding other than UTF-8, you may need to configure the third party software that JasperReports Server relies on. For more information, refer to the documentation for your application server and database server. For Tomcat, you can specify a different character encoding by following steps similar to those described in Tomcat and UTF-8 Configuration.
Configuration for Localized Analysis Schemas
If you plan to use localized OLAP views, you must take additional steps to configure JasperReports Server.
To configure JasperReports Server for localized OLAP views:
Recommended Comments
There are no comments to display.