Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 75:use_reports [2020/09/23 14:23] – cgl | 75:use_reports [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ===== Run a Report ===== | ===== Run a Report ===== | ||
| - | All available reports can be found at <font inherit/ | + | All available reports can be found at Reports. |
| Reports are global. Besides Administrative reports, reports usually analyze the content of the user's current workspace or the sub-workspaces. | Reports are global. Besides Administrative reports, reports usually analyze the content of the user's current workspace or the sub-workspaces. | ||
| Line 32: | Line 32: | ||
| {{https:// | {{https:// | ||
| - | |||
| - | ===== Troubleshooting ===== | ||
| - | |||
| - | If Stages is accessed through a proxy server, in some cases there can be connectivity problems for reporting requests (report execution, parameters loading and script upload fails). When these problems cannot be resolved otherwise, the following workaround can be used: | ||
| - | |||
| - | 1.) Add the following property to config.xml with an url of the Stages server (host name or ip address) which is accessible for internal request from the Stages server to itself:< | ||
| - | |||
| - | < | ||
| - | |||
| - | </ | ||
| - | |||
| - | 2.) Configure the proxyName and proxyPort of your proxy server for the internal connector in tomcat/ | ||
| - | |||
| - | < | ||
| - | < | ||
| - | proxyName=" | ||
| - | proxyPort=" | ||
| - | ..../> | ||
| - | |||
| - | </ | ||