3.1.4.22 RenderReport

The RenderReport operation generates HTML markup for a specific report stored on the protocol server. The protocol client specifies which report is to be rendered, and other parameters that affect the result’s HTML content.

 <wsdl:operation name="RenderReport" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input wsam:Action="http://www.microsoft.com/performancepoint/scorecards/IBIMonitoringServiceApplication/RenderReport" message="tns:IBIMonitoringServiceApplication_RenderReport_InputMessage" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"/>
   <wsdl:output wsam:Action="http://www.microsoft.com/performancepoint/scorecards/IBIMonitoringServiceApplication/RenderReportResponse" message="tns:IBIMonitoringServiceApplication_RenderReport_OutputMessage" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"/>
   <wsdl:fault wsam:Action="http://www.microsoft.com/performancepoint/scorecards/IBIMonitoringServiceApplication/RenderReportBpmExceptionFault" name="BpmExceptionFault" message="tns:IBIMonitoringServiceApplication_RenderReport_BpmExceptionFault_FaultMessage" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"/>
 </wsdl:operation>

The protocol client MUST send an IBIMonitoringServiceApplication_RenderReport_InputMessage request message (section 3.1.4.22.1.1) and the protocol server MUST respond with an IBIMonitoringServiceApplication_RenderReport_OutputMessage response message (section 3.1.4.22.1.2) containing the HTML markup for the report.

Exceptions:

In case of any other failure, the ErrorCode MUST be one of the values specified in section 2.2.2.1.2. For a detailed specification of how exceptions are reported by the protocol server, see section 2.2.2.1.