Here are the documentation links for planing your re-hosting from Linux to Windows as well as other considerations for re-hosting from Linux to Windows"https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/continuous-testing/devtest-solutions/10-5/installing/preinstallation/system-requirements.htmlOperating System Requirements
We do not support on operating systems for which the software vendor has discontinued support.
The following operating systems are supported:
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows 7
- Windows 8.1
- Windows 10
Depending on the settings for Windows 7, 8.1, 9 and 10, you might have to start the installer executable as “Run as Administrator.”DevTest Server Requirements
Application Test and Service Virtualization require the registry in.
The minimum requirements for are:
CPU: 2 GHz or faster, 8 cores minimum
RAM: 8 GB available
Disk Space: 50 GBNOTE from Support: I would double the minimum and request at least 16 GB for each machine for better performance
Database: See Database Requirements. The registry database can reside on a different system and must have at least 500 GB of available storage.
For load and performance testing, the following resources are recommended:
250 virtual users for each simulator
1 processor core and 2-GB available RAM for each simulator
Example for 4000 concurrent virtual users: 16 simulators; 16 processor core; 32-GB available RAM (for )
For each data center:
1 test registry and 1 coordinator
1 processor core/process = 2 processor cores
2 GB available RAM/each = 4-GB available RAM (for )
A basic configuration has one enterprise dashboard, one registry, and one portal, which are required for all products. Application Test requires one coordinator server and one simulator server. Service Virtualization requires one virtual server environment. The Application Insight feature requires one broker. Only one enterprise dashboard server is required for any given configuration.
The requirements that are listed here are intended as a guideline. For large load environments, we recommend contacting Professional Services to assist with developing a load generation environment to suit your needs.Default Port Numbers
Will need to open all the needed DevTest ports number on the Windows machines, as well as the database port numbers.https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/continuous-testing/devtest-solutions/10-5/administering/general-administration/default-port-numbers.htmlPatches
Note any patches you have applied on your Linux machine, if any, will have to also be applied on the Windows machine.
Normal patches are deployed to the DEVTEST_HOME\lib\patches folder. These can be copied from Linux to Windows. If you have had any other patches applied where a folder or a jar files is replaced that was delivered with DevTest, this will need to be re-applied.Property and Vmoptions Files
Since staying with the same release, and databases, we can easily copy all the *.properties files, except lisa.properties, from Linux to Windows, as well as all the *.vmoptions files as well and change according to fit a Windows platform.Virtual Services MAR Files
Can copy all the *.mar files from the DEVTEST_HOME\vseDeploy\ folder from Linux to Windows DEVTEST_HOME\vseDeploy\Test Case Files
Can copy all the Project folders from the DEVTEST_HOME\Projects\ folder from Linux to Windows DEVTEST_HOME\Projects\Custom Jar Files
Can copy all the custom jar files from the DEVTEST_HOME\hotDeploy\ folder from Linux to Windows DEVTEST_HOME\hotDeploy\.Third-Party Jar Files
Can copy all the 3rd-party jar files not delivered with DevTest from the DEVTEST_HOME\lib\Shared\ folder from Linux to Windows DEVTEST_HOME\lib\Shared folder.NOTE: It is important to not copy earlier or later versions of a file we deliver with DevTest to the folders where DevTest is installed to.