<< 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!
|