Users receiving alerts in SOI that originate from CA UIM need to identify and access the User_tag fields (such as os_user1, os_user2, user_tag1, or user_tag2) within the SOI alert payload for better alert correlation and troubleshooting.
Product: CA Service Operations Insight
(SOI) Component: UIM Connector
By default, the UIM connector for SOI does not map custom user tags from the UIM alert payload to specific SOI alert attributes. A manual configuration change in the connector policy is required to enable this mapping.
To extract the User tag from the UIM alert payload and display it in the SOI Console, follow these steps to modify the UIM connector policy:
os_user1, os_user2, user_tag1, or user_tag2).CA\Catalyst\CatalystConnector\registry\topology\physical\_CatalystConnector\modules\policy\nimsoftconnector_policy.xmlCA\SOI\resources\Core\Catalogpolicy\nimsoftconnector_policy.xmlnimsoftconnector_policy.xml file and locate the <EventClass name='Alert'> section. Add a mapping entry to link the UIM property to an available SOI attribute (e.g., userAttribute1).userAttribute1 (or your chosen attribute) column in the SOI Console.UIM robot shows user_tag_2 is set
SOI Console shows the value of user_tag_2 in userAttribute2