|Applies To||RSA Product Set: RSA Archer|
|Issue||In some Archer installations changes in the Archer Control Panel that should immediately take effect immediately have no effect until the service is restarted.|
|Cause||When a configuration change is made in the Archer Control Panel all the Archer services, web sites, and applications must be notified of the change. There a few things that must happen for this to occur.|
Both conditions must be successful otherwise dependent systems will be unaware of the configuration change.
Note: If the service is unable to open its' own listener port, there is a fallback behavior where the configuration is requested every time it is needed. That prevents missing configuration changes but has a large negative performance impact because of the large number of additional database calls.
The client name in the table tblClientMonitor may not be a reliable indicator of the service that registered the listening port.
|Resolution||Resolve any firewall rules or account permissions configurations that prevent communication between all servers running any Archer application code except the Archer database over the configuration service ports typically 13300 - 13350.|
|Workaround||When modifying systems do not have an accurate list of configuration listeners or are unable to communicate to those listeners the only way for configuration changes to be reflected is to restart any Archer applications or services that are affected by the configuration change.|