Hi,
this is a great question and depends on what you want to achieve - there is no single answer:
Using the UIM Connector gives you all the granular objects, e.g. Alerts are assigned to individual objects (such as Processes, Disks, Databases, ...) rather than the device-level objects. Spectrum does not know about this level of objects coming from UIM and assigns all messages to the parent. For Business Service Models you mainly need all the granular objects.
Spectrum can perform some Root-Cause-Analysis in the context of the network topology when UIM is integrated into Spectrum.
When only using the Spectrum Connector, everything comes into SOI as "Spectrum" Alerts and CIs, and as such SOI has no knowledge about that they come from UIM originally, for example there is no Launch-in-Context to the UIM Portal from SOI.
When using both Connectors (e.g. UIM and Spectrum) to SOI you can face multiple issues:
- duplicate Alerts (there is no automatic suppression, because the Alerts come from different Connectors and are assigned to different CIs)
- loops/inconsistencies in updating information especially when using Synchronization to both systems from SOI
- not all updates (Acknowledge, Ticket Number, Maintenance) are synchronized in all directions if they are performed in one system
Thus, to use both Connectors and the Spectrum-UIM integration has to be carefully analysed and configuration is required to avoid some of the above issues.
A "Best Practices Guide" to handle this triple-integration is under development, but there are also adoptions in the Connectors required to handle this situation.
At the moment there is only one answer: It depends .
MichaelBoehm