Installation of Master Core

Prerequisites

These pre-requisites are necessary for the successful deployment of the AspenTech Inmation solution.

# Procedure Expected Result

1

Confirm hostname for this deployment

D-GXPC-Core

2

Log into the server, where the Master Core is to be installed with an administrative account (domain user) using a Remote Desktop console session.

In CMD Shell, type:

MSTSC /v:D-GXPC-Core

Execute this command by pressing Enter.

Successful login on machine with administrative account.

3

Open the Start Menu and type Explorer

Open File Explorer by pressing Enter.

Check the file contents of the folder D:\installation.

Installation Files

The following files exist in D:\installation

  • AspenTechInmationNodeSetup.exe

  • AspenTechInmationSetup.exe

  • install.ps1

  • mongodb-windows-x86_64-5.0.x-signed.msi

  • Setup.xml

4

Ensure the security on the files is "Unblocked" by right-clicking on each file, selecting properties and checking the status of security as shown below. (Unblocking, where required, will ensure the setup can run without manual intervention)

Unblock File

Files are unblocked and run without intervention.

5

Ensure that the Setup.xml contains the right settings for the following parameters. Edit and save if necessary.

These parameters define the requirements for the instance type being installed (in this case a Master Core) and will not change between installations on any deployment.

The parameter CoreProfileEnableLogin in the Setup.xml file must be set to '1' to be able to login to Data Studio. In general, this property is optional but it is required if testing using Data Studio.

xml file settings are as below:

InstallCore

1

InstallDataStudio

1

IntegrateMongoDB

1

OfflineInstallMongoDb

1

LocationMongoDb

D:\installation

InstallWebApi

0

InstallOpcComponents

0

InstallRelay

0

InstallConnector

0

InstallServer

0

ConfigureFirewall

1

6

Depending on the server environment (D\Q\P) and its configuration specification, the parameters below might be different from one server to another.

If required, consult the Design Specification/Configuration Specification (DS/CS) document and edit the following settings in the Setup.xml file.

InstanceName

InstallationFolder

CorePort

OverrideObjectName

ProductKey

EnableAuditTrail

CoreProfileName

CoreProfileEnableLogin

CoreSystemOwner

IsCoreSystemOwnerGroup

MongoDbUserName

CreateISA95Object

ISA95ObjectParent

ISA95ID

ISA95Description

ISA95ObjectType

CreateKPIObject

KPIObjectParent

KPIObjectName

KPIObjectDescription

KPIObjectType

CreateMsiObjects

MsiVersion

MsiSystemId

CreateSecurityPerimeter

AdName

AdPrefix

EmgUser

EmgAdName

EmgUserDescription

Install Master Core

The Master Core solution should be simple using a dedicated script that installs the software with the settings as defined in the Setup.xml. The script execution should not require any user interaction (aside from that to execute the script).

# Procedure Expected Result

1

On the Master Core server, open File Explorer and browse to the installation directory used in Prerequisites step #3 (e.g. D:\installation)

Folder contains 5 files as shown in pre-requisites.

2

In File Explorer, go to File  Open Windows Powershell  Open Windows Powershell as administrator.

Start PowerShell

PowerShell with administrative privileges is opened.

3

Execute the command to run the installation script by typing

.\install.ps1
Start Install

The script starts, executes without user intervention, and ends successfully.

4

Copy autogenerated passwords to the clipboard.

Start Install

Default is N. If needed, enter Y to copy the Core Profile password to the clipboard, and then paste to a text editor like Notepad. Repeat with the MongoDB autogenerated password.

5

Check the output for errors; successful installation will be error free. This can be done both on the console output, and the "install.log" file which will be created in the installation directory from which the install.ps1 script was executed.

Install Complete

The installation completes with the message "Installation completed successfully". No errors are shown.

Detailed Testing

The following sections are intended for use only during the initial deployment (first use) of the installer script (install.ps1) following which successful execution of the script (step 4 in the previous section) will be assumed to have deployed as per the detailed sections below. Therefore it is only necessary to check deployment with the sections below once (although any user may decide to implement the detailed tests on an ad-hoc basis).

Installation Testing - Firewall

Ensure Windows Firewall settings reflect requirements as defined in the Setup.xml file.

# Procedure Expected Result

1

From the Windows Start Menu, type "Firewall" and select the "Windows Firewall with Advanced Security" application.

Start Windows Firewall

Windows Firewall application is opened.

2

Inbound Rules - Click the Name column header to order the rules by "Name". Scroll down to find the single created inmation rule as shown below. Check the highlighted items for consistency with the setup XML file.

Inbound Firewall Rules
  • Core Service rule reflects the "InstanceName" in the settings XML file (e.g. AspenTech Inmation Core Service (D))

  • Program locations reflect the "InstallationFolder" in the XML file (e.g. D:\AspenTech\inmation.root\)

  • The Local Port for the Core Service reflects the "CorePort" set in the XML file (e.g. 6512)

3

Outbound Rules - Click the Name column header to order the rules by "Name". Scroll down to find the single created AspenTech Inmation rule as shown below. Check the highlighted items below for consistency with the setup XML file.

Outbound Firewall Rules

Close the Windows Firewall application when checks are completed.

  • Core Service rule reflects the "InstanceName" set in the settings XML file (e.g. AspenTech Inmation Core Service (D))

  • Program locations reflect the "InstallationFolder" set in the XML file (e.g. D:\AspenTech\inmation.root\)

Installation Testing - Services

Ensure the correct windows services have been installed.

# Procedure Expected Result

1

From the Windows Start Menu, type "Services" and select the "Services" desktop application.

Start Windows Services

Windows Services application is opened.

2

Check the single expected AspenTech Inmation installed service, and the MongoDB service, are present and running by verifying the items highlighted as below.

AspenTech Inmation Services
MongoDB Service

Close the Services application when verification is complete.

  • AspenTech Inmation Core Service is present and running; the InstanceName as set in the XML file is reflected in the service name.

  • MongoDB is present and running.

Installation Testing - Data Studio

Check the detailed installation of the AspenTech Inmation software using the Data Studio interface application.

To log in to the Core using DataStudio, the CoreProfileEnableLogin property must be set to 1 in the Setup.xml file. See steps 5 and 6 of the prerequisites section above.
# Procedure Expected Result

1

Data Studio is installed as part of the AspenTech Inmation installation and there will be a icon on the desktop to start this application.

Data Studio desktop icon

Double-click the icon to start Data Studio. On the first dialogue presented, ensure the selected Port (highlighted below) is the same as required from the XML settings file. Ensure that the "Enable TLS encryption" box is checked. Click Ok to continue.

Data Studio Connection

The first time that Data Studio is loaded, with a successful connection to the Core, you will be asked to create a new workspace. Select Ok to create the default workspace.

Data Studio Workspace

Data Studio starts correctly and interfaces to the AspenTech Inmation Master Core.

2

In the I/O Model panel, expand the System to show the installed Master Core.

Data Studio Master Core

Selecting the Core will display the Object Properties Panel. Check the settings as highlighted below.

Data Studio Master Core Object Properties
  • In the Common section:

    • Object Name reflects the OverrideObjectName setting of the XML file

    • Host Name or IP reflects the Object Name (as above)

    • Server Port reflects the CorePort setting of the XML file

  • In the Component Identification section:

    • The Component Role shows this is a Master Component (i.e. Master Core)

    • Instance shows the InstanceName setting of the XML file

3

In the I/O Model panel, select the System object and check the settings for the MongoDB database.

Data Studio Master System

In the Object Properties Panel, check the settings highlighted below.

Data Studio Master Core MongoDB Properties

Do this for each of the MongoDB Connection sections for the Data Stores as shown below.

Data Studio Master Core MongoDB Stores

For each Data Store the MongoDB Connection settings show:

  • Authentication Mode is set as SCRAM-SHA-256

  • User Name reflects the MongoDbUserName setting of the XML file

  • Password contains a random password generated during the installation phase

This should be checked for these data stores:

  • Time Series Data Store

  • Event (A&E) Data Store

  • Logging Data Store

  • Production Tracking Data Store

  • Custom Data Store

  • File Store

  • Audit Trail Data Store

  • Big Table Data Store

4

Select the Access Model panel and check the profile and specific users have been created with an Administrator role as per XML settings. View the passwords using the "eye" icon to show the random passwords, assigned during installation, for the three (3) MU-Global profiles associated with MES, Visual KPI and WebAPI.

Also, six (6) profiles have been created associated with the required Global functional roles (Administrators, Auditors, Engineers, Readers, and Writers) and the local "Core Owner" profile, which will take the name of the CoreProfileName of the XML file. In each profile, check a group has been created to reflect the AdPrefix and AdName settings of the XML file.

For the Core Owner profile (e.g. System-Administrators), check the CoreSystemOwner group or user has been configured per the XML file, as well as the emergency user (EmgUser) and also the Global-Administrators group is associated with this profile.

Data Studio Access Model

The functional user profiles for the following profiles have been created, all with Administrative privilege and unique and random passwords:

  • MU-Global-MES

  • MU-Global-VisualKPI

  • MU-Global-WebAPI

Five (5) Global profiles have been created for Administrators, Auditors, Engineers, Readers and Writers. In each profile, a Group has been created using the Authenticating Domain as set by the AdName setting of the XML file, with the group name prefixed with the AdPrefix setting of the XML file. Each Group name reflects this prefix concatenated with the group functional role (e.g. G-GXPC-DEV-Administrators).

A sixth Profile has been created to reflect the Core Owner as per the CoreProfileName of the XML file. This will contain the Emergency User configured using the EmgUser, EmgAdName and EmgUserDescription settings of the XML file. It will also contain the Global Administrators group as above, as well as the CoreSystemOwner configured either as a group or a domain user.

5

In the KPI Model, an Enterprise KPI object has been created with settings reflected from the XML configuration file.

Data Studio KPI Model
  • Enterprise KPI object is present

  • Object Name reflects the KPIObjectName of the XML file

  • Object Description reflects the KPIObjectDescription of the XML file

6

In the ISA-95 Model, an Enterprise ISA-95 Equipment Model object has been created with settings reflected from the XML configuration file.

Data Studio ISA-95 Model
  • Enterprise ISA-95 object is present

  • Object Name reflects the ISA95ID of the XML file

  • Object Description reflects the ISA95Description of the XML file

7

Returning to the I/O Model, the Security Perimeter and Message Broker objects are created as per the settings reflected from the XML configuration file.

Data Studio I/O Model
  • Core Logic Security Perimeter object is present per CreateSecurityPerimeter setting of the XML file

  • Message Broker (MSI) object (and Message Processor child object) is created per CreateMsiObjects setting of the XML file

  • Message Broker version and System Id reflects the MsiVersion and MsiSystemId of the XML file respectively.