Armedia Blog

Archive for December, 2009

Migrating CAD Drawings into Documentum

December 17th, 2009 by Rahul Rana

Anyone who has ever attempted a data migration knows that there is no such thing as ‘a smooth transfer of power’, as it were. From learning both the legacy system and the new system, business processes, data clean-up, data mapping, deciding between existing tools and creating new ones, there is a lot to keep track of to ensure that what you have at the end matches what you started with.

Migrating CAD engineering drawings poses its own set of unique challenges. AutoCAD and MicroStation drawings can internally have references to other drawing files that exist within the content management system (or file system). When moving these files over to a new system, care must be taken to ensure these references are maintained.

Sword CADtop is a tool that provides users access to CAD drawings that are stored in a Documentum repository directly from within AutoCAD or MicroStation. It gives the user the ability to check in/out drawings, browse, search, view documents and attach reference drawings that exist in the docbase. CADtop maintains reference information by updating the links within the drawing and storing this information in a registered table.

CADtop also provides an import tool that can be used to migrate documents into the Documentum system. It handles importing of documents of multiple types, such as .pdfs, .docs, .tifs, etc. along with the drawing formats, .dwg and .dgn. It is a very simple to use command line tool, but it has its limitations. It can only handle importing up to around 5000 files at a time. However, this can be overcome by creating a batch script to automate the copying of sets of files to a temporary directory and running the import tool.

The import tool uses an XML configuration file to determine the object type, folder path to import from and cabinet/folder to import to. However, those are the only properties you can set. The import tool has no way to attach meta-data from a database to content files being imported. A way around this is to make sure each file has a unique name, then import the files, then using a DFC script, update the properties of all the objects in the docbase from an XML file (for example). This works well as long as all the filenames are unique in the first place, or not drawings with references. If filenames are not unique, then you would have to rename the files, which means the filenames will no longer match the drawing’s internal reference links.

The import tool provides you with a switch that lets you run it in attach reference mode. This allows you to pass an Excel file which consists of a table of parent object IDs, child object IDs and reference filenames, so that you can resolve references within drawing files after they’ve been imported into the docbase. Thereby allowing you to use a tool such as Caliente (Shameless Plug™) to import the drawings into Documentum and update the properties. Then create the Excel file with all the references and run the CADtop import tool to attach them.

The end result will be that when you open one of these drawings through AutoCAD, CADtop will automatically pull out all the references from the Documentum repository and display them, just as in the legacy system.

Living in the clouds…

December 9th, 2009 by Jim Nasr

It wasn’t too long ago when “living in the clouds” sparked visions of rolling hills, untethered joy, Julie Andrews and other dreamy and whimsical sights and sounds in my mind. Maybe there is still a time and a place for that—as Bill Cosby used to say, those of you with children, you’ll understand! But in the world of business, and ECM, there is no longer a place for it…

I was fortunate to attend the Microsoft Professional Developer’s Conference in LA as a guest of Microsoft’s last month. Two things hit me right off: (one) pretty much every person in attendance blogged, facebook’d and tweet’d—my apologies in advance to OED—seemingly all at pretty much the same time! (two) Microsoft’s cloud, Windows Azure, is more real than not…as are some others. Better wake up the brain cells.

To me, the truly impressive thing about Azure was, well, not its infrastructure, scale, configurability. Though impressive enough, they’re the annonymous linebackers to the superstar QB—the dude you really pay to watch. And he to me, was ability to develop and deploy using Azure. Seemlessly developing against a “cloudy” SQL server like it’s sitting on your very own laptop (actually better because it won’t kill your laptop in doing so!), writing and compiling your code of choice (give or take…though including Java through Eclipse), and deploying using something other than ANT and a thousand man-hours. Lots of exciting stuff!

This rhetoric though really is not about Azure, nor am I in any shape or form an expert in it. And, besides Microsoft, Amazon, IBM, Dell, EMC and a whole bunch of other folks are in various states of making noise in cloud computing. Watch for it. It’ll impact all of us.

What this rhetoric is about is ECM in the cloud. Hosted ECM or ECM SaaS has, of course, been around for a number of years already. There are a number of good success stories around. Just see SpringCM, WordPress or even Salesforce.com…the lines between managing structured and unstructured content are awfully blurry these days. Are these true examples of cloud ECM? Perhaps. Or maybe the definition is still evolving.

The days of the multinational running a full-blown, multi-purpose ECM platform on a cloud-ready “traditional” ECM toolset (take your pick: Documentum, Filenet, Oracle, Sharepoint, Alfresco, et al) is not far off. There are some challenges left for sure. A little technology. A lot inertia.

Public or private cloud? Oracle or SQL? Java or .net? Or maybe, who cares? Our cloud challenge may well become how to ask more relevant questions to get more useful things done faster, better.