Install MongoDB on the secondary replica set members

Install MongoDB

The MongoDB installation on either of the secondary nodes should be the same by using a dedicated script that installs the software with the settings as defined in the Setup.xml. The script execution should not require user interaction (aside from that to execute the script).

# Procedure Expected Result

1

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

In CMD Shell, type:

MSTSC /v:D-SITE-RepB

Execute this command by pressing Enter.

Successful login on machine with administrative account.

2

Open File Explorer and browse to the installation directory (e.g. D:\installation)

Folder contains 4 files as shown in pre-requisites.

3

In File Explorer, go to the File  Open Windows PowerShell  Open Windows PowerShell as administrator.

Start PowerShell

PowerShell with administrative privileges is available.

4

Execute the command to run the installation script by typing

 .\install.ps1

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

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.

6

Repeat step 1 to 4 to all secondary replica set nodes

MongoDB and Connector services are successfully installed in all secondary replica set nodes.

Test Installation - Log file

Ensure there is no error recorded in the log file during the installation.

# Procedure Expected Result

1

Go to the installation directory (D:\installation) and open the install log file (install.log.txt) Make sure that the installation was completed without errors.

No error recorded in the log file during the installation..

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).

Test Installation - Firewall

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

# Procedure Expected Result

1

Open a Window command prompt and type wf.msc.

Windows Firewall with advanced security is opened.

2

Inbound Rules - order rules using "Name" by clicking the Name column header. Scroll down to find the two created AspenTech Inmation rules 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\).

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

3

Outbound Rules - order rules using "Name" by clicking the Name column header. 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\).

Test Installation - Service

Ensure the correct windows service has been installed.

# Procedure Expected Result

1

Open a Window command prompt and type services.msc.

Windows Services application is opened.

2

Check the expected MongoDB installed service is present and running by verifying the item highlighted as below.

MongoDB Service

Close the Services application when verification is complete.

MongoDB service is present and running; the Name as set in the XML file is reflected in the service name.

3

Check the installed Connector service is present and running by verifying the item highlighted as below.

AspenTech Inmation Services

Close the Services application when verification is complete.

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

4

Go back to the Master Core machine and use DataStudio to check the Connector object status and its properties settings.

MongoDB Connector Object Properties

The status of the Connector object for the installed secondary replica set is good (Green).