Proceedings of SerbiaTrib '13

2.1 The life cycle of the reportThe life cycle of the report is the events or theactivities of the report, start from the moment whenwe start creating it. In the Figure 4 we can see thatthe life cycle is made of Authoring, Managementand Delivery phases [1].requests and sends them to an application thatshould answer to these requests. As a part of theconfiguration of the Reporting Services, it must besaid that URL address report server i ReportManager. Reporting Services Windows service hasthree server applications: Report Manager, ReportServer Web Service and Background Processor.Behind the scene, this service in fact creates threenet applications which will host them.Figure 4. Work with the reportIn the Authoring phase, the author of the reportuses one of the Microsoft designer reports (ReportBuilder). When the report is completed, the authorcan upload it so it can be seen by the final users. Inthe Management phase, the administratorconfigurates the generated reports and developingsurrounding where it is going to be shown. Theadministrator can use Report Manager to organisethe report in the folders as well as to set the securitymeasures so that the access can be authorised to theusers. When it is configurated, the reports can beseen to only those to whom this right is authorised.The report can be seen by the final users typingURL address in the web searcher or alternatevilyusing the option schedule -through some channallike an e-mail.The designers of the report are the tools whichthe authors use for the definition of the data looks atthe moment of creating the reports. Since thetechnological knowledge and the experiences of theauthors can vary, it is not easy to create a designerreport that can satisfy the need of the all users.In theFigure 5 allthe designer tools for the creating of thereport are shown with their basic characteristics [2].Figure 5. Tools for creating the reports and theircomparisonIt is important to say that all mentioned reportdesigners support RDL standard (Report DefinitionLanguage).2.2 Physical architecture of Reporting ServiceIn the Figure 6 we can see the physicalarchitecture of the Reporting Services, which ismade of three Report Server aplications: ReportManager, Report Server Web Service andBackground Processor. In the physical architecturewe can see an implemented network interfacewhich includes Service Network Interfaces (SNI)which checks new requests HTTP.SYS.HTTP.SYS je HTTP driver which accepts theFigure 6. Reporting Services 2008 architectureReport Manager is an ASP.NET web applicationwhich enables management and the look into theabilities of the Reporting Services instanceconfigurated in the natural code. We can see ReportManager as a client application configurated withthe report of the server. Thanks to the same hostingmodel, configuration adjustments of the ReportManager and Report Server Web service are kept inthe same configuration file in rs report server.confingDue to this, Report Manager can add somenew extensions. For example, if the user developsnew extension, using C# or VB.NET we canconfigurate in the Report Managers a web controland later use it as we adjust the details of the report.Report Server Web service processes the reportsby using the systems on-demand. When the userclicks on the link pages where the reports are,he\she sends the requests to the Report Web,service accepts this request, processes this requestand returns the report to the client. To make iteasier integrations with the different types of thereports, Report Server Web service enables the useof URL and SOAP protocol and their integrationoptions.Background Processor is an application whichjob is to accept all the tasks which are in anunmarked mode. For example, when the descriptionof the event is accepted, Background Processorinterprets the description of the report and sends itto the final destination. Basically, its job is to13 th International Conference on Tribology – Serbiatrib’13 403