Working with Multiple Databases for Enterprise Deployments - PAS ICS Integrity - 7.3 - Administration & Configuration - Intergraph

ICS Integrity Administration Guide

Language
English
Product
PAS ICS Integrity
Subproduct
ICS
Search by Category
Administration & Configuration
PAS Version
7.3

Based on your deployment requirements, you can configure Integrity to work with multiple databases. How the databases work together depends on the type of deployment you select. For example, various levels within your organization may need to view Integrity information. While users at the site level are involved in day-to-day operations and change management of their local systems, the centralized engineering group may want to view consolidated information from multiple sites. If the amount of data permits, you can use data forwarding to make the data available both at the site level and at the corporate level. For more information, see Understanding Data Forwarding and Receiving.

In other deployments, multiple databases allow you to segment larger amounts of data and view the consolidated data as needed. Each site can have a secondary database, and the centralized engineering group can have the primary database to view information across the databases. To use multiple databases, an administrator uses the Admin Utility to create the primary database with the database ID set to 1. Next, the administrator creates one or more additional, secondary databases with unique database IDs. Then, the administrator configures Integrity to recognize these databases and to coordinate data requests for assets stored in secondary databases.

To make sure the Integrity services and utilities work properly with multiple databases, the pasIntegrityDB and IntegrityDataCollector2 services on the Integrity server for the primary database need to run using a domain account. This domain account allows the pasIntegrityDB service to see the assets in the secondary databases for multiple database services to perform correctly. You also need to modify the .config file for Integrity and each utility to identify the domain account you set up for the services to use. For more information, see Defining Your Service Accounts.

When you use multiple databases, some features may require additional configuration and considerations for the primary database. For more information, see Configuring Baselines with Multiple Databases.

  • If the password for the service account is changed in the future, you must also change the service configuration or the service will no longer work.

  • The names of the assets across all databases must be unique.

To configure multiple databases:

  1. Create one primary database using the Admin Utility and set the database ID to 1. Only one primary database can exist. For more information, see Creating a Database.

    admin-db-multiple-id

  2. Create one or more secondary databases using the Admin Utility and set the database ID for each secondary database to a value other than 1. For a secondary database, the database ID can be an integer value between 2 and 255, and the database ID must be unique.

  3. On the Integrity server for the primary database, which will be the web server, open the IntegrityMOCRoot.XML file in the folder where you installed Integrity, C:\Program Files (x86)\PAS\Integrity by default.

  4. Copy the <IMOCConnStr> line, and then paste and rename the line as <MainDB>, and shown in the following image.

    admin-db-maindb

  5. In each secondary database, import the needed asset models and create the assets for that database using unique names across all databases. Then, import the data for each asset in each database.

  6. Open Configuration Manager on the Integrity server for the primary database. To open Configuration Manager, run the following file:

    InstallPath\DataCollector\ConfigurationManager.exe

  7. Click Tools > Multiple Database Configuration.

    admin-db-distribute

  8. For each of the secondary databases, complete the following steps:

    1. Type the connection information for the secondary database, including server name, database name, authentication type, and login credentials.

    2. Click Test Connection to make sure the connection information is correct.

    3. Click Save.

  9. Click Apply. Then, click OK. Integrity adds the data owners from the secondary databases to the primary database data owner table.

  10. Close Configuration Manager.

  11. Identify a domain account to use for the pasIntegrityDB service, IntegrityDataCollector2 service, and the Integrity configuration utilities. For more information, see Defining Your Service Accounts.

  12. On the Integrity server for the primary database, configure the services to use the identified domain account by completing the following steps:

    1. Click Windows Start > Run.

    2. Type services.msc, and then click OK.

    3. Right-click the pasIntegrityDB service, and then click Properties.

    4. Click the Log On tab, and then select the This account option. Type the domain account user name and password.

      If the password for this account is changed in the future, you must also change this specified value or the service will no longer work.

    5. Click Apply, and then click OK.

    6. If the service is not running, click Start the service.

    7. Repeat these steps (a-f) for the IntegrityDataCollector2 service.

  13. Verify the pasIntegrityDB service has started correctly and is running by completing the following steps:

    1. Open the InstallPath\DataCollector\pasIntegrityDB.txt file, where InstallPath is the folder where you installed Integrity.

      If the pasIntegrityDB.txt file does not exist, the service never started.

    2. Verify no major errors exist.

  14. On the Integrity server for the primary database, specify the identified domain user account in the .config files for Integrity and its configuration utilities by completing the following steps:

    1. Use Notepad to edit the following files:

    • InstallPath\web.config

    • InstallPath\DataCollector\AdminUtility.exe.config

    • InstallPath\DataCollector\AMDK.exe.config

    • InstallPath\DataCollector\AssetModelBuilder.exe.config

    • InstallPath\DataCollector\IDC.exe.config

    • InstallPath\DataCollector\IntegrityDataCollector2.exe.config

    • InstallPath\DataCollector\WFSAlerts.exe.config

    1. Find the <userPrincipalName value="domain\username" /> tag in each file.

      admin-db-service

    2. Change domain to the domain name of the primary Integrity server and change username to the domain account name associated with the pasIntegrityDB and IntegrityDataCollector2 services.

    3. Save the files, and then close Notepad.

  15. Open Configuration Manager on the Integrity server for the primary database. To open Configuration Manager, run the following file:

    InstallPath\DataCollector\ConfigurationManager.exe

  16. Build the asset hierarchy so you can manage assets from secondary databases. You can drag and drop assets to Asset Explorer to define the hierarchy for Asset Explorer in the Integrity web interface, or you can use Microsoft Excel to specify your asset hierarchy, and then copy and paste that data to the object grid. For more information about defining your asset hierarchy, see Understanding and Defining Your Asset Hierarchy.

  • When using multiple databases, use Configuration Manager instead of the Admin Utility to define the asset hierarchy. Since the Admin Utility focuses on one database, the Asset Explorer Configuration window can be missing assets when using multiple databases. If you select Asset Explorer Configuration in the Admin Utility, your asset hierarchy may need to be rebuilt using Configuration Manager.

  • Certain core asset models need to be imported into specific databases to function correctly. For example, the Baselines asset model should be imported into the primary database. For more information, see Configuring Baselines with Multiple Databases.

  • The source asset models, such as PAS Recon or Honeywell EPKS, should be imported into the appropriate secondary databases, where needed. For more information, see the Implementation Guide for each source asset type.