Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hi

I am running a policy which is scheduled to run 24X7 and the object that is being used monitor mom alerts and gets triggered as soon as the new alert is seen on mom server. Opalis mom connector service sometimes goes into hung state and this policy will be still in running mode .This make us missed alerts on Weekends and on monday we stop and restart the policy manually after opalis mom connector service is restarted on MOM server. Is there a way we can check the health of the deployed policy and if it is hung state ,stop the policy and restart the same . I was able to automate the job for restart of the policy if the policy is in stopped mode but if it is in hung mode ,i could not find a way to check the same .I did try to compare the heartbeat with db time but no luck .Please let me know if I need to check any table in Opalis db to determine if policy health is ok .

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hello,

perhaps you can make a "workaround": Schedule the policy to run every x minutes with the "Monitor Date/Time" -object followed by a  "Get Alert"-object which gets the new alerts. Then let follow a "Update Alert" to acknowledge the alerts to no get them found the next schedule.

Another thing is to make a policy with "Monitor Service" or  "Monitor Date time"  and "Get Service Status" which looks for the "MOM Connector Service". -> Whe it's in the hung state -> Resart service and the policy. 

• Proposed as answer by Vivian Xing Tuesday, June 21, 2011 6:49 AM
• Marked as answer by Vivian Xing Monday, July 04, 2011 9:04 AM

Hi

Thanks ,This was helpful

Hi

I want run same sort of policy for log file, whenever get hung status, it should send an alert. Hope you r running almost same thing. I want to use it for SystemOut.log in Websphere Application Server for listner ports.

Can you please help me on this and send process & commands.

regrads

Hello,

do I understand right? You want to monitor with Opalis a log file from Websphere (SystemOut.log) for keywords, right?

If yes, perhaps you can open a different thread for it because this topic is different from yours.

Perhaps this thread from Orchestrator (Name for new Release of Opalis) helps: http://social.technet.microsoft.com/Forums/en-US/scoscip/thread/84410c10-a154-40e7-a75c-9fd194eefdd4

Do you have a Monitor Solution where you can monitor log files?

Regards,

Stefan