Notes and restrictions

This chapter contains important notes and restrictions regarding the reporting feature:

Notes

Debug-Levels

The following debug levels are available for the Reporting Manager:

dbg 10 - Output of the whole data traffic

dbg 11 - Time stamps of request and response messages

dbg 12 - Information of new connections

Manager options

The Reporting Manager is started as a device manager. If several Reporting Managers should be started, the start options -num1, -num2 etc. must be specified.

If you want to filter by messages or managers to obtain debug information, use the option "device" for the Reporting Manager (e.g. -snd 2 -sndFilterMan "device 1").

System overview

The Reporting Manager is displayed as REPORTING in the "CTRL and other" table of the system overview.

Redundancy

Basically, no additional settings are necessary for redundant projects. Consider, however, the following notes regarding the two use cases:

  1. Remote Reporting Manager: In order to connect a remote Reporting Manager to a redundant system, use the config entry connectToRedundantHosts = 1. See also Configuration files for redundancy

  2. Reporting manager on both systems: Reporting Managers are not redundant. An HTTP request is always processed and answered by one Reporting Manager. Therefore, independent of a redundancy switch, the request is processed by the requested Reporting Manager regardless of whether the manager is active or passive.

Distributed Systems

No additional settings are necessary for distributed systems. Note that you have to specify the appropriate system name in addition to the data point name for data queries (e.g. Dist2:TestDP.value).

WSDL File

The Reporting Manager uses the Reporting.wsdl file of the installation directory <wincc_oa_path>/data/Reporting/ by default.

If a Reporting.wsdl file is located in the project directory, the Reporting Manager uses this file. If another directory is specified by using the config entry wsdlPath = <path>, the manager uses this file instead. However, the file must be called "Reporting.wsdl", otherwise the Reporting.wsdl file in the installation directory is used.

Use the config entry wsdlPath = <path>/<file name>.wsdlto specify another file name for the wsdl file.

If the specified file does not exist, the Reporting Manager uses the Reporting.wsdl from the installation directory.

Restrictions

Ports under Linux

The default port 443 can only be used by the user root under linux. Other users may not open a port <= 1024. Therefore, specify a port number >1024 by using the httpPort or httpsPort config entries in the [reporting] section. Otherwise the Reporting Manager will stop.

Data point lists

Only single DPE requests can be made using the functions provided . Therefore, you cannot query several data points by using the functions provided by the Reporting.wsdl file. Only one data point per data set can be queried.

ISO standard Projects

When the Reporting is used in an ISO standard project, the Cyrillic languages such as Russian and Chinese languages are not supported. Furthermore, the following characters cannot be shown:

§ , ´ , ° , ² , ³

Display Problem with the web browsers Safari and Firefox on iOS

If the web browsers Safari and Firefox are used with the Birt Runtime (4.5) via the Tomcat web server on iOS 9.0, the screens are displayed too big. To avoid this, use a report as PDF (via the parameter __format=pdf, see chapter Web view) or use the web browser Chrome.

queryRDBdirect

The usage of queryRDBdirect is not supported when using the Reporting Manager.