Session timeout is set to 3 minutes. However, a keep alive ping is running every minute.
Latest version of OSR Designer 5 will always be available from the following link: https://portal.onestopreporting.com/reportdesigner/download
Can you please help define the purpose of the following records in the masterSettings table? Also, can you please let me know if the values should be adjusted. As an example, what does ServiceRunner.MaxConcurrentRenderingReports=2 mean? Does that mean we can only render 2 reports at once? What if we change this to 10 or 100 or 1000? Please help clarify the purpose of each.
These are the steps needed to render a report.
Execute: Analyzing the report, generate SQL, running SQL and transforming data into an abstract report model. This may be memory intensive within the service and CPU intensive on the database-server.
Rendering: Taking the abstract report model and transforming it into Excel-format. This may be memory intensive and CPU intensive.
Package Execute: Run execute and render steps (above) for all reports in a package and await the result. Can be set rather high since Execute and Rendering of reports will limit the number of executions anyway. This only starts that process.
Package Rendering: Package all reports from Package Execute into a new report (Excel) containing the result from all “sub reports”. This may be memory intensive but quite fast since it only smashing together pre-rendered reports.
ServiceRunner.MaxConcurrentRenderingReports – How many report renderings (i.e. Excel) will run in parallel
ExecuteService.MaxConcurrentJobs – How many executions (i.e. SQL) will run in parallel
ExecutePackageService.MaxConcurrentJobs – How many packages to execute in parallel (adds new executions and rendering jobs and await these jobs to finish)
RenderPackageService.MaxConcurrentJobs – How many packages to render in parallel (merge Excel documents into one).
It is possible (and recommended) to run several services due to stability (Azure never guarantee a machine to be up all the time) and scalability. Each service allows the parallelism set by the setting. So if you have one service and ExecuteService.MaxConcurrentJobs = 4 the service can run 4 jobs at the time. I you have two services running the service can run twice as many jobs at the time.
Setting these settings to 0 will cause the service check the value Environment.ProcessorCount on the server and use that value. There may be an upper limit on how many parallel jobs that’s run within a single service due to limitations within .NET threading handling. Its safe (from a threading point of view) to set these setting these settings high (like 1000), but it’s not sure .NET will start that many threads (parallel jobs). But setting these values very high might be a bad idea from a CPU/Memory starvation point of view. You have to do some tweaking and consider the size of the reports as well as the hardware you are running your reports and DW on. It is generally a better idea to scale with more services rather than setting these settings very high.
No, only outgoing vouchers are supported. This is because incoming vouchers are not available on the api from Visma.