User Tools

Site Tools


iphist:index

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
iphist:index [2021/06/28 08:29] – [Archiving Model] suiphist:index [2022/08/29 12:05] (current) – [Licensing] su
Line 130: Line 130:
  
 ===== System Requirements ===== ===== System Requirements =====
 +
 +See [[app_store_connect:system_requirements|See App Store Connect System Requirements]].
 +
 +However, note the system requirements should be adjusted for the particular use-case of the historian. If you intend to support historization of large data volumes and intensive data queries, a more powerful spec is required. Please consult with the Intelligent Plant support team for detailed guidance.
 +
 +===== Configuration Best Practice =====
 +
 +Details to follow.
 +
  
  
Line 139: Line 148:
  
  
 +==== How to find your Machine ID ====
 +
 +It is necessary to know the Machine ID of your system for licensing to be completed. To find your Machine ID, you must first open App Store Connect and select "Configure Data Core"
 +
 +Go to your Data Sources and click "Details" on the historian that you wish to use.
 +
 +{{:app_store_connect:data_core_-_data_sources_selection.png?300|}} 
 +
 +{{:app_store_connect:data_core_-_details.png?500|}}
 +
 +Under Action, click "Configure Data Source Settings"
 +
 +{{:app_store_connect:data_core_-_configure_settings.png?300|}}
 +
 +And at the bottom you will see the Machine ID for your system. 
 +
 +{{:app_store_connect:data_core_-_machine_id.png?800|}}
 =====IPHist - IPHist replication===== =====IPHist - IPHist replication=====
  
 Connections can be setup in datacore to provide reslient transfer of historical data between IPHist instances. this means that a loss in connectivity will not result in a permanent loss of data on the remote IPHist to the datasource. that data will be back filled, and consistent. Connections can be setup in datacore to provide reslient transfer of historical data between IPHist instances. this means that a loss in connectivity will not result in a permanent loss of data on the remote IPHist to the datasource. that data will be back filled, and consistent.
  
-this can be configured by ..+For further information regarding replication and data resilience, contact support@intelligentplant.com.
  
 =====Other historian - IPHist replication, or vice-versa ===== =====Other historian - IPHist replication, or vice-versa =====
iphist/index.1624868982.txt.gz · Last modified: 2021/06/28 08:29 by su