Plant Integrations Installation
The Plant Integrations module enables connectivity between TrendMiner and on-premise data sources. It supports two hosting models: WebHost (hosted in IIS) and AppHost (self-hosted).
WebHost (IIS-hosted)
This is the traditional hosting model where the application runs under Internet Information Services (IIS). Choose this deployment model if you already use IIS and prefer centralized management of web applications. WebHost handles many aspects of configuration and security automatically, making it easier to maintain for most users. For more information, visit Plant Integrations - Web-Hosted (IIS).
AppHost (self-hosted)
With the latest updates to the Plant Integrations, we are introducing a self-hosted (AppHost) deployment option alongside the traditional IIS-hosted (WebHost) model. This transition is part of our ongoing effort to reduce external dependencies, simplify upgrade processes, and improve long-term maintainability.
Why move to AppHost?
The self-hosted model offers several advantages:
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.
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).
However, the current version of AppHost comes with certain limitations. It's not possible to:
Change the network port where tm-plant-integration is running
Configure TLS to enable HTTPS
Configure Basic Authentication
Install multiple instances of tm-plant-integrations on the same machine
Important
If your environment requires any of the above features,WebHost may be the more suitable option.