Installing Multiple Instances

<< Click to Display Table of Contents >>

Navigation:  Software Overview > RMS Monitoring Software > Server Software Installation > RMS Software V2.1.1 > System Requirements for Version 2.1.1 >

Installing Multiple Instances

The RMS license can be activated 3 times:

a.Test environment.

b.Validation environment.

c.Production environment.

 

Here are two different ways to carry out the installation:

Option 1

Install the RMS software on 3 different servers with 3 different MS SQL Instances.

Option 2

Install the RMS software on 1 server, with 1 MS SQL Instance and 3 databases.

 

RMS needs to be installed 3 times, each time the IIS details, the ports and the parth for the files need to be different:

IIS details: set wPageName and wServiceName in InstallRmsV210.cmd for each environment (Example: RMSTest and wServiceTest; RMSVal and wServiceVal; RMSProd and wServiceProd).

Port: set ManagerInstance in InstallRmsV210.cmd and the port in ServiceManager\RmsServiceManager.exe.config, wPage\web.config and wService\web.config for each environment.

Path for the files: set LogDir of Nlog.config in the folder wService, wPage and ServiceManager for each environment.

RMSAppPool details: set RMSAppPool fore each environment (Example: RMSAppPooltest and RMSAppPoolVal and RMSAppPoolProd.

 

Important the LAN devices need to be configured correctly to be able to communicate with the required software.

 

Important: all software environments can be opened via the browser (/RMSTest, /RMSVal, RMSProd), however, the user cannot be logged into various systems at the same time.

 

When setting up the installations on 1 server, it is important to clearly organise the setup. Rotronic recommends the following setup:

C:\inetpub\wwwroot\rms\

C:\inetpub\wwwroot\rmsTest\

C:\inetpub\wwwroot\rmsVal\

 

Under each path, the software should be saved. And the location of the files and each environment should have their own files.

C:\inetpub\wwwroot\rms\files

C:\inetpub\wwwroot\rmsTest\files

C:\inetpub\wwwroot\rmsVal\files

 

Under the RMS system settings, the documentation path should be added correctly!

 

Note:

 

When all environments are setup identically, then the users can log into all environments without having to login via the browser Cookies, where the login details are saved.

 

Remove the settings in the web.config and wPage to ensure that the Cookies cannot be used:

<machineKey

validationKey="5B7324A48A4D8E74498DC14FA165372F8ACDCE8EC9C0892B4A6591BB1314D5EE8AC30E895E05AD23DB0B980DB7F7871040DAA1B3A4F4CC2429AC3D0EE6656BBC"

decryptionKey="A504E29FAC4A4F6C1A6E1D8636EA5EBE3A71604287223B648C8FBA54DDB2781D"

validation="SHA1"

decryption="AES"

/>