The new SCOM Connector 4.7.3 seams to publish the Alarm Name incorrect.
Running Software class CIs are being named with format usm-core:RunningSoftware... instead of just the hostname
SOI 4.2
1. Stop the IFW services where SCOM connector has installed
2. Remove the Connector from the Administration so this will remove the wrong CIs
3. Modify below policy
CA\SOI\resources\Core\Catalogpolicy\scom_policy.xml
Add below line with EventClass RunningSoftware section. Here, we are populating 'RunningSoftware' with TypeName property. After above changes it should replace 'usm-core:RunningSoftware' from CI label.
<Field output="TypeName" format="RunningSoftware" input="" />
Add above line like in below screenshot highlighted in yellow-
4. Also, Open below configuration and enable debug log.
CA\SOI\resources\log4j_IFW.xml
Uncomment below line.
<Logger name="com.ca.sam.ifw.framework" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
<Logger name="com.ca.sam.ifw.eventplus" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
<Logger name="com.ca.sam.ifw.publisher" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
<Logger name="com.ca.sam.ifw.consumer" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
<Logger name="com.ca.sam.ifw.api" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
<Logger name="com.ca.eventplus.catalog" level="DEBUG" additivity="false">
<AppenderRef ref="EITransform"/>
</Logger>
<Logger name="com.ca.usm.ucf" level="DEBUG" additivity="false">
<AppenderRef ref="IFW"/>
</Logger>
5. Start the IFW servcies
The next SCOM connector version will include this fix.