000033070 - How to configure RSA Archer to use a customized port for SQL Server connection

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Mar 28, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033070
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x, 6.x
Product Description: Archer Platform
IssueSQL Server is configured to be connected on a customized port other than the standard 1433, so it needs to make changes on Archer accordingly.
ResolutionAfter making changes on the SQL Server, please follow the below steps to make change on Archer web server.
  1. Make a copy of the below file:
    Default Archer installation folder is C:\Program Files\RSA Archer
  2. Edit the file and locate the ConnectionStrings part.
  3. Add comma and port number after the server name. In this example, 2500 is the customized port.
    SQL Authentication example:

    <add name="SqlDB" connectionString="Server=sql.archer.local,2500;Database=Archer_Config;UID=XXX;PWD=XXXX" providerName="System.Data.SqlClient" />

    Windows Authentication (integrated security) example:

    <add name="SqlDB" connectionString="Server=sql.archer.local,2500;Database=Archer_Config;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

  4. Restart RSA Archer Configuration service.
  5. Open Archer Control Panel, go to Instance page and Database Tab.
  6. In the SQL Server field, add a comma and port number after the server, such as Sql.archer.local,2500. 
NotesFor more information to change the listening port on SQL Server, please refer to Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager).
For any questions regarding the Microsoft KB, please contact Microsoft Support.