BIRT Reporting. \"Client HTTP GET method not implemented\" error.

[LIGO]

Hello,

I'm trying to make some BIRT reports with 3.14, and keep getting an error "SOAP-ENV: Client HTTP GET method not implemented" from reporting manager. That error is shown, when I'm trying to pass ip:port as URL (in DemoApplication, for example).
But everything works fine (data from my process is shown), when I open the report from the BIRT by the Run-View Report-In Web Viewer (ip 127.0.0.1 and some port like 58601).

I was trying to change port number in config, but no success.

Is there any solution for this problem?

[Andorhal]

Hello.

I would assume some kind of port communication issue.

For the Demo Application Birt Panel to run properly some things should be kept in mind:

• In Birt you can set the port of the preview Server: Window-> Preferences -> Report design -> Preview -> Preview Server (otherwise it will be changed with every start).
• In the WinCC OA config file you specify which port the Reporting Manager shall use (see product help)
• In the reporting template you have to tell birt where the data source is located (=the Reporting Manager IP/port).

When you have made the above (and the ports are matching) you can enter the Preview Server IP/port in the panel (and make sure your preview server is running by starting it once with the Run command inside Birt).
If you need to reset the preview Server IP/port combo pls do so at the (internal) _Reporting DP.

BR Robert

[LIGO]

Thank you very much, Robert, for pointing out on Preview Server.
I thought, WinCC OA Reporting manager is working as some kind of web-server (so it responsible for showing final report) and that was my main issue.
Today I tried a BIRT-runtime and tomcat, which worked out perfectly well for my task.

[Andorhal]

Glad you could work it out.

The Reporting Manager "only" acts as SOAP interface providing the WSDL to a client (BIRT, ...).
Birt in fact has a built in Webserver (Jetty), by running a report it is started an then displays the reports.

Birt Runtime and Tomcat is also our recommended setting to go for production.