Initial Installation Steps - PAS ICS Integrity - 7.3 - Installation & Upgrade - Intergraph

ICS Integrity Installation Guide

Language
English
Product
PAS ICS Integrity
Subproduct
ICS
Search by Category
Installation & Upgrade
PAS Version
7.3

Before you install Integrity, use the Readiness Checklist to make sure your systems are equipped with the hardware and software required for running Integrity. You should also understand how you will deploy Integrity in your environment.

Integrity is very flexible and can be deployed in many ways, depending on your network architecture, firewalls, and security policies. For more information about requirements and deployment options, see Completing the Readiness Checklist.

Actual system requirements are based on the number and types of assets included in the deployment.

The following steps allow you to plan for, install, and configure Integrity for the first time. These steps guide you through the remaining sections of this document.

  1. Verify all computers meet (or exceed) the requirements as stated in the Readiness Checklist for the version of software being installed. For more information, see Readiness Checklist.

  2. On each computer where you will install the Integrity Server or Integrity Data Collector, you can update the hosts file to include the IP address and host name for the SQL Server computer it will communicate with, if needed. For more information, see Adding the SQL Server Host Name and IP Address to the Hosts Files.

  3. On each computer where you will install one or more Integrity components, open the ports used by those components. For more information, see Open Ports Required by Integrity.

  4. Use the Ping command and Telnet to test communication between the computers where you will install Integrity components. For more information, see Testing Communication between Integrity Computers.

  5. If you want to ensure permissions are set as needed, create the folder where you will install Integrity on each computer and set the permissions on that folder. For more information, see Creating the Integrity Installation Folder.

  6. If you are upgrading an existing Integrity database, check that the existing database compatibility is set above SQL Server 2000 to the highest compatibility possible. For more information, see Checking the Compatibility Level in SQL Server.

  7. Verify that the Integrity Web servers have no underscores in the host name. If they do, rename the host. For more information, see http://support.microsoft.com/kb/909264.

  8. Ensure that both the Application and Web Server Roles and the associated services/features are added on the Integrity Servers. For more information, see Configuring Windows Web Server Roles and Features for Integrity.

  9. On the SQL Server computer, use SQL Server Management Studio for the following tasks:

    1. Make sure the person running the Integrity installation program has at least the dbcreator server role where the Integrity database will be created. If using multiple databases, this person must have at least the setup_admin server role. For more information, see Configuring Roles and Permissions in SQL Server.

    2. Disable CLR strict security. For more information, see Updating SQL Server CLR Strict Security and Cost Threshold Settings.

    3. Allocate the appropriate amount of memory to SQL Server: 75% of memory for systems with 24GB of RAM and above, or 50% if system RAM is below 24GB. For more information, see Performance Issues - Checking SQL Server Memory.

  10. PAS by Hexagon recommends that you turn off the Windows User Account Control (UAC) feature.

  11. Turn off the Windows Firewall (or alternatively, enable Notifications if the firewall blocks a program for all types of network, such as Public, Domain, or Work).

  12. If you need to save control maps, check that Visio is installed. Open a Visio file (*.vsd) and verify the software product is present, licensed, and activated. For more information, see Issues with Report Generation for PDF or Visio.

  13. Create a PAS folder in a root directory (for example, C:\ or D:\). Give permissions to the PAS folder and propagate to children (Network Service, IIS_IUSRS, Authenticated Users and any Application Accounts).

  14. Enable FILESTREAM (requires SQL Server 2008 or later). For more information, see FILESTREAM Configuration Recommendations and Enabling FILESTREAM.

  15. Install the Full-Text and Semantic Extractions for Search feature in SQL Server. This is an optional component of the SQL Server Database Engine. For more information, see Installing Full-Text Search for SQL Server.

  16. Make sure that IIS X-frame options are set to allow. For more information, see Setting IIS X-Frame-Options to Allow.

  17. Install Microsoft Excel 2010 or later on the web server if you want to run the hierarchical reports or if you use certain asset models.

    Some asset models, such as PAS Sensor Data Integrity or ABB Symphony Plus, require data imports from Excel files. See the individual asset model Implementation Guide to determine whether an individual model has this requirement to facilitate the transfer from Microsoft Excel, which may require Microsoft Access Database Engine (AccessDatabaseEngine.exe) on the data collector computers. The AccessDatabaseEngine.exe file is available in the following ways:

  18. Install Integrity on each computer where you need a component. For more information, see Installing Integrity for the First Time.

  19. Set the Admin Utility to run as administrator. For more information, see Setting Integrity Admin Utility to Always Run as an Administrator.

  20. Start the Integrity Admin Utility. For more information, see Using the Integrity Administration Utility.

  21. Validate your product license. For more information, see Validating Your License.

  22. Create the Integrity database. For more information, see Creating the Database.

  23. If you are using multiple databases, create the additional databases. For more information, see Configuring Multiple Databases. For more information about importing source assets using multiple databases, see Importing Asset Models Using Multiple Databases.

  24. Configure the virtual directory for the Integrity Web application. For more information, see Defining the Web Application (Integrity Web Interface).

  25. On the SQL Server computer, use SQL Server Management Studio to make sure the Integrity service accounts have the required permissions. Then, assign the accounts to the Integrity services. Since the IntegrityAppPool for the Integrity web interface uses the Network Service account by default, make sure the NT Authority\Network Service account has the appropriate roles for the Integrity database. For more information, see Defining Your Service Accounts.

  26. If you are installing ICS Integrity, import the PAS Cyber Integrity asset model and create an asset using this model to support the other ICS Integrity features you choose to use. For more information, see Setting Up the Asset for ICS Integrity Features.

  27. Import an asset model for one type of asset. Integrity provides many asset models. To make sure Integrity is correctly installed and configured, initially import one asset model and add an asset of that type. For more information, see Loading (Importing) an Asset Model.

  28. Add one or more assets for the imported asset model. For more information, see Adding an Asset (Data Owner).

  29. Run an import so you can view data for the added asset. You can select the Run Now option when scheduling an import to run the import immediately. For more information, see Scheduling Data Imports.

  30. Create SQL Server Maintenance Jobs per Application. For more information, see Setting Up SQL Server Maintenance Jobs.

This initial installation and configuration ensures your database and user interfaces are connected and you can view data for the initial asset model. You should now import additional asset models, add your remaining assets, schedule imports, and review security for service accounts. You can also configure the asset explorer tree and perform other maintenance tasks. For more information about Integrity administration and additional configuration, see the Integrity Administration Guide.