Duplicate checking policy
There are two parameters that control whether duplicate integration identifiers can exist in the Maximo® database.
The cci.dis.dupe.policy.ui parameter determines the policy applied for duplicate integration identifiers, if found when:
- Creating or modifying assets in the Assets application
- Creating or modifying CIs in the Configuration Items application
- Promoting assets in the Deployed Asset application
- Promoting CIs in the Actual CI application
| Value | Default | Description |
|---|---|---|
| allow | Default value assigned when upgrading IBM® Control Desk. Also the default value, if an invalid value is specified for this parameter. | The asset or CI with a duplicate integration identifier is created. |
| disallow | Default value assigned for a new installation of Control Desk | The asset or CI with a duplicate integration identifier is not created and an error message is shown. The message indicates that the generated integration identifier is a duplicate of a specified asset or CI. |
The cci.dis.dupe.policy.background parameter performs a similar function but for tasks that run in the background. That is, it determines the policy applied for duplicate integration identifiers, if found when:
- Creating or modifying assets or CIs in the integration framework
- Promoting deployed assets in one of several escalations (PROMOTECOMP, PROMOTENETD, and PROMOTENETP)
| Value | Default | Description |
|---|---|---|
| allow | Default value assigned when upgrading IBM Control Desk. Also the default value, if an invalid value is specified. | The asset or CI with a duplicate integration identifier is created. |
| disallow | Default value assigned for a new installation of Control Desk | The asset or CI with a duplicate integration identifier is not created and an error message is added to the J2EE application server log. The error message indicates that the generated integration identifier is a duplicate of a specified asset or CI. |