[Performance] Diagnostic Tips

Elixir Repertoire Repertoire Server
1

Diagnostic Tips

 

List of actions that can be taken to debug issue encountered


Ask yourselves the following questions :

  1. Can the report be generated via Elixir Report Professional?
    • If No, please validate the template and datasource
    • If Yes, please proceed on to the next question

  2. Can the report be generated via Elixir Report Server's sample java application? (Located at $ERS_HOME/clients/demo/JavaClientApp)(Ensure that you are able to launch the sample java application, otherwise, please state that you are not able to launch it)
    • If Yes, please verify our calling application
    • If No, please verify
      1. if the necessary files, such as JDBC drivers are available
        (JDBC drivers should be place at folder of Elixir Report Server)

      2. if the job request is sent to Elixir Report Server
        (Job request message will be sent to Elixir Report Server, visible in server.log of directory:- $ELIXIR_REPORT_SERVER_HOME/logs/)

      3. if error message is logged in server.log of directory :- $ELIXIR_REPORT_SERVER_HOME/logs/
        • If Yes, please verify if
          1. you do encounter any error message when generating through your application and debug accordingly

          2. there is reaction upon clicking of button for report generation
            • If No, please verify if the web page is able to reference to the necessary files

          3. there is a request sent to the report server?
            Please check server.log of Elixir Report Server.
            If no job message, please verify the report server configuration

          4. is the report generated in cache folder?
            • If report generated with correct file size, please verify your cache configuration and cache path within your application
            • If report generated with incorrect file size, please verify if the necessary parameters are passed in correctly for report generation
            • If report is not generated, please verify if the report is generated to other directory
            • If report could be found in other directory, please modify our cache configuration and cache path with your your application.
        • If No,
          please send us the feedback to the above questions and
          report template, datasource file, sample data and calling application (if necessary)
          to replicate the issue.
List of things to take note such as to avoid such issue

  1. Practice good designing habits
  2. Standardize on naming convention for files
  3. Organization of files
  4. Keep files, JVM and products used in sync always
  5. Use repository path for reference to files (if possible) 
  * Example, Image URL : repository:/ReportSamples/images/logo.jpg
  * Instead of, Image URL : C:/ReportSamples/images/logo.jpg