Installation of Node Server (Master-Core)

These instructions refer to a Node Server, which connects to a Master-Core. The associated files are part of the installation template of the Node Server. The configuration files have to be modified as indicated, if not pre-created through an initial Preparation step. Refer to the installation preparation section General Installation Preparation.

The instructions can also be used to install multiple Connector instances on a single machine. For combined D/Q/P deployment on a single Node-Server, an important rule needs to be followed: The version of NodeSetup must match the lowest version used by either Q- or P- Master-Core. Otherwise an error is created "Downgrades are not supported by setup", when trying to install a lower version than already installed by a previous installation run. Additionally, the files of a previous installation in D:\installation need to be moved to a separate directory.

Prerequisites

# Procedure Expected Result

1

Confirm hostnames for this deployment:

Connector Server

D-GXPC-Conn-A

Core Server

D-GXPC-Core

2

Confirm extension parameters for this Connector, according to naming convention

Extension1: VLAN42

3

Open RDP session to Connector machine (Node Server)

Successful login on machine

4

Open File Explorer

Copy installation deliverables into the installation directory D:\installation

Installation Files

The following files exist in the installation directory D:\installation

  • AspenTechInmationNodeSetup.exe

  • install.ps1

  • NodeSetup.xml

  • pre-install.lua

5

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

6

Ensure that the NodeSetup.xml contains the right settings for the following static parameters. These parameters define the requirements for the instance type being installed (in this case, a Connector Node) and will not change between installations on any deployment. Edit and save if necessary.

ConnectorActiveComponent

TRUE

HasConnector

TRUE

HasRelay

FALSE

HasServer

FALSE

RelayActiveComponent

FALSE

InstallConnector32Bits

FALSE

InstallRelay32Bits

FALSE

InstallServer32Bits

FALSE

Install

TRUE

Update

FALSE

Delete

FALSE

7

Ensure that the NodeSetup.xml contains the right settings for the following dynamic parameters. 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 your Design Specification/Configuration Specification and verify that the following parameters in the xml match your specification.

Name

ConnectorCoreServerHost

ConnectorCoreServerPort

ConnectorListenerPort

ConnectorPassphrase

ConnectorSecurityMode

ServerCoreServerHost

ServerCoreServerPort

RelayListenerPort

RelayCoreServerHost

RelayCoreServerPort

InstallationFolder

OverrideObjectName

Initialize Connector Object

# Procedure Expected Result

1

Open RDP session to Master Core

Successful login on machine

2

Open start menu and type DataStudio

Open “AspenTech Inmation DataStudio” by pressing Enter

DataStudio window opens with “Connect to dialog”

3

Use Windows Authentication

Click Ok

Connection dialog closes. No error message is shown in connection dialog.

4

Optional: When using DataStudio for the first time, the “Create new workspace…” dialog appears

Leave proposed name and click Ok

Create new workspace dialog closes

5

In the Menu Bar, click Open  Console

New Console opens in AspenTech Inmation DataStudio

6

Copy the following mass command to the Console (pre-install.lua):

(require "esi-deploy"):INIT_CONNECTOR({
    extension1 = "VLAN42",
    connectorHost = "D-GXPC-Conn-A"
})

7

Press F5 to run the command

A new Connector object is created in the I/O Model.

The status of the Connector object is bad

All Lua scripts during installation are run on the DataStudio console. DataStudio is connected to the Master-Core.

Install Connector Service

# Procedure Expected Result

1

On the Connector installation server, open File Explorer and browse to the installation directory D:\installation

2

In File Explorer, select 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

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 deployment of the script (step 3 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 - Scroll down to find the single created AspenTech Inmation rule as shown below. Check the highlighted items for consistency with the setup XML file.

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

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

  • The Local Port for the Connector Service reflects the ConnectorListenerPort set in the XML file (e.g. 6510)

3

Outbound Rules - 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.

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

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

Installation Testing - Services

Ensure the correct windows service has been installed and configured

# 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 installed AspenTech Inmation Connector Service is present and running by verifying the item highlighted as below

Connector Service in Windows Services

Close the Services application when verification is completed

AspenTech Inmation Connector Service is present and running; the Name as set in the XML file is reflected in the service name

3

Go back to the Master Core machine and use DataStudio to check the Connector object status

Connector Status Good

The status of the Connector Object is good (Green)

4

Select the Object Properties and check the settings as highlighted below:

Connector Properties
Connector Properties
  • In the Common section:

    • The Object Name reflects the OverrideObjectName setting of the XML file

  • In the Communication section:

    • The Connection Mode reflects the ConnectorActiveComponent setting of the XMl file

    • The Security Mode reflects the ConnectorSecurityMode setting of the XML file

    • The Passphrase reflects the ConnectorPassphrase setting of the XML file.