You should be aware of some problems that may occur with the exported
XML file from the Export Values view.
When exporting your business measures, you may find that the data
of the XML file is either inaccurate or incomplete. For example, the values
of business measures are zero, or the percentages of all paths in a process
are zero. Also, some tasks information in one or more exported process might
be missing.
Some causes for these problems that you will need to check.
- The process or the activity whose values you want to export has not been
executed so there is nothing to export.
- The process or the activity has started, but the data is not replicated
yet from the Runtime database to the Historical database (by default, every
24 hours). You will not see values until replication takes place.
- There was no activity of the process or task in the date range in which
you selected to export the file. The values of any business measure in this
date range would be inaccurate.
- You expected to see other data that you do not see. The factor that determines
what to be monitored is the Business Measures editor user
who creates business measures for the process elements to be monitored. For
example, only a subset of the tasks in a process could be monitored, while
the other set is not. Any process element that is not set to be monitored
(has no business measures) will have no data in the exported XML file.
- The process elements cannot be monitored through the WebSphere® Integration
Developer or
the Business Measures editor. They do not emit
events.
- The process failed or terminated before any tasks were executed.
- The process had some branches that were never executed.
In other cases, your exported XML file is zero size, indicating
an error has occurred. You will need to contact your Dashboard
Client administrator to check the log file on the WebSphere Portal Server
to diagnose and solve the error.