000024618 - How to change RSA ACE/Server agent host parameters in sdconf.rec file

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 Number000024618
Applies ToRSA ACE/Server 5.0.1 (no longer supported as of 8-15-2004)
RSA ACE/Server 5.0.2 (no longer supported as of 8-15-2004)
UNIX (AIX, HP-UX, Solaris)
Microsoft Windows
Remote Administration
IssueHow to change RSA ACE/Server agent host parameters in sdconf.rec file
How to generate legacy sdconf.rec files in RSA ACE/Server
Generating legacy sdconf.rec does not show changes made in Configuration Mgmt (Windows) or 'sdsetup -config' (UNIX)
CauseWhen generating a legacy sdconf.rec through the 'Assign Acting Servers' Option of an Agent Host, the admin is attempting to do this with Database Administration REMOTE Mode (or Remote Administration), as opposed to Database Administration HOST Mode.
- When generating the legacy sdconf.rec, the software will generate this from its 'working' sdconf.rec
- When generating a legacy file through HOST mode, you will be using the sdconf.rec in the ACEDATA directory of the ACE/Server itself
By default, Configuration Mgmt and 'sdsetup -config' are both editing the same ACEDATA sdconf.rec file. However, when generating a legacy file through REMOTE mode, you will be using the sdconf.rec in the ACEREALMS folder as opposed to ACEDATA. Remote mode may be through our own Remote Administration Software...or even when "terminal server'ed" into the ACE/Server using Remote Mode. This ACEREALMS sdconf.rec may not have the same parameters as the one in ACEDATA.
ResolutionWhenever making changes to the sdconf.rec with Configuration Mgmt or 'sdsetup -config', be sure to copy the sdconf.rec to the appropriate locations.
Legacy Article IDa12696

Attachments

    Outcomes