000027365 - How to Move the NIC App Server in an enVision 4.0 Multi-Site

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027365
Applies ToenVision Core
IssueHow to Move the NIC App Server in an enVision 4.0 Multi-Site
Resolution

 

 

  The following discussion is based on a simple deployment model. Master has A-Srv1, which is running App Server, and Slave has A-Srv2. The goal is to move the App Server from A-Srv1 to A-Srv2. After moving, the App Server will run on A-Srv2.

 

  1. Delete all custom Task Triage Dashboard reports since we cannot support moving them now. You have to delete them first here, and then recreate them in step 11.

                                                    i.     Access Web_UI of A-Srv1 running App Server.

                                                  ii.     Go to Overview >> System Configuration >> Dashboard Items >> Dashboard Reports.

                                                iii.     Find a Task Triage custom dashboard report by clicking a report name, pressing ?Modify? button (If the button is disabled, this report is a built-in one rather than custom one. Ignore It.), pressing ?Next? button, and assuring that the Select table is ?Task Triage? table.

                                                iv.     Delete by clicking the name of the found Task Triage custom dashboard report again, and then pressing ?Delete? button.

 

  1. Uninstall App Server on A-Srv1 by running un-installation script (E:\nic\<version_number>\<server_name>\bin\appserver_uninstall.bat)
  2. Wait for about 10 min to get configuration data replicated among D-Srvs. Waiting time depends on the size of multi-site (i.e. number of D-Srvs)
  3. Stop NIC DB Server on A-Srv1 with Services dialog box (Start >> Control Panel >> Administrative Tools >> Services). (This also stops NIC Alerter, NIC DB Report Server and NIC Web Server due to dependencies).
  4. Move data from A-Srv1 to A-Srv2. The data includes the following (please keep the directory / subdirectory structures):
    • App Server DB file located at E:\nic\<version_number>\<server_name>\database\appserver.d
    • The files and subdirectories in  E:\nic\tasktriage directory.

                                                    i.     TT meta data (Built-InMetaData.xml and EscalateMetaData.xml files)

                                                  ii.     ?journal? directory

                                                iii.     ?escalate? directory (if escalation functionality has been used)

                                                iv.     ?trace? directory (if escalation functionality has been used)

                                                  v.     ?userattachments? directory.

 

  • Custom non-dashboard Task Triage reports. All schema files (xml files) of custom reports are located at E:\nic\<version_number>\<server_name>\etc\reports\custom directory and its subdirectories. You only need to move those report schema files referring to the ?Task Triage? table. (User can open individual report xml file to see if it refers to ?Task Triage? table.)

Please note you need to delete the above data from A-Srv1.

 

  1. Start NIC Alerter on A-Srv1 with Services dialog box (this also starts NIC DB Server and NIC Web Server due to dependencies). Start NIC DB Report Server if it is not started.
  2. Restart NIC DB Server on A-Srv2 with Services Manager.
  3. Install App Server on A-Srv2 by running installation script (E:\nic\<version_number>\<server_name>\bin\appserver_install.bat).
  4. Wait for about 10 minutes to get configuration data replicated among D-Servers. Waiting time depends on the size of multi-site (i.e. number of D-Srvs).
  5. Restart the NIC Web Services on all A-Srvs in order for them reconnect to App Server.
  6. Recreate the deleted custom Task Triage dashboard reports (see step 1) from Web_UI on A-Srv2 now running App Server.
Notes

This document targets pure enVision 4.0 deployment. It is expected these steps also work for pure enVision 3.5.x deployment or pure enVision 3.7 deployment, just ignoring the steps for enVision 4.0 Task Triage reports. But this document is not applicable for the mixed deployment during enVision upgrade to 4.0.

 

This document has been verified by both Engineering and QA.

Legacy Article IDa44982

Attachments

    Outcomes