Tag Archives: EMC

Big Men on Content

Hopefully you’ve already been reading the musings of Lee Dallas and Marko Sillanpaa over at their Big Men on Content blog. If not, I recommend that you give them a read; I do, regularly.

Anyway, this post is a belated acknowledgment of the fact that both Lee and Marko are EMC colleagues now. Marko joined EMC last quarter and is focused on enabling strategic SI’s to develop solutions on top of the CMA platforms. Marko also writes for CMSWire. Although not a package deal–“might have exceeded weight limitations,” to quote Marko*–, Lee joined around the same time and is part of the same group supporting our system integration partners.

So, welcome Lee and Marko to the EMC team!

* Reference the BMoC tagline and about panel for context, please. :-)

Intelligent capture

Today, EMC announced new releases of EMC Captiva products (i.e. EMC Captiva InputAccel 6.0 and EMC Captiva Dispatcher 6.0). I want to address the benefits of service-oriented infrastructure related to capture as embodied by these new releases.

The big deal with SOA and InputAccel 6.0 (IA6) is the connectivity it enables with other enterprise applications.

Capture depends heavily on validation of the captured data so access to systems that can supply information based on an extracted value or can perform the validation of extracted values is necessary. Service-orientation in IA6 lets capture be part of a company’s composite TCM applications.

Prior to the release of IA6, capture systems “connectivity” was restricted to ODBC, dropping files on file shares, and/or duplicating validation rules in software.

Another potentially big deal is the exposure of Captiva’s capture functionality to other applications (e.g. a web service for importing data into Captiva).

Today Captiva takes (captures) data from scanners, email, fax machines and legacy systems using specialty importers and file shares. Using web services will reduce complexity by allowing for a single method to be used to take in data from all kinds of systems.

Capture processing tends to occur in large batches; so, the “queue” behavior of a file share is useful. However, it lacks a handshake when the data has been picked up.

A web service would be more likely to be used by an interactive process or could be used as a call-back with the file share method to give a handshake.

It will be interesting to see how service-orientation within capture takes hold.

I want to thank my colleague, Clay Mayers, Captiva CTO, for contributing to this post. (Ah, another potential CMA blogger target… :-) )

Atmos

On Monday EMC announced Atmos. While I was in flight, returning from a short vacation, a number of my EMC colleagues blogged about this new offering. I’d like to draw your attention to their posts as follows:

  • Steve Todd first offers, among other things, a concise definition of Cloud Optimized Storage (COS): “global storage with a policy focus.” He continues in a follow-up post by delving into more details concerning the “special sauce” of Atmos (i.e. its use of global policies). I have the strong sense that more posts will come from Steve regarding Atmos in the not too distant future, too.
  • Barry Burke: “Atmos seeks to blaze a new approach to “cloud” storage (oh how I hate that term), to create a global storage platform that is not only cost-effective to install and grow, but extremely efficient to operate as well…set-it-and-forget-it cloud storage. And trust me, if your business thinks in petabytes or even exabytes of unstructured data, you’re already looking for a totally new storage paradigm, because nothing – and I mean NOTHING – built on current commercial file systems or databases will handle that kind of storage.”
  • After some humorous precursor posts, Mark Twomey dives into Atmos by relaying his conversation with one of the Atmos architects, Dr. Patrick Eaton, who was also involved in OceanStore.
  • Dave Graham talks about what Atmos is and is not and then covers the underlying architecture of Atmos.
  • Last but not least, Chuck Hollis provides his perspective on Atmos, drawing in other commentary from the web in the process.