Overview: ECM suites often provide the ability to direct address and solve many business problems directly, however there are many more problems that cannot be directly solved by an ECM suite and, instead, require some 3rd party solution.
When native or reasonably inexpensive integrations between these solutions and the ECM repositories where the content should reside do not exist, then there are only a few options available:
Do nothing and leave the content unmanaged, unknown, and at risk.
Create bespoke integration solutions writing whatever modules, functions or code is required to accomplish the required integration. This option is almost always the most expensive, usually exceeding any existing 3rd party solution. It means long-term development, support, maintenance, and training. While this approach can lead to a superior solution, it is one that will almost always take longer than expected and be over budget.
Work locally and force the users to change the way they work, manually storing and retrieving the content from the ECM system using other tools like, for instance, WebDav or Windows Explorer. For some problems, this is the ideal solution when there are only a few users requiring the integration. However there is on-going training required to assure the integration over the long-term and there is a real risk that the ECM system may not get used 100% of the time.
Work locally and use scheduled tasks to synchronize content between local storage and ECM solutions. This loose integration approach requires almost zero training, limited development and long-term support and is easily maintained over time. The difficulty is in creating the synchronization solution; it too can often turn into a full-blown be-spoke application.
Areas Covered in the Session:
Problem space – a discussion as to where CLI and scripting fit within an enterprise
Powershell description – a look into relevant portions of powershell
ECM Integration – the meaning of; the choices available along with the tradeoffs associated with each type of integration
MS Integration – the meaning of; some examples of
File System Archiving / Synchronization example Integration Solution
Workflow Word Robot example Integration Solution
ECM content migration (ETL) example Integration Solution – SharePoint to Content Server
Automation / Task scheduling
Powershell / ECM Error Handling, Pitfalls and Gotchas
Speaker Profile: Dave Kinchlea
is a 25 year veteran in managing the growing content problem. He holds a Master of Science in Computer Science from the University of Western Ontario where he also worked in the core Information Technology administrative department. Being part of the team that brought the Internet to Canada, Dave has had an interest in content management for longer than the discipline has existed. Dave spent nearly 12 years, from 1998 through to 2009, working with Open Text Corporation defining and building out Enterprise Content Management tools and expertise. He is recognized around the world for his technological expertise in respects to ECM deployments having designed and helped organizations maintain some of the largest and most complex ECM systems in existence.
Click here to know more about : ECM Integration with Microsoft PowerShell