000032652 - Moving database to a new server for RSA Archer

Document created by RSA Customer Support Employee on Jul 10, 2019Last modified by RSA Customer Support Employee on Jul 10, 2019
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000032652
Applies ToRSA Product Set: Archer
 
IssueThis article provides instructions on how to update the RSA Archer settings for the instance database.
ResolutionTo resolve this issue,
  1. Open the Archer Control Panel and navigate to Installation Settings > Job Management.
  2. Check the box labeled Discontinue processing new jobs and click Save.
  3. Return to the Job Management page and ensure that there are no jobs listed in the Jobs in Progress window.  If there are, refresh periodically until all currently executing jobs have completed.
  4. Screenshot all the settings in the Instance Tab of the Archer Control Panel
  5. Close the Archer Control Panel.
  6. On each legacy Archer Web and/or Archer Services server, stop IIS and Archer Services.
    1. World Wide Web Publishing Service (website)
    2. Archer Services – LDAP Service
    3. Archer Services – Job Engine
    4. Archer Services – Queuing Service
    5. Archer Services – Configuration Service
    6. Archer Services - Advanced Workflow
  7. Backup the Archer Instance Database on the legacy SQL server.
  8. Restore the Archer Instance and create a new Configuration Databases on the new SQL server.
  9. Verify SQL Accounts as DB_OWNER to the Archer Framework and Configuration Databases on the new SQL server.
  10. Run the following two scripts on the Archer Instance Database on the new SQL server:


DELETE FROM tblSearchMessageContent
DELETE FROM tblSearchMessageQueu
e


  1. Run the installer on a web server with all boxes checked. This will set up the new Configuration database and existing Instance Database properly.
  2. The Configuration Service will be Started.
  3. When the Archer Control Panel opens, re-create the Instance settings using your screenshots.
  4. On each legacy Archer Web and/or Archer Services server, start the remaining Services.
    1. Archer Services – Queuing Service (If multiple servers, this service should run on ONLY ONE server).
    2. Archer Services – Job Engine
    3. Archer Services – LDAP Service (If multiple servers, this service should run on ONLY ONE server).
    4. Archer Services - Advanced Workflow (on web servers)
  5. Navigate to the Archer Login page and verify that you can now login to the Framework on the new database server.
  6. Open the Archer Control Panel and navigate to Installation Settings > Job Management.
  7. Uncheck the box labeled Discontinue processing new jobs and click Save.
  8. Still in the Archer Control Panel, navigate to Instances > [YourInstance]. In the Actions pane, select Rebuild Search Index and confirm the prompts.
  9. If this does not work, do a complete search index rebuild. See 000030392 - How to perform a Search Index Rebuild in the RSA Archer Suite for more information.

Attachments

    Outcomes