## Reporting a problem or requesting a feature

If you are having trouble running JReport Enterprise Server or encounter any problems during reporting, take the following steps.

1. Check whether the system on which JReport Enterprise Server is running meets the system requirements.
2. Check the JReport FAQ pages for frequently-asked questions and their solutions.

If the problem persists, report it to Jinfonet Support (support@jinfonet.com) with the following information:

1. Describe the precise steps leading to the problem.
2. Run the batch file jrenv.bat in the `<install_root>\bin` subdirectory. Running this batch file will generate a file called report.env in the current directory. Send this file to Jinfonet Support. Also, describe the operating environment, including machine type, CPU, memory, OS, and Java version.
3. If you are running JReport in an integrated Java application server, click the Server Information button on the JReport Administration page to list the environment.
4. Send Jinfonet Support the log file with the recorded JReport Enterprise Server problems.
   - For a standalone server: Start JReport with the batch file DJREntServer.bat (.sh on UNIX). Running this batch file will record the most detailed logging information and write them to the log files in the `<install_root>\logs` directory. Try to reproduce the problem, and send the log files along with the other information.
   - For an integrated JReport Enterprise Server: If your JReport Enterprise Server runs as a servlet inside a Java application server, send the log files generated by the JReport Engine in the application server. When the JReport Servlet is installed, a property file is generated which is used to define the class and arguments of the JRServlet. For example, if you integrated JReport Enterprise Server into WebLogic, find the WebLogic properties file located in the installation path of WebLogic. Edit the file to use the option -vDebug -vError. Your file should then contain the following content:

     vError=true
     vDebug=true

     In addition, you can also directly add the java option -Dlogall=true (or -DvError=true, -DvDebug=true) to the java command line within the launch file of the application server.

     After restarting your application server, reproduce the problem and send the log files to Support.

5. Send Support the log files recording all of the logging information of engine and server (including event, error, debugging, access, management, and performance).
   - Change the configuration to record all logging events by starting the server and accessing the JReport Administration page through `http://localhost:8889`.
     1. Go to the Configuration > Logs tab.
     2. Set the trace level of all logs to TRIVIAL, and set the error level of all logs to WARN.
     3. After that, reproduce your problem and send Support the log files in `<install_root>\logs`. In addition, you can also directly modify the logging configuration file LogConfig.properties in `<install_root>\bin`. If you set the server property log.config.update to true (all server properties are managed within the file server.properties in `<install_root>\bin`), any changes to the configuration file will automatically take effect at runtime after the specified update interval (set by the server property log.config.update.interval).
   - If your JReport Enterprise Server runs as a servlet within a Java application server, in the address bar of a web browser, type in `http://<hostname>/jreport/admin`, where jreport is the servlet context path.
6. To reproduce your problem of running reports with JReport Enterprise Server, we will often need your report, catalog and data information.
   1. Send Support the catalog file (*.cat and *.fml) and the report set file *.cls that you are having problems with.
   2. In order to resolve technical issues that you have reported, we will need to access your report data so that we can recreate and analyze the problem. Your database may be very large. However, we will only require access to the data returned by the query of the troublesome report, and if necessary we will sign a confidentiality agreement with you. To extract the report data, in the Catalog Browser of JReport Designer, right-click the query that your report is using, select the menu item Create Cached Query Result. Then, input the data file name and click the Save button. The query result will then be saved in this file. Send Support all of the files generated (including the description file).