When you upgrade DXmanager, the dxmanager.dxc file is retained, unchanged. This file is used to specify any configuration that should be a default for your directory. This is the last configuration file to be sourced in a DSA's initialization, which means that it overrides any other configuration.
DXmanager has been changed significantly between CA Directory r12 SP2 and r12 SP9. In particular, many configuration items are now supported by DXmanager, and no longer need to be set in configuration text files.
If your dxmanager.dxc files contain any of these configuration items, it will not appear to cause any conflicts even though these values are overridden by the DXmanager configuration. This is because the dxmanager.dxc files are ignored if they conflict with settings in DXmanager.
If any of these settings exists in a custom configuration file, it may cause conflicts. When CA Directory encounters a configuration conflict while loading or re-initializing the configuration, the following alarm is logged:
DSA_E3410: Configuration: Text-based configured values are redefining DXmanager set values (see warn-log for details)
The warn-log shows which commands are being redefined by DXmanager. You should remove these items from the text configuration files and set them using DXmanager. Use the list of configuration items in Commands Used in DXmanager to find out where to set these items in DXmanager.
Note: We recommend that you use a pre-production test environment, to help you isolate any migration issues and configuration conflicts.
|
Copyright © 2013 CA.
All rights reserved.
|
|