Migrate Load Balanced Environment

Introduction

This document will describe how to migrate an already functional Load Balanced (LB) environment to a new environment. This document will describe in detail how you can move your existing LB environment to a new LB environment. All steps in this document need to be followed one-by-one to ensure that the migration will be performed without any issues.

Step 1 – Make Note of Current Configuration

On the current parent and any of the current child open the vSEC:CMS console application. From Options – Connections make a screenshot capture of what you have configured for each of the SOAP services connections configured, i.e. User Self-Service, RSDM Service, Operator Console Service and API Service. For example, make a screenshot of the connection details for User Self-Service and do the same for the other connections and store this information to be used later.

Step 2 – Stop vSEC:CMS Services child(s)

On each of the current child(s) stop ALL of the vSEC:CMS services that maybe running from the Windows services console, i.e. vSEC:CMS Service, vSEC:CMS - User Self Service, vSEC:CMS - RSDM Service, vSEC:CMS - Operator Console Service and vSEC:CMS – API Service. Ensure that all of the services have shutdown. You can verify this from the Details tab of Windows Task Manager on the server and ensure that AdmServer.exe, ApiServer.exe, CmsService.exe and UssServer.exe are not running. If any of these are running you should select them and click End task from Task Manager to stop them.

Step 3 – Stop vSEC:CMS Services

On the current parent stop ALL of the vSEC:CMS services that maybe running from the Windows services console, i.e. vSEC:CMS Service, vSEC:CMS - User Self Service, vSEC:CMS - RSDM Service, vSEC:CMS - Operator Console Service and vSEC:CMS – API Service. Ensure that all of the services have shutdown. You can verify this from the Details tab of Windows Task Manager on the server and ensure that AdmServer.exe, ApiServer.exe, CmsService.exe and UssServer.exe are not running. If any of these are running you should select them and click End task from Task Manager to stop them.

Step 4 – Install vSEC:CMS

On the new server install the version of vSEC:CMS that you wish to run using the installer GUI wizard. Once complete stop the vSEC:CMS Service from the Windows services console.

Step 5 – Install vSEC:CMS child(s)

On the new child(s) server(s) install the same version of vSEC:CMS that was installed on using the installer GUI wizard. Once complete stop the vSEC:CMS Service from the Windows services console.

Step 6 – Change Service Account

On the new and new child(s) change the vSEC:CMS Service to run under the same Windows user account as was configured on the current and child(s). This should be changed in the Windows services console.

Step 7 – Copy DAT Contents

Copy ALL files from the current dat folder of the to the dat folder on the new replacing any files in the new . The dat folder is located in the root folder of the vSEC:CMS server. You will need to make sure that the Windows user account that the vSEC:CMS service runs under, as configured in Step 6, has full permission on the dat folder on the new .

Similarly, copy ALL files from the current dat folder of the child to the dat folder on the new child replacing any files in the new child. The dat folder is located in the root folder of the vSEC:CMS server. You will need to make sure that the Windows user account that the vSEC:CMS service runs under, as configured in Step 6, has full permission on the dat folder on the new child. If you have more than one child in your environment it is recommended to copy the contents from current child1 to new child1 and so on for as many childs as you have in your environment.

Step 8 – Copy LB_config.xml

From the current copy the file LB_config.xml to the new . The LB_config.xml is located in the root of the vSEC:CMS installation which is normally located here: C:\Program Files (x86)\Versasec\vSEC_CMS S-Series.

From the current child(s) copy the file LB_config.xml to the new child(s). The LB_config.xml is located in the root of the vSEC:CMS installation which is normally located here: C:\Program Files (x86)\Versasec\vSEC_CMS S-Series. If you have 2 or more childs make a copy of the file on current child1 as indicated above and copy this file to the new child1. Continue the same procedure on any other childs you may have.

Step 9 – Start vSEC:CMS Service

On the new server start the vSEC:CMS Service. Depending on the size of your database it may take some time for the service to fully load. You can monitor this from the Details tab in Task manager and look at the CmsService.exe. Once you see that the CmsService.exe CPU is constant at 0-2% then start the other vSEC:CMS services that you had running on the current .

Log onto the vSEC:CMS console application on the new to confirm that this can be done successfully.

Navigate to Options – Operators and select the Service key store operator, as indicated by Type in the table, and click the Activate button to activate the key store operator.

Step 10 – Export Registry Settings

On each of the current child(s) make an export of registry key located below and save this as a file:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Versatile Security\vSEC_CMS_T]

Copy this file to each of the child(s) and apply it. For example, if you have 2 childs make a copy of current child1 registry as indicated above and copy this file to the new child1 and apply the registry key on the new child. Continue the same procedure on any other childs you may have.

These URLs are configured in registry below on each of the child(s):

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Versatile Security\vSEC_CMS_T\Service]

Look at the DWORD entries soap.adm.lb.url, soap.rsdm.lb.url and soap.uss.lb.url and make sure these point to the correct URL.

If SSL/TLS is used it is important that you have similar certificates available on the child(s) and as was configured when setting up the original LB environment. This is out of scope for vSEC:CMS.

Step 11 - Start vSEC:CMS child(s) Service

On the new child start the vSEC:CMS Service. Depending on the size of your database it may take some time for the service to fully load. You can monitor this from the Details tab in Task manager and look at the CmsService.exe. Once you see that the CmsService.exe CPU is constant at 0-2% then start the other vSEC:CMS services that you had running on the current childs.

Perform the same as described above on any other childs you may have deployed.

Log onto the vSEC:CMS console application on the new child(s) to confirm that this can be done successfully.

Step 12 – Validation

Now with all components in place you should perform a task from a client to ensure that the new LB environment is functioning as expected. A suggestion is to perform a full end-to-end credential token issuance to make sure everything is functional as expected.