What?s Next For CEP Vendors?

Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News What?s Next For CEP Vendors?
# 1  
Old 01-28-2008
What?s Next For CEP Vendors?

by Larry Barrett, InternetNews.com, January 25, 2008 IBM on Wednesday made its first significant foray into the emerging but relatively low-profile complex event processing (CEP) market with its acquisition of privately held AptSoft. CEP applications aggregate information from corporate databases and applications in real time and applies rules to discern patterns and events that otherwise would go [...]

Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

EPTS4: The Future, from the Vendors

vincent 09-20-2008 07:20 AM EPTS4 day 2 started with a a keynote by Susan Urban of Texas Tech Uni on a Roadmap for Research Directions. Susan comes from the active database world and was talking about fun stuff like distributed event processing agents and so forth. Susan emphasized... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. UNIX for Advanced & Expert Users

How to avoid vendors having root access ?

Hi gurus: We have several production *nix boxes from vendors and the policy here has been to give them root access as and when they require ( upgrade, troubleshooting the application, etc). Sudo is implemented on the systems but vendors cannot upgrade the application cause it says that the root... (2 Replies)
Discussion started by: geomonap
2 Replies
Login or Register to Ask a Question
EXCHANGE2MBOX(1)					     OpenChange Users' Manual						  EXCHANGE2MBOX(1)

exchange2mbox - Convert Exchange mailbox to mbox file SYNOPSIS
exchange2mbox [-?|--help] [--usage] [-f|--database PATH] [-p|--profile PROFILE] [-P|--password PASSWORD] [-m|--mbox FILENAME] [-u|--update] [-d|--debuglevel LEVEL] [--dump-data] DESCRIPTION
exchange2mbox provides a way to synchronize an Exchange mailbox with a mbox file. The tool is developed so it only retrieves mails not already stored in the message ID index database and reflects changes back to the Exchange server if the local message copy are deleted. OPTIONS
--database -f Set the path to the profile database to use --profile -p Set the profile to use. If no profile is specified, exchange2mbox try to retrieve the default profile in the database. If no default profile has been set, exchange2mbox returns MAPI_E_NOT_FOUND . --password -P Set the password for the profile to use. This can be omitted if the password is stored in the profile. --mbox -m Set the mbox file full path --update -u Synchronize the local mbox file with the remote Exchange server mailbox. --dump-data Dump the hex data. This is only required for debugging or educational purposes. --debuglevel LEVEL -d Set the debug level. EXAMPLES
Create/Update the mbox file and indexes within the profile database: exchange2mbox Update the Exchange mailbox and indexes according to the changes made to the mbox file. exchange2mbox -u REMARKS
If no mbox file is specified, one will be automatically created in $(HOME)/.openchange/mbox . If you are using the default profile data- base path and have set a default profile (using mapiprofile --profile=profile_name -S ) you do not need to specify these parameters on the command line. AUTHOR
Julien Kerihuel <j.kerihuel at openchange dot org> Brad Hards <bradh at openchange dot org> OpenChange libmapi 0.8 2008-11-14 EXCHANGE2MBOX(1)