Page tree
Skip to end of metadata
Go to start of metadata
Problem Description

Saving or Displaying report in the Report Builder of ADG dashboard is very long.

Example:

  1. Login to Dashboard 
    1.     User: USR
    2.    Password: XXXX
  2. Go to Useful Links : Quick Access page : Report Builder Administration
  3. Create new report
  4. Create new section "FlexReport - Items" : this step is very long. It takes about  200 sec
  5. Define filter values
  6. Save report: this step is very long. It takes about  150 sec
  7. Display report : this step is very long. It takes about  400 sec
Applicable in CAST Version
Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
7.3.x(tick)
7.2.x(tick)
7.0.x(tick)
Action Plan
  1. Get the customer's input
  2. Check the query result
  3. If the  number and the complexity of used sections can explain the performance issue, come back to customer by explaining him the noraml behavior.
  4. If not,Get the customer's input to reproduce
  5. Reproduce the issue
  6. Transmit to the Dashboard team

Get the customer's input

  1. Get customer's expectation and justification
  2. The result of following query executed on central repository used for report generation.

Check the query result

The aim of section is identify the get the number and the complexity of sections used for the report generation. If the  number and the complexity of used sections can explain  the performance issue, come back to customer by explaining him the normal behavior.

If not, go to next steps

Get the customer's input to reproduce

  1. the user and password to connect to the dash board
  2. A dump of central repository
  3. the time requested by each long step reported by customer

Reproduce the issue

  1. Import the central site 
  2. Update the web.xml file of web server application as described here
  3. Restart application in tomcat
  4. Connect again to the dash board
  5. Create and save the report using same section(s) and parameter(s) as customer
  6. Display the generated report.
  7. Measure the time for long steps reported by customer: check the SQL trace and the queries times in the bottom of the dashboard page to get slowest queries

Transmit to the Dashboard team

In the Jira report, provide

  1.  The customer central
  2. The step by step scenario to create report by precising
    1. the user to connect to the dashboard
    2. the section(s) and parameter(s) used to create the report
  3. The time requested by each long step reported by customer: the time reported by customer and the time observed by support.
Notes / Comments


Related Pages


  • No labels