Plant Integrations Installation
The Plant Integrations module enables connectivity between TrendMiner and on-premise data sources. It supports two hosting models: AppHost (self-hosted) and WebHost (hosted in IIS).
AppHost (self-hosted) - Recommended
The AppHost model runs Plant Integrations as standalone Windows Services without requiring IIS. Endpoint configuration, HTTPS, and Basic Authentication are managed through a dedicated Configurator tool.
Choose AppHost if you want:
Fewer dependencies: No need for IIS, reducing system complexity.
Simplified upgrades: Updates are easier to manage without IIS-specific configurations.
Improved maintainability: Decoupling application data from binaries makes the system more modular and easier to troubleshoot.
Minimal impact on the historian: The new architecture is designed to isolate changes and reduce disruptions to data collection and storage.
Centralized configuration: All settings are managed through the Plant Integrations Configurator tool — no need to manually edit configuration files.
For more information, please refer to the following resources: Installing a self-hosted Plant Integrations and Migrating Plant Integrations from WebHost (IIS) to AppHost (self-hosted)
WebHost (IIS-hosted)
The WebHost model runs Plant Integrations as a web application under Internet Information Services (IIS). IIS manages hosting, HTTPS, authentication, and allows running multiple Plant Integrations instances on the same machine using separate IIS sites.
For more information, visit Plant Integrations - Web-Hosted (IIS).
Feature comparison
WebHost (IIS) | AppHost (self-hosted) | |
|---|---|---|
IIS required | Yes | No |
HTTPS/TLS | Configured via IIS | Configured via Configurator |
Basic Authentication | Configured via IIS | Configured via Configurator |
Custom port | Configured via IIS | Configured via Configurator |
Firewall rules | Manual | Automatic |
Multiple instances per machine | Supported | Not out-of-the-box, manual installation possible |