Attribute or template conflicts
Attribute or template conflicts can occur when Bravura Security Fabric is upgraded. You can use loadplatform to list attribute or template conflicts, and forcibly override those conflicts if required. The idmsuite.log file also describes which attributes or templates are at fault and proposes changes.
It is the responsibility of the Bravura Security Fabric administrator to determine which portions of the Bravura Security Fabric instance may be affected by changes to default attribute values or characteristics; for example, the attribute’s value may no longer be queried by default. If PSLang scripts make decisions based on this attribute’s value, the decisions may no longer be correct.
Note
The Connector Pack upgrade process does not modify any existing attribute definitions used by the instance. You must decide which, if any, attributes should be modified when upgrading the Connector Pack.
If you choose to apply this upgrade, then it is recommended that you backup the attrdef and attrdefval tables before updating the values. The attrdef and attrdefval CSV files are located in the agent\dat directory.
There are currently two ways to update the attribute default values:
Manually running
loadplatform. exe with the -force flag. This applies all changes for the targets you specify. See the loadplatform usage information for details.Manually overriding individual attributes from the menu. You can override attributes at the target system or target system type level. See the Bravura Security Fabric documentation for details
To forcibly update the attributes or templates, manually run loadplatform.exe with the -force flag. This applies all changes for the targets you specify. For example:
loadplatform.exe -force -a <connector name>
To see a list of all loadplatform arguments, use the following command:
loadplatform.exe --help