AVEVA PI Connector

The PI to PI (PI2PI) system extracts values from one or more PI systems in the source (BLUE) domain and stores those values on a designated PI system in the destination (RED) domain. It is designed to operate using the MetaDefender Security Gateway.

The PI2PI system also performs historical backfill. Historical backfill alleviates any gaps in archive data on the destination PI system.

Pi Collectives

OPSWAT NetWall PI Replication system supports Pi Collectives.

Two or more PI databases can be configured as a redundant set. This redundant set is called a Collective. The Collective is normally created in a specified domain, and each PI database is operating on a computer that is a member of that domain. Every collective has a Primary PI Database member, and one or more secondary PI Database members.

PI2PI

OPSWAT PI2PI-Blue Service

OPSWAT NetWall OSI-PI Service (BLUE) needs to be installed on each PI server of interest on the BLUE network. It operates as a Windows Service, configuration for the PI2PI system is done using the OPSWAT Web interface on Blue and the OPSWAT Web interface on Red. There is no user interface on the Windows machines. OPSWAT NetWall OSI-PI Service (BLUE) service can be loaded either on the PI server itself or on another Windows machine that has the PI SDK installed and has a trusted relationship with the PI Server. To correctly install it, follow the instructions:

  1. Double click on the msi file that OPSWAT will provide OPSWAT NetWall OSI-PI Service (BLUE) and click Next.
  2. Fill in the IP address and port for listening for the configuration and click Next. Tipically, this IP will be the IP of MetaDefender Security Gateway BLUE.
  3. Click finish button to exit the Setup.

MetaDefender Security Gateway BLUE

To configure OSIPI Connector, a security dongle should be inserted in the BLUE server.

  1. Login into MetaDefender Security Gateway BLUE.

  2. Go to OSIPI menu, select Pi to PI label, deploy Action button and select Add Client.

  3. Type values in the following boxes:

    1. Flanker IP: IP address of the Blue Windows Machine.
    2. Flanker Port Config: Port number the Blue Windows Machine is listening on for Config.
    3. Instance: The Interface Instance number to be used at red. Must be a positive integer.
    4. Backfill Max Records/sec: Max values per second to extract during backfill (range: 1000-20000).
    5. Backfill Slice (m): The number of minutes to read for each History Backfill retrieval (range: 1-60).
    6. Point Prepend: Prepend the string indicated here to each Pi point. The maximum length for the string is 20 chars (lowercase, uppercase, numbers, dash and undescore are allowed characters).
    7. Source Tag Select: Dropdown list where the user can select between Exact Tag Name, Instrument Tag, ExDesc and UserInt1.
    8. Backfill Time (HH): How far back in time to go for historical backfill (range: 0.5-168, values with more than two decimals will be rounded).
    9. Database Name : Windows Network Name of the PI server.
    10. User: PI Username (blank: use trusted connection).
    11. Password: PI Password (blank: use trusted connection).
    12. Debug Points: Points for debugging, separated by semicolon ';'. Maximum 10 points.
    13. Debug Mode: User can select the debug mode using this dropdown list. User can select between Disabled, All, Snapshot only and History only.
    14. Debug Detail: User can select the debug detail using this dropdown list. User can select between Count only and List History values.
    15. Point Sources: One or more PI point sources, separated with semicolon ';'.
    16. Point Filter Name: User can assign a Pi field to use for additional point filtering in BLUE. "None" means no filter.
    17. Point Table Refresh Rate: Rate in hours for transmitting the PI Point Table. Range is from 0.2 to 2.
    18. Schema Records per Second: Maximun number of Schema records to transmit per second (default value is 2000, range is from 1000 to 5000).
    19. Statistics Seconds: Statistics frequency in seconds. If the value is 0, no statistics are printed (range: 5-3600).
    20. Use Location1: If 'Yes' is selected, Location1 on Red must match Instance.
    21. Description: user-friendly description for the defined Client.

  4. Click on Submit button to save the changes.

OPSWAT PI2PI-Red Service

OPSWAT NetWall OSI-PI service (RED) needs to be installed on the PI server on the RED network. It operates as a Windows Service, configuration for the Pi2PI system is done using the OPSWAT Web interface on Blue and the OPSWAT Web interface on Red. There is no user interface on the Windows machines. OPSWAT NetWall OSI-PI service (RED) service can be loaded either on the PI server itself or on another Windows machine that has the PI SDK installed and has a trusted relationship with the PI Server. To correctly install it, follow the instructions:

  1. double click on the msi file that OPSWAT will provide OPSWAT NetWall OSI-PI Service (RED) and click Next.
  2. Fill in the IP address and port for listening for the configuration and click Next. Tipically, this IP will be the IP of MetaDefender Security Gateway RED.
  3. Click finish button to exit the Setup.

MetaDefender Security Gateway RED

To configure OSIPI Connector, a security dongle should be inserted in the RED server

  1. Login into MetaDefender Security Gateway RED.

  2. Go to OSI-PI menu and click on Edit button. Notice that only one OSIPI Client can be configured in MetaDefender Security Gateway RED.

  3. Type values in the following boxes:

    1. Flanker IP: IP address of the Windows Machine in the BLUE network acting as flanker.
    2. Flanker Port Config: Port number where the flanker defined will listen on for configuration.
    3. Flanker Port Data: Port number where the defined flanker will listen on for data transmission.
    4. Database Name: PI Server name within the Windows Network.
    5. User: PI username (leave it blank for using a trusted connection).
    6. Password: PI password (leave it blank for using a trusted connection).
    7. Point Sources: User can include here one or more Pi point souces seperated with semicolon.
    8. Debug Points: A maximum number of 10 debugging points can be configured including them in this field separated by semicolon ';'.
    9. Debug Mode: User can select the debug mode using this dropdown list. User can select between Disabled, All, Snapshot only and History only.
    10. Debug details: User can select the debug detail using this dropdown list. User can select between Count only and List History values.
    11. Statistics Seconds: Statistics frequency in seconds. If the value is 0, no statistics are displayed.
    12. Description: User-friendly description field for the created client.

  4. Click on Submit button to save the changes.

PI Database Replication

OPSWAT NetWall OSI-PI DB replication Service (BLUE)

OPSWAT NetWall OSI-PI DB replication service (BLUE) needs to be installed on each PI server of interest on the BLUE network. It operates as a Windows Service, configuration for the DB Replication system is done using the OPSWAT Web interface on Blue and the OPSWAT Web interface on Red. There is no user interface on the Windows machines. OPSWAT NetWall OSI-PI DB replication service (BLUE) service can be loaded either on the PI server itself or on another Windows machine that has the PI SDK installed and has a trusted relationship with the PI Server. To correctly install it, follow the instructions:

  1. Double click on the msi file that OPSWAT will provide OPSWAT NetWall OSI-PI replication Service (BLUE) and click Next.
  2. Fill in the IP address and port for listening for the configuration and click Next. Tipically, this IP will be the IP of MetaDefender Security Gateway BLUE.

MetaDefender Security Gateway BLUE

To configure OSIPI Connector, a security dongle should be inserted in the BLUE server.

  1. Login into MetaDefender Security Gateway BLUE.

  2. Go to OSIPI menu, select Pi Replication label, deploy Action button and select Add Client.

  3. Type values in the following boxes:

    1. Flanker IP: IP address of the Blue Windows Machine.
    2. Flanker Port Config: Port number the Blue Windows Machine is listening on for Config.
    3. Instance: The Interface Instance number to be used at red. Must be a positive integer.
    4. Backfill Max Records/sec: Max values per second to extract during backfill (range: 1000-20000).
    5. Backfill Slice (m): The number of minutes to read for each History Backfill retrieval (range: 1-60).
    6. Point Prepend: Prepend the string indicated here to each Pi point. The maximum length for the string is 20 chars (lowercase, uppercase, numbers, dash and undescore are allowed characters).
    7. Point Append: Append the string indicated here to each PI point. Maximum lenght is 20 characters. (lowercase, uppercase, numbers, dash and undescore are allowed characters).
    8. Backfill Time (HH): How far back in time to go for historical backfill (range: 0.5-168, values with more than two decimals will be rounded).
    9. Database Name : Windows Network Name of the PI server.
    10. User: PI Username (blank: use trusted connection).
    11. Password: PI Password (blank: use trusted connection).
    12. Debug Points: Points for debugging, separated by semicolon ';'. Maximum 10 points.
    13. Debug Mode: User can select the debug mode using this dropdown list. User can select between Disabled, All, Snapshot only and History only.
    14. Debug Detail: User can select the debug detail using this dropdown list. User can select between Count only and List History values.
    15. Point Sources: One or more PI point sources, separated with semicolon ';'.
    16. Point Filter Name: Allows filtering on attributes in addition to Point Sources.
    17. Point Table Refresh Rate: Rate in hours for transmitting the PI Point Table. Valid values are 0.2-2.
    18. Schema Records per Second: Maximum number of Schema records to transmitper second. Valid values are 1000-5000.
    19. Statistics Seconds: Statistics frequency in seconds. If the value is 0 no statistics are printed. Valid values are 5-3600, default value is 60 seconds.
    20. Enabled: This checkbox should be marked to enable OSIPI connector.

  4. Click on Submit button to save the changes.

OPSWAT NetWall OSI-PI PI DB replication Service (RED)

OPSWAT NetWall OSI-PI DB replication service (RED) needs to be installed on the PI server on the RED network. It operates as a Windows Service, configuration for the DB Replication system is done using the OPSWAT Web interface on Blue and the OPSWAT Web interface on Red. There is no user interface on the Windows machines. OPSWAT NetWall OSI-PI DB replication service (RED) service can be loaded either on the PI server itself or on another Windows machine that has the PI SDK installed and has a trusted relationship with the PI Server. To correctly install it, follow the instructions:

  1. double click on the msi file that OPSWAT will provide OPSWAT NetWall OSI-PI replication Service (RED) and click Next.
  2. Fill in the IP address and port for listening for the configuration and click Next. Tipically, this IP will be the IP of MetaDefender Security Gateway RED.
  3. Click finish button to exit the Setup.

MetaDefender Security Gateway RED

To configure OSIPI Connector, a security dongle should be inserted in the RED server

  1. Login into MetaDefender Security Gateway RED.

  2. Go to OSI-PI menu and click on Edit button. Notice that only one OSIPI Client can be configured in MetaDefender Security Gateway RED.

  3. Type values in the following boxes:

    1. Flanker IP: IP address of the Windows Machine in the BLUE network acting as flanker.
    2. Flanker Port Config: Port number where the flanker defined will listen on for configuration.
    3. Flanker Port Data: Port number where the defined flanker will listen on for data transmission.
    4. Database Name: PI Server name within the Windows Network.
    5. User: PI username (leave it blank for using a trusted connection).
    6. Password: PI password (leave it blank for using a trusted connection).
    7. Point Sources: User can include here one or more Pi point souces seperated with semicolon.
    8. Debug Points: A maximum number of 10 debugging points can be configured including them in this field separated by semicolon ';'.
    9. Debug Mode: User can select the debug mode using this dropdown list. User can select between Disabled, All, Snapshot only and History only.
    10. Debug details: User can select the debug detail using this dropdown list. User can select between Count only and List History values.
    11. Statistics Seconds: Statistics frequency in seconds. If the value is 0, no statistics are displayed.
    12. Description: User-friendly description field for the created client.
    13. Attribute Blocking: Identify one or more attributes that are not to be replicated on Red. This applies to all points.
    14. Security Attributes Sync: If the checkbox is checked, the security attributes will be synchronized and new options will be selectable in "Attibute Blocking" list. Please, notice that the groups/users should be identical on BLUE and RED PI servers.

  4. Click on Submit button to save the changes.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
Software Update
On This Page
AVEVA PI ConnectorPi CollectivesPI2PIOPSWAT PI2PI-Blue ServiceMetaDefender Security Gateway BLUEOPSWAT PI2PI-Red ServiceMetaDefender Security Gateway REDPI Database ReplicationOPSWAT NetWall OSI-PI DB replication Service (BLUE)MetaDefender Security Gateway BLUEOPSWAT NetWall OSI-PI PI DB replication Service (RED)MetaDefender Security Gateway RED