Reports

WinForms to Web PowerBuilder to .NET PowerBuilder to Java
Search…
Reports
This document describes the overall design of the reporting mechanism of modernized applications.
This document assumes knowledge of modernized application concepts such as DataManagerControl(TODO ADD LINK TO DATAMANAGER DOC). Also basic knowledge of concepts from the original platform is required.
Overview of report processing in the original platform
In PowerBuilder reports are DataWindows that are created for printing. Some kinds of DataWindows are usually used as reports (for example: Label, Composite) . However all other kinds of DataWindows (ex. FreeForm) could also be used as reports. The rendering process is performed in-process by the runtime environment..
In the modernized application the DataWindows are converted to DataManagers (TODO LINK TO DATAMANAGER DOC). DataManager classes are converted to C# , For example a simple DataManager looks like this:
1
[Mobilize.WebMap.Common.Attributes.Observable]
2
public partial class d_my_report
3
   : Mobilize.Web.DataManager, Mobilize.Web.IDataManager
4
{
5
​
6
   [Mobilize.WebMap.Common.Attributes.Intercepted]
7
   public Mobilize.Web.DmText name_t { get; set; }
8
​
9
   [Mobilize.WebMap.Common.Attributes.Intercepted]
10
   public Mobilize.Web.DmColumn _name { get; set; }
11
​
12
   ...
13
​
14
   public d_my_report()
15
   : base()
16
   {
17
      ...
18
      this.PrintSpecification.PrinterName = "";
19
      this.PrintSpecification.DocumentName = "";
20
      this.PrintSpecification.Orientation = Mobilize.Web.CaseExtensions.String("0");
21
      this.PrintSpecification.Margin.Left = 110;
22
      this.PrintSpecification.Margin.Right = 110;
23
      this.PrintSpecification.Margin.Top = 96;
24
      this.PrintSpecification.Margin.Bottom = 96;
25
      this.PrintSpecification.Paper.Source = 0;
26
      this.PrintSpecification.Paper.Size = 0;
27
      ...
28
      this.name_t = new Mobilize.Web.DmText();
29
      this.name_t.Band = Mobilize.Web.CaseExtensions.String("detail");
30
      this.name_t.Alignment = 1;
31
      this.name_t.Text = "Name:";
32
      this.name_t.Border = 0;
33
      this.name_t.Color = "33554432";
34
      this.name_t.X = 37;
35
      this.name_t.Y = 4;
36
      this.name_t.Height = 64;
37
      this.name_t.Width = 174;
38
      this.name_t.Name = Mobilize.Web.CaseExtensions.String("name_t");
39
      this.name_t.Visible = true;
40
      this.name_t.Font.FontFace = "Tahoma";
41
      this.name_t.Font.Height = -10;
42
      ...
43
      this.name_t.Background.Color = "536870912";
44
      this._name = new Mobilize.Web.DmColumn();
45
      this._name.Band = Mobilize.Web.CaseExtensions.String("detail");
46
...
47
      }
48
}
Copied!
DataManager instances are converted at runtime to the format used for rendering the report. The following sections describe the process of converting these objects to a PDF representation of the report.
Rendering in the target platform
A modernized application uses Microsoft SQL Server Reporting Services (henceforth referred as SRSS) reporting technology. This solution offers a lot of services for creating and interacting with reports. More information about this solution see MSDN What is SQL Server Reporting Services (SSRS)? .
The main way to use SRSS is to use a set server side web services. These services are used to render and store reports (more information see MSDN Report Server Web Service Methods ). Modernized applications do not use these webservices and do not require using the SRSS server side process. Instead of this, modernized applications use the ReportViewer ASP.NET control to convert a report definition and data to a PDF document . This ReportViewer control is provided by Microsoft WebForms ReportViewer Control .
Microsoft reporting services solution uses the Report Definition Language (henceforth referred as RDL) for defining reports. This language is specified here: Report Definition Language (SSRS) .
ReportWatcher service
Modernized applications target the .NET Core development and execution environment. This environment provides flexibility and performance features such as cross platform execution, flexible deployment, modern development tools,etc. More information can be found here https://docs.microsoft.com/en-us/dotnet/core/about .
Since .NET Core is a new implementation of the .NET environment, there is no binary compatibility with existing .NET assemblies. There are APIs defined in the full .NET Framework that are not compatible with .NET Core. This is true for Microsoft's ReportViewer.As described in the previous section, this is the component used to render report . This component depends on the ASP.NET WebForms infrastructure. Having a direct dependency in this control implies that the modernized application cannot take advantage of the .NET Core features. This is the reason of having an external service that take care of rendering the report. This service is called ReportWatcher.
The ReportWatcher service is a small webservice dedicated to render reports on modernized applications. It has a dependency on ReportViewer and the full .NET Framework. This service can be hosted on a server different from the one that runs the modernized application. When a report needs to be rendered, the modernized application invokes this web service with everything required to render the report (report definition and data) and returns a PDF .
More information how to configure or use this service is provided in the following sections.
Data Manager
Report Rendering in Modernized Code
Last modified 1yr ago
Copy link
Contents
Overview of report processing in the original platform
Rendering in the target platform
ReportWatcher service