Documentation PI Nexus+ Documentation

PI Nexus+ / Installation and Administration

Installation and Administration

Install, configure, secure, operate, and maintain PI Nexus+ in a PI System environment.

Overview

Software Athlete

Version: 1.4.3.0

Vendor: Software Athlete GmbH

This guide is for Windows, SQL Server, and PI System administrators who install and configure PI Nexus+.

PI Nexus+ inventories PI Data Archive tags, Asset Framework databases, AF attributes, AF analyses, and PI Vision displays. It stores inventory, scan history, health results, and dependency information in SQL Server so administrators can search the PI System, review health issues, and trace dependencies between PI Vision, AF, analyses, attributes, and PI Points.

Articles in this category

28 articles
1. Installation FlowInstall PI Nexus+ in the order shown below. The order matters because later steps depend on the service account, SQL permissions, and runtime identities being correct.2. Deployment ComponentsPI 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.3. Prepare the ServerInstall PI Nexus+ on a Windows Server that has network access to the systems it will inventory. The server does not need to be a PI Server, AF Server, or SQL Server, but it must be able to reach those systems.4. Prepare the Service AccountPI Nexus+ needs a Windows account for the PINexusAppPool IIS application pool and the PI Nexus+ Scanner Windows service. This account should also receive the required SQL database permissions and PI System read permissions.5. Prepare SQL Server AccessPI Nexus+ stores all application configuration and inventory results in SQL Server. Before installation, decide which SQL Server instance will host the PI Nexus+ database and which Windows account will perform the database setup step.6. Run the InstallerInstaller file:7. Run Database SetupWhen the installer finishes, it opens the PI Nexus+ database setup window if Run PI Nexus+ Database Setup now was left checked.8. Verify Runtime IdentitiesAfter installation and database setup, verify that Windows is actually running PI Nexus+ under the intended service account. This is important because the installer can complete with fallback identities if Windows rejects the supplied service account. The application may open with a fallback identity, but SQL, PI, AF, or PI Vision access can fail until the correct identity is assigned.9. Open the Web UIOpen the PI Nexus+ web UI after the database setup and runtime identity checks are complete.10. Install the LicensePI Nexus+ requires a valid license before inventory features are available. Install the license before configuring scans so the application can validate the environment against the licensed validity period, tag limit, and server bindings.11. Configure Inventory TargetsInventory targets control scan scope:12. Deployment ReadinessDeployment Readiness is a pre-flight check for the PI Nexus+ installation. It is designed to catch common first-scan problems before a scan is started.13. Recommended First RunRun scoped scans before the first full scan. Scoped scans validate permissions, target configuration, and scan behavior with less runtime and less noise.14. Manual ScansManual scans are started from the Scanning page. Use manual scans during installation, validation, and troubleshooting.15. Scan SchedulesScan schedules run inventory scans automatically. Use them after the first scoped scans and first full scan have succeeded.16. Inventory PagesInventory pages show the latest active inventory from successful scans. Use these pages to review health, search for objects, and open detail dialogs.17. Dependency GraphsDependency graphs help trace relationships between PI Vision displays, AF attributes, AF analyses, and PI Points. They are useful when investigating why an object is unhealthy or where a tag or attribute is used.18. PI Vision Ad Hoc Workspace LinksPI Nexus+ can open PI Points and AF Attributes in PI Vision Ad Hoc Workspace. This is useful when an administrator sees a stale, bad, or out-of-range value and wants to quickly inspect the trend in PI Vision.19. Support and DiagnosticsSupport and Diagnostics provides logs, temporary debug logging, readiness information, and support bundle generation. Use this area when troubleshooting installation, scans, permissions, or performance.20. Inventory MaintenanceInventory Maintenance is used for recovery and support. These actions affect stored inventory data, so use them deliberately.21. SQL Admin UIAdmin > SQL is used to review and apply SQL bootstrap and schema settings from the web UI.22. Schema MigrationsSchema migrations update the PI Nexus+ database structure to match the installed application version. PI Nexus+ requires a compatible schema before scans can run.23. Upgrades and RepairUse the installer to upgrade or repair PI Nexus+. Always verify SQL status and runtime identities after an upgrade or repair because Windows Installer can reapply service and IIS configuration.24. UninstallUse Windows Apps and Features to uninstall PI Nexus+. Uninstall removes installed application files and installed services, but it does not automatically remove the SQL database or all ProgramData diagnostics.25. TroubleshootingUse this section when installation, login, discovery, or scans fail. Start with the UI error, then check the web application or scanner logs in ProgramData for the full exception.26. Installation ChecklistUse this checklist before handing the system to users or scheduling recurring scans.27. Important PathsUse these paths when troubleshooting or when support asks for logs and configuration files.28. Support Information to CollectWhen requesting support, collect enough information to identify the installation, the runtime identities, and the failing operation.