Report Template

2022-12-16T00:57:40Z

Kenric: /* Loading & Saving */

2022-08-18T07:41:36Z

Kenric:

WebStyles are closely associated with WebTemplates, providing a means by which one can apply stylesheets to their pages. Using this system allows for a consistent styling across pages (or a subset of pages), since they would all speak to a certain WebStyle. Note also that despite being intended for CSS styling, they can contain any data, meaning the system could be used for other types of documents.

== Fields ==
=== Code ===
The Code field is the unique identifier by which a given WebStyle is accessed. This should be somewhat descriptive, since it must be referenced via other pages, but it is recommended to keep it short and sweet.

=== Description ===
An arbitrary field by which one can give a description for the WebStyle. It is non-functional, but provides a reference on top of the code for humans to identify the purpose or contents of the WebStyle.

== How To Use ==
Once you have created a [[PRS/WebTemplate|WebTemplate]], you can pull in stylesheets through the WebDatabaseInterface class. Simply call <code>WebDatabaseInterface.GetStylesheet(code)</code>, which returns an object of type <code>WebStyle</code>. This class has an attribute named <code>Style</code>, which contains the raw text from the WebStyle. Thus, to load and apply a style, put this markup in the <code><head></code> tag of your template:
<pre>
<style> @(WebDatabaseInterface.GetStylesheet("EXAMPLE").Style) </style>
</pre>

=== Loading Multiple Stylesheets ===
Since each call to <code>GetStylesheet</code> results in a request to the database, it can be beneficial to load multiple stylesheets at once. This is made possible with the <code>GetStylesheets</code> function, as demonstrated:
<pre>
Dictionary<string, WebStyle> styles = WebDatabaseInterface.GetStylesheets("FIRST", "SECOND");
<style>
@(styles["FIRST"].Style)
@(styles["SECOND"].Style)
</style>
</pre>

2022-06-21T08:22:17Z

Kenric:

[[File:PRS Database Service Account Settings.png|none|thumb]]
The PRS database service is the engine room of PRS, providing access to one or more PRS databases. In most cases, only one main database is required - however, there may be circumstances (for instance, multiple divisions or companies using the same infrastructure) where more than one database service may be running at the same time.

To add a database service, click the "Add Service" button at the bottom right of the screen, and select "Database":
[[File:PRS Add Database.png|none|thumb]]
The Database Properties screen will appear, allowing you to customise the service as required:
[[File:PRS Database Service General Settings.png|none|thumb]]

* The "Name" field provides a description of the database, which can be automatically provided to clients if the AutoDiscovery Service is enabled

* The "File Name" filed indicates the location of the (not-yet-created) database itself - click the "Select" button at the right to choose a location and file name for the database. If you have an existing database file, you can select this here to use the existing data - it will not be overwritten or erased.
* The "Port" field indicates the TCP port that the database service will listen on for client requests. This port should be configured to allow traffic through any firewalls you may have installed.

To ensure that the service can be validly installed on your system, click on the "Account" tab, and enter the Domain, User name and Password for an account that has privileges to install services on your system:
[[File:PRS Database Server Account Details.png|none|thumb]]
(If you are using a local account, use "." as the Domain Name)

At this point you should see the Database Service appear in the list of available services:
[[File:PRS Database Service Status.png|none|thumb]]
The "Disk" image at the left indicates that this service is a Database.

The "Pause" image indicates that the service currently stopped - click this will start the service, after which the image will change to a "tick":
[[File:PRS Database Service - Running.png|none|thumb]]
Once the service is running, a "target" indicator will appear in the right-hand column - clicking this will display a debug console to allow you to monitor service activity:
[[File:PRS Database Console.png|none|thumb]]
Since this log is reset when the debug console is closed, a full log can be found in a log file which is saved to the "Local System" service account's AppData folder. On 64-bit Windows, this can be found under the "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\PRSServer\PRSDatabase" folder as a ".log" file.

Once the service is successfully running, you can move on to adding and configuring additional services as required:

* Add an [[AutoDiscovery Service|Auto Discovery Service]] to allow client workstations to automatically find and connect to this database
*Add a [[GPS Gateway Service]] to capture incoming GPS data from Digital Matter IoT devices
*Add a [[Scheduling Service|Scheduler Service]] to perform regular actions on you database
*

Database Service

2022-06-21T08:20:18Z

Kenric:

[[File:PRS Database Service Account Settings.png|none|thumb]]
The PRS database service is the engine room of PRS, providing access to one or more PRS databases. In most cases, only one main database is required - however, there may be circumstances (for instance, multiple divisions or companies using the same infrastructure) where more than one database service may be running at the same time.

To add a database service, click the "Add Service" button at the bottom right of the screen, and select "Database":
[[File:PRS Add Database.png|none|thumb]]
The Database Properties screen will appear, allowing you to customise the service as required:
[[File:PRS Database Service General Settings.png|none|thumb]]

* The "Name" field provides a description of the database, which can be automatically provided to clients if the AutoDiscovery Service is enabled

* The "File Name" filed indicates the location of the (not-yet-created) database itself - click the "Select" button at the right to choose a location and file name for the database. If you have an existing database file, you can select this here to use the existing data - it will not be overwritten or erased.
* The "Port" field indicates the TCP port that the database service will listen on for client requests. This port should be configured to allow traffic through any firewalls you may have installed.

To ensure that the service can be validly installed on your system, click on the "Account" tab, and enter the Domain, User name and Password for an account that has privileges to install services on your system:
[[File:PRS Database Server Account Details.png|none|thumb]]
(If you are using a local account, use "." as the Domain Name)

At this point you should see the Database Service appear in the list of available services:
[[File:PRS Database Service Status.png|none|thumb]]
The "Disk" image at the left indicates that this service is a Database.

The "Pause" image indicates that the service currently stopped - click this will start the service, after which the image will change to a "tick":
[[File:PRS Database Service - Running.png|none|thumb]]
Once the service is running, a "target" indicator will appear in the right-hand column - clicking this will display a debug console to allow you to monitor service activity:
[[File:PRS Database Console.png|none|thumb]]
This log file is saved to the "Local System" service account's AppData folder, which on 64-bit Windows can be found in the "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\PRSServer\PRSDatabase" folder as a ".log" file.

Once the service is successfully running, you can move on to adding and configuring additional services as required:

* Add an [[AutoDiscovery Service|Auto Discovery Service]] to allow client workstations to automatically find and connect to this database
*Add a [[GPS Gateway Service]] to capture incoming GPS data from Digital Matter IoT devices
*Add a [[Scheduling Service|Scheduler Service]] to perform regular actions on you database
*