PI Nexus+ / Reference
AF Server Settings
This reference lists the settings of AF servers and AF databases under Admin > AF Servers, the rules for scanning them, and the analysis recalculation permission.
Overview
This reference lists the settings of AF servers and AF databases under Admin > AF Servers, the rules for scanning them, and the analysis recalculation permission.
AF server row
| Column or action | Meaning |
|---|---|
| Select | Opens the server's AF Databases, Attribute Scanning and Analysis Settings tabs |
| Authentication, Version | Windows or OpenID Connect; AF server version from the last test |
| API Connecting As, AF User | Account the web application connected as; its AF user and AF identities |
| Last Test | OK or Failed with the message |
| Edit | Site (two or more sites) and Authentication mode. Moving the server moves its databases. A new mode clears the test result |
| Test, Enable / Disable, Purge Inventory | As for PI Data Archives. Enabling also discovers the server's databases |
AF database row
| Column or action | Meaning |
|---|---|
| Status | Enabled, Disabled, Error (last test failed) or Enabled - AF Server disabled (kept but not scanned) |
| Analysis Recalculation | Off or Allowed |
| Enable | Refused while the server is disabled. Tests the database first; a failed test leaves it disabled |
| Recalculation settings | Opens the permission dialog |
| Test, Disable, Purge Inventory | As for other targets |
Scan requests
An AF scan, health refresh or schedule that names an AF server runs once per enabled database of that server.
| Request | Result |
|---|---|
| Named AF server is not configured | Rejected; the message names the server |
| Named AF server is disabled | Rejected: enable the AF Server first |
| Enabled AF server with no enabled database | Rejected: enable at least one AF Database first |
The same check runs when a recurring schedule is saved.
Attribute Scanning: value evaluation mode
| Mode | Reads current values of | Skipped attributes |
|---|---|---|
| All attributes | Every scanned attribute | None |
| Operational attributes (default, Recommended) | Attributes with a data reference, including Configuration Items with one, and Manual Data Entry attributes | Attributes without a data reference, hidden and excluded attributes; shown as Not Evaluated |
| Inventory only | None | All; structure, analyses and dependencies are still inventoried |
The mode belongs to the AF server and never removes attributes from the inventory. A newly added server and a server upgraded from 1.4 get Operational attributes; later upgrades keep the chosen mode. When an attribute becomes skipped, the next successful scan sets it to Not Evaluated and clears its issue; a linked PI Point keeps its own health.
Analysis Settings
| Setting | Default | Range |
|---|---|---|
| Service Load Performance | On, 5 %, Warning | Threshold 0 to 100 %; severity Warning, Error or Info |
| Disabled or Stopped Analyses: Issue severity | Info | Ignored (no issue), Info, Warning, Error |
Disabled and stopped analyses keep their inventory and get no health verdict; their issue uses the severity above. Not-ready analyses always raise a Warning. Runtime counters are read for running analyses only. A runtime error ratio above 50 % makes an analysis Error; any captured error or skip makes it Warning.
Analysis recalculation permission
| Item | Value |
|---|---|
| Default | Off for every database |
| Set by | Admin, per database, in Recalculation settings |
| Requires to allow | Enabled database and server; the historical-write acknowledgement |
| Covers | Every analysis in the database, for manual runs, suggestions and scheduled plans |
| Does not | Queue work, enable analyses, change native automatic recalculation or PI security |
| Still checked per run | License, native PI rights, each analysis's eligibility |
Native rights to check before allowing it:
| Right | Holder |
|---|---|
| Permission to queue recalculations | The PI Nexus+ scanner service account |
| Write access to the output PI Points | The PI Analysis Service account |
Viewers can see runs and suggestions; Operators can start and retry them; only Admins can change the permission (see Roles and Permissions).
