IBM Plunges Into ?Business Event Management,? Helping Define Field


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News IBM Plunges Into ?Business Event Management,? Helping Define Field
# 1  
Old 11-28-2008
IBM Plunges Into ?Business Event Management,? Helping Define Field

by Charles Babcock InformationWeek November 26, 2008 The fairly new field of complex event processing sets parameters around a software event and triggers alerts if the rules governing it are violated. IBM (NYSE: IBM) is staking out a position in complex event processing as applied to business processes; it’s coined the term “business [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. AIX

IBM business partner login

I'm looking to download some docs and test software from IBM web site. My login stated I'm not a IBM Business partner. Does anyone know of a guest or temp login I could use to access this site information? (1 Reply)
Discussion started by: soupbone38
1 Replies

2. Programming

Need to know about Event Management

Hi I need to understand abt Event Management Library for example..A module will be responsible for Handling the event posted by the other modules...and creating a new process for handling the event posted by the other modules..also after completing the event clearing of the event... Need to... (3 Replies)
Discussion started by: nathgopi214
3 Replies
Login or Register to Ask a Question
event_class(5)															    event_class(5)

NAME
event class file - The file that contains the declaration of an event class. DESCRIPTION
Audit events can be logically grouped into event classes. Event classes are defined in event class files. An event class file contains an event class number and a list of event numbers corresponding to audit events. All event class files must be created in the dcelocal/etc/audit/ec directory. The name of the event class file becomes the name of the event class. The recommended naming convention for event class files is: dce_server-name_class where class is a descriptive text that characterizes the event class. Event class files must be write-protected by the local operating system (that is, only administrators should have write access to these files). Audit clients read these files to maintain an event table in their address space. Optionally, an event class file can contain a SEP line. This line contains a list of prefixes of the event numbers in the file. The SEP line speeds up the scanning performed by the Audit clients. Audit clients which do not have events with one of the prefixes listed will not scan the event list. If the SEP line is not provided in the file, Audit clients will have to read the entire file to find out if the event class file contains any of their events. Empty lines are ignored in the event class file. Comments are designated by the number sign (#) placed before the comment text. The Event Class File Format The format of an event class file is: ECN=event_class_number SEP=prefix_1 prefix_2 ... # comments start with the number sign event_num- ber_1 event_number_2 EXAMPLES
Following is an example of an event class file for the event class ec_local_authentication: ECN = 0x00000001 SEP = 0x100 # AS_Request 0x00000100 # TGS_TicketReq 0x00000101 # TGS_RenewReq 0x00000102 # TGS_ValidateReq 0x00000103 event_class(5)