tag:blogger.com,1999:blog-2852787584922573183.post945860183135105198..comments2023-07-22T08:23:32.922-04:00Comments on Tivoli With A z: Exploit policies to manage OMEGAMON situationsEd Woodshttp://www.blogger.com/profile/06527379412750259529noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2852787584922573183.post-83029214920686621732010-01-13T15:31:54.182-05:002010-01-13T15:31:54.182-05:00Paul, you bring up a good point. The example I sh...Paul, you bring up a good point. The example I show is admittedly a bit simplistic. I just wanted to show that you can use policies to stop/start these situations.Ed Woodshttps://www.blogger.com/profile/06527379412750259529noreply@blogger.comtag:blogger.com,1999:blog-2852787584922573183.post-9960587522992587342010-01-12T11:16:25.655-05:002010-01-12T11:16:25.655-05:00ITM V6 has a new "Activity" located in t...ITM V6 has a new "Activity" located in the "Extensions" tab. It is called "Wait until a situation is False".<br />I would add this to the policy after it starts the situation. Have it wait until situation EW_check_Prime_Time is False. This way , it will start the situation once and then wait. Without this, it will restart the situation each interval. (Interval of the situation EW_Check_Prime_time). This has two benefits. First, less overhead when you don't restart the situation every interval. Second, if the situation EW_Demo_DB2_Alert is true, restarting it would re-drive the event and make it fire True again.Paulhttps://www.blogger.com/profile/09620816615374159661noreply@blogger.com