IBM Support

Using SOAP and needing to use two CT_reset commands to close alert.

Technical Blog Post


Abstract

Using SOAP and needing to use two CT_reset commands to close alert.

Body

image

Using SOAP and needing to use two CT_reset commands to close alert.

Came across this the other day, where a customer had upgraded to a 6.3 ITM version, and was using soap to create their own alerts.

The CT_Alert and CT_Acknowledge worked fine, but using CT_Reset did not close the alert.
The alert was not closed until a second CT_Reset was sent.


Investigating,  it was found that the origin node on the alert did not exist in the node list or node status table.

Customer was testing out the SOAP alerts using a test node name so that is did not effect any live machine information.

This make sense from the data side, but does not make 'sense' to ITM.

ITM expects that every node it gets information about,  is known and is in the node list and/or node status tables.  

Since ITM expects to be able to match the origin node and then cannot do this, there can be odd behaviours and inconsistent results.

The same tests were run with a node origin that was known to ITM (so was in the tables) and the first CT_Rest closed the alert as would be expected.

image

Check out all our other posts and updates:

Academy Blogs:                    http://ow.ly/FezGi

Academy Videos:                  http://bit.ly/1wFKveY

Academy Google+:               http://bit.ly/1sR5QTV

Academy Twitter Handle:     http://bit.ly/1CknfoF

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"SSZ8F3","label":"IBM Tivoli Monitoring V6"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":""}]

UID

ibm11084173