AVEVA System Platform: SeQent Integration Requirements

1. Determining the Install Machine

System Platform is inherently distributed, so FPAMGWSP does not need to be installed on a specific Windows host.

2. Abbreviations & Definitions

3. Environment Requirements

Prepare the environment for FPAMGWSP implementation:

1. Add a Platform node to the ArchestrA IDE when setting up a new VM, or locate the existing Platform node when using an existing VM to host FPAMGWSP.
   1. Enable the InTouch alarm provider, and confirm this setting for the appropriate node.
   2. If Register using “Galaxy <Galaxy name>” instead of “Galaxy” is checked, note this for configuring FPAMGWSP.
   3. Confirm Alarm Areas is blank or supports the desired lists of alarms to be monitored. This setting limits which alarms FPAMGWSP can monitor.
   4. Deploy from the IDE (if required).
2. Confirm that any managed InTouch instance alarms exist in ArchestrA IDE. Use the InTouch Application Manager to check whether the InTouch project is configured as Managed or Standalone.
3. Install runtime files: Application Server Bootstrap.
   • For testing, installing the InTouch Runtime is recommended so you can run a view and confirm dataflow.
   • No AVEVA license is required if setting this up on a new VM host.

Gateway selection: Standalone InTouch projects require SeQent’s FirstPAGE Alarm Manager Gateway for InTouch. Managed InTouch instances where alarms exist in Window Maker (Tag Database) also require the FPAM Gateway for InTouch. Managed InTouch instances where alarms exist in both ArchestrA IDE and Window Maker (Tag Database) require both the FPAM Gateway for System Platform and the FPAM Gateway for InTouch.

4. SeQent Software Requirements

Prepare the following details for configuring FPAMGWSP.

4.1 Create the DSN to the Alarm Database SQL Server

1. Create the DSN connection to the Configuration DB, typically on the Galaxy Repository, which shares the same name as the Galaxy.
2. During DSN creation:
   • If using With Windows NT authentication using the network login ID, no username and password are required.
   • If using With SQL Server authentication, enter a valid username and password for a SQL user with read access to the Galaxy database.
3. Set the default database to the database that shares the same name as the Galaxy.

Note: Connect to the Galaxy configuration database, not Alarm2DB (historical).

4.2 Check the SQL Server Authentication Mode

Check the authentication mode of the System Platform SQL Server instance, then follow the matching steps.

Windows Authentication Mode

1. Select With Windows NT authentication using the network login ID when creating the DSN.
2. After install, you must change the FPAMGWSP service logon account (default: system):
   • Ensure the pop-up verifying the user account appears.
   • Ensure the logon account has write privileges on the local machine (required for SeQent software logging).
3. To locate an appropriate user, open Computer Management > Local Users and Groups > Groups, select aaAdministrators, and review its members.

SQL Server and Windows Authentication Mode

1. Select With SQL Server authentication when creating the DSN.
2. You may need to create a SQL Server user account with db_owner privileges for the Galaxy database.

Why db_owner: db_owner is required to execute stored procedures.

4.3 Enable TCP/IP in SQL Server Configuration Manager

In SQL Server Configuration Manager, confirm the following is set:

SQL Server Network Configuration > Protocols for MSSQLSERVER > TCP/IP = Enabled

4.4 Select the DSN in FPAMGWSP

During configuration of FPAMGWSP, browse to select the DSN you created. The Galaxy name should auto-populate.