Understanding WebSphere Business Monitor Failed Events Manager

Size: px

Start display at page:

Download "Understanding WebSphere Business Monitor Failed Events Manager"

Laura Hill
5 years ago
Views:

1 IBM Software Group Understanding WebSphere Business Monitor Failed Events Manager Sridhar Staff Software Engineer 17 June 2010 WebSphere Support Technical Exchange

2 Agenda Overview Architecture Basic Modeling Terminology Admin Console Screens Common Scenarios Summary Useful Links WebSphere Support Technical Exchange 2 of 22

3 Introduction A failed event is an incoming event that has not been successfully processed and has caused part of a monitor model's processing to stop in order to maintain data consistency. The tools in the WebSphere Business Monitor 6.1 administrative console let you inspect a failed event and take appropriate action to resume processing. An administrator can edit, delete, and reorder existing events to resubmit them for successful processing. WebSphere Support Technical Exchange 3 of 22

4 Architecture Model Logic Monitor Queue CEI Event Service Event Stream Moderator Model Logic Queue Bypass Monitor Database x Model Logic Failed Event Resubmit Event Failed Event Queue Admin User WebSphere Support Technical Exchange 4 of 22

5 Flow of failed Events Events are resubmitted via admin console Event is read from failed event "queue". Queue contents found in EQ_* tables. Event is placed on the wbm_modelid_versionid_q_r JMS queue. Event stream moderator picks it up for processing. Event stream moderator processes the event immediately. Event processing results (e.g. success/ failure) returned to failed event sequence manager. If event processing was successful, event is deleted from the failed event queue. WebSphere Support Technical Exchange 5 of 22

6 Modeling Terms WebSphere Support Technical Exchange 6 of 22

7 Modeling Terms Explained Monitoring Context: A monitoring context definition is the term used by WebSphere Business Monitor to describe all the data that should be collected about an entity (such as a transaction or business process). Each monitoring context evaluates to a Monitoring Context Instance Correlation Expression: Events are processed by monitoring context instances. The correlation expression identifies which instances will process the event. You can specify what action perform when no monitoring context instances are identified (such as creating a new monitoring context instance, or treat as error), when one monitoring context instance is identified (typically deliver the event to the instance for processing), or many monitoring context instances are found Sequence Number: Determines what order the events have to be processed. Sequence has to be of the same Type Eg: String or Integer etc; When using numbers as type string then the USER MUST add the padding since they are compared lexographically WebSphere Support Technical Exchange 7 of 22

8 Admin console Screens WebSphere Support Technical Exchange 8 of 22

9 Admin Console Screen (Continued) WebSphere Support Technical Exchange 9 of 22

10 Admin Console Screen (Continued) WebSphere Support Technical Exchange 10 of 22

11 Runtime Settings WebSphere Support Technical Exchange 11 of 22

12 Some known Error Codes Event OutOfOrder Exception Parent Not found Exception Instance Already Halted No Correlation found exception "stop if event cannot be interpreted is received" (Unrecoverable Events). Event processing retry failure Correlation error retry failure WebSphere Support Technical Exchange 12 of 22

13 Error Codes Explained Parent not found exception: a) child instance created before the parent instance b) parent never created c) correlation expression of child to parent could be wrong d) event emission not enabled on the parent e) Some events could have been filtered out at CEI WebSphere Support Technical Exchange 13 of 22

14 Error Codes Explained (continued) No correlation exception: a) Instance was never created. b) correlation expression is wrong. c) Parent instance has been terminated. WebSphere Support Technical Exchange 14 of 22

15 Error Codes Explained (continued) Instance already halted: a) An event when hits the failed event queue will automatically arrange for all the events of its monitoring instance to fall into the failed event queue with the reason of Instance already halted. b) Normal event processing can only resume after the failure reason has been corrected and Resume Processing has been submitted for that instance. WebSphere Support Technical Exchange 15 of 22

16 Mbean Interface There is an Mbean interface that could be used in conjunction with wsadmin to address failed event functions programmatically. This also allows for cleaning up all the failed events for a particular Monitor Model. Eg: resetmodelversion(). A particular failed instance could be cleaned up also, based on the Event Sequence Instance ID. Eg: reseteventsequenceinstance(). WebSphere Support Technical Exchange 16 of 22

17 6.1 multithreaded vs emulation In emulation the event processing is single threaded, wherein an event processing failure causes any event received by Monitor to be piled up on the failed event queue. In 6.1 Multithreaded Mode failed events are categorized based on Event Sequence Instance ID. This literally means a failed event blocks only the failed events for its particular instance. WebSphere Support Technical Exchange 17 of 22

18 Summary Failed Events lets you identify Event Processing failure scenarios. There are at least 7 errors, that are known to cause failure of event processing. Runtime Settings and Modeling Practices can help alleviate some event processing failures. 6.1 multithreaded mode is the preferred runtime processing strategy. WebSphere Support Technical Exchange 18 of 22

19 Useful Links rs=802&uid=swg v6r2mx/topic/com.ibm.btools.help.monitor.doc/ home.html WebSphere Support Technical Exchange 19 of 22

20 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 20 of 22

21 We Want to Hear From You! Tell us about what you want to learn Suggestions for future topics Improvements and comments about our webcasts We want to hear everything you have to say! Please send your suggestions and comments to: WebSphere Support Technical Exchange 21 of 22

22 Questions and Answers WebSphere Support Technical Exchange 22 of 22

Troubleshooting IBM Business Monitor

IBM Software Group Troubleshooting IBM Business Monitor Benjamin Bertow (benjamin.bertow@de.ibm.com) WBI Level 2 Support Engineer 20 December 2011 WebSphere Support Technical Exchange Agenda Missing instances