PI Nexus+ / Installation and Administration
2. Deployment Components
PI Nexus+ installs a web application, a background scanner service, and supporting configuration files. The web application is used by administrators and operators. The scanner service performs inventory scans in the background. Both components use SQL Server to store configuration and scan results.
Overview
PI Nexus+ installs a web application, a background scanner service, and supporting configuration files. The web application is used by administrators and operators. The scanner service performs inventory scans in the background. Both components use SQL Server to store configuration and scan results.
| Component | Default | Purpose |
|---|---|---|
| IIS site | PI Nexus+ | Hosts the web UI and API |
| IIS URL | http://localhost:5139/ | Local web endpoint |
| IIS app pool | PINexusAppPool | Runtime identity for the web application |
| Windows service | PI Nexus+ Scanner | Runs background inventory scans |
| SQL database | PINexus | Stores configuration, inventory, scan history, health, issues, and dependencies |
| Install folder | C:\Program Files\Software Athlete\PI Nexus+ | Application files, scanner files, installer scripts, and admin scripts |
| ProgramData folder | C:\ProgramData\Software Athlete\PI Nexus+ | Bootstrap configuration, logs, and support diagnostics |
The IIS app pool and scanner service should run under the same PI Nexus+ service account unless the environment has a specific reason to separate them. Using one account makes SQL, PI, AF, and PI Vision permissions easier to review and troubleshoot.
2.1 Architecture Overview
PI Nexus+ is deployed as a separate application alongside the customer's PI System. It inventories the connected systems and stores normalized configuration, health, dependency, and change information in its own SQL database. It does not install components inside PI Data Archive, Asset Framework, or PI Vision.
The normal inventory connections are predominantly read-only:
- PI Data Archive: PI Nexus+ reads PI Point configuration, metadata, and values. When Interface Tracking is enabled, it also reads legacy PI Interface configuration from the PI Module Database. Changes are limited to explicitly enabled and confirmed Compression Tuning workflows.
- Asset Framework: PI Nexus+ reads AF databases, elements, templates, attributes, and analyses.
- PI Vision: PI Nexus+ reads display definitions, data-source references, and usage information from the PI Vision database, and provides links back to the original displays. It does not modify the PI Vision database.
- SQL Server: The separate PI Nexus+ database stores application configuration, inventory, health results, issues, dependencies, scan history, and background work state.
