• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

Open Source Scanning For Documentum and Alfresco – Introducing OpenCapture

You are here: Home / Alfresco / Open Source Scanning For Documentum and Alfresco – Introducing OpenCapture

May 25, 2010

Over the years, TSG has worked with many different clients on projects that utilize a scanning tool to ingest content into a repository.  While products like InputAccel and Kofax are great, especially when dealing with centralized, large volume or bulk scanning models,  many clients desire a more quick and seamless approach that utilizes the web and cost-effective scanners for decentralized scanning environments.

TSG is proud to announce our first open source scanning solution for both Documentum and Alfresco – OpenCapture!

OpenCapture is a configurable web-based application that allows users to easily scan and upload documents directly into a content repository.  A simple interface provides intuitive user controls for scanning documents, performing image manipulations such as rotations and crops, and setting metadata.   Available metadata fields for document indexing can be configured based on the document type.

OpenCapture can be directly launched from Documentum Webtop and Alfresco Share.  The system detects the user’s current folder location and automatically uploads content to this location.  Once the scanning process is complete, the user can return right back to the view from which OpenCapture was initially launched.

OpenCapture uses the Dynamsoft Dynamic Web TWAIN ActiveX control to interface with the scanner hardware.  This allows users to control the scanner and manipulate images all without using separate scanner software.  The ActiveX control also removes the need to have the user upload scanned content to the application server before indexing to the Documentum or Alfresco repository.  The result is a seamless solution that takes the user from scanning and image manipulation to indexing to the central repository in one web-based interface.

To see demos of scanning documents for both Documentum and Alfresco, check out OpenCapture in the TSG Learning Zone!

Filed Under: Alfresco, Documentum, OpenCapture, Product Suite

Reader Interactions

Comments

  1. Reg its usage says

    October 13, 2011 at 4:00 am

    Hi We are trying to evaluate your product OpenScan But when we are trying to call the OpenScan through our browser it throws a Error saying that please support us

    Exception

    org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘openScanConfig’ defined in ServletContext resource [/WEB-INF/config/openscan-core.xml]: Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: org.apache.commons.jxpath.JXPathContext.selectNodes(Ljava/lang/String;)Ljava/util/List;

    Reply
  2. George says

    October 13, 2011 at 9:10 am

    It looks like you must have a conflicting commons-jxpath jar file in your classpath somewhere. OpenCapture requires the commons-jxpath-1.3.jar file that is located in the WEB-INF/lib folder. If you have a conflicting version of the commons-jxpath on your classpath somewhere, for example in Tomcat’s common lib folder, you would get this error.

    Reply
  3. Yan Duarte says

    January 17, 2012 at 11:04 am

    Hi, I am trying to use your product OpenScan but when i call the OpenScan in my browser it throws an error:

    type Exception report

    message

    description The server encountered an internal error () that prevented it from fulfilling this request.

    exception

    javax.servlet.ServletException: Servlet.init() for servlet openscan threw exception
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    java.lang.Thread.run(Thread.java:619)

    root cause

    org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘openScanService’ defined in ServletContext resource [/WEB-INF/config/openscan-core.xml]: Cannot resolve reference to bean ‘connectionService’ while setting bean property ‘connectionService’; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘connectionService’ defined in ServletContext resource [/WEB-INF/config/openscan-core.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: com/tsgrp/dfi/DfiException

    Do you know what can be wrong?

    Thanks,
    Yan Duarte.

    Reply
  4. George says

    January 17, 2012 at 4:18 pm

    Yan,

    From your error message it looks the the problem is that something is wrong with the connectionService bean definition. Can you double check that the connectionService bean is defined in the WEB-INF/config/openscan-core.xml file? Perhaps that bean definition was accidentally removed or commented out?

    George

    Reply
    • Yan Duarte says

      January 18, 2012 at 6:11 am

      I just can’t put the bean definition here, so i upload a print screen from it, you can see in the link: http://postimage.org/image/nr26e1r1z/

      Thanks,
      Yan Duarte

      Reply
      • George says

        January 18, 2012 at 10:02 am

        Yan,

        Your config looks correct. We’ve never seen this problem before, so I’m not sure exactly what the issue is. From your error message, it looks like it’s not creating the connectionService bean correctly. What application server are you using to deploy OpenCapture? Can you verify that the WEB-INF/lib and WEB-INF/classes folders deployed correctly and contain all of the files from our website download zip?

        George

        Reply
      • Yan Duarte says

        January 26, 2012 at 6:47 am

        Hello George,

        When i put the war files into the folder “…/tomcat/webapps/” and restart the tomcat application, Tomcat Web Application deploy automatically, after that i try to enter in browser with http://localhost/OpenScan and the error appears.
        I tried to do the deploy uploading the war file in the tomcat manager too, and get the same situation.

        I checked the files in OpenScan/WEB-INF and down in this message i put a tree of the folders.

        There is one thing that i have questions.

        There are two links to download OpenCapture, one for the application and other for the documentation.
        When i get the application and unzip it, there are OpenScan and OpenContent war files. There is nothing Inside OpenScan.war and when i try to put it on my server nothing happens.
        The other download link (documentation) has a folder of documentation and other folder with the same 2 war files (OpenScan and OpenContent), this OpenScan is the one that ‘works’, there is archives inside it, but when i try to open it in the browser i get the error message

        The question is: The right war file to use is the one that is inside of documentation download?

        Tree of content of WEB-INF folder:
        WEB-INF/
        –> classes
        |—-> config-details.xml
        |—-> config-picklists.xml
        |—-> config-scanner.xml
        |—-> config.xml
        |—-> log4j.properties
        |—-> messages-overlay.properties
        |—-> messages.properties
        |—-> OpenScan.properties
        |—-> tsgrp.properties
        –> config
        |—-> openscan-core.xml
        |—-> openscan-project.xml
        |—-> openscan-spring-config.xml
        –> jsp
        |—-> docProperties.jsp
        |—-> header.jsp
        |—-> login.jsp
        |—-> main.jsp
        |—-> prelude.jspf
        |—-> scanDocument.jsp
        |—-> sessionTimeout.jsp
        |—-> setupError.jsp
        |—-> unsupportedBrowser.jsp
        |—-> uploadSuccessful.jsp
        –> lib
        |—-> activation-1.1.jar
        |—-> activation.jar
        |—-> All-MB.jar
        |—-> ant-contrib-1.0b3.jar
        |—-> aspectjrt.jar
        |—-> avalon-framework-4.2.0.jar
        |—-> axiom-api-1.2.7.jar
        |—-> axiom-dom-1.2.7.jar
        |—-> axiom-impl-1.2.7.jar
        |—-> axis2-adb-1.4.1.jar
        |—-> axis2-adb-codegen-1.4.1.jar
        |—-> axis2-ant-plugin-1.4.1.jar
        |—-> axis2-clustering-1.4.1.jar
        |—-> axis2-codegen-1.4.1.jar
        |—-> axis2-corba-1.4.1.jar
        |—-> axis2-fastinfoset-1.4.1.jar
        |—-> axis2-java2wsdl-1.4.1.jar
        |—-> axis2-jaxbri-1.4.1.jar
        |—-> axis2-jaxws-1.4.1.jar
        |—-> axis2-jaxws-api-1.4.1.jar
        |—-> axis2-jibx-1.4.1.jar
        |—-> axis2-json-1.4.1.jar
        |—-> axis2-jws-api-1.4.1.jar
        |—-> axis2-kernel-1.4.1.jar
        |—-> axis2-metadata-1.4.1.jar
        |—-> axis2-mtompolicy-1.4.1.jar
        |—-> axis2-saaj-1.4.1.jar
        |—-> axis2-saaj-api-1.4.1.jar
        |—-> axis2-spring-1.4.1.jar
        |—-> axis2-xmlbeans-1.4.1.jar
        |—-> backport-util-concurrent-3.1.jar
        |—-> batik-all-1.6.jar
        |—-> bfopdf.jar
        |—-> certjFIPS.jar
        |—-> cglib-nodep-2.1_3.jar
        |—-> commons-beanutils-1.8.0.jar
        |—-> commons-codec-1.3.jar
        |—-> commons-codec-LICENSE.txt
        |—-> commons-collections-3.2.1.jar
        |—-> commons-configuration-1.6.jar
        |—-> commons-fileupload-1.2.jar
        |—-> commons-fileupload-LICENSE.txt
        |—-> commons-httpclient-3.1.jar
        |—-> commons-httpclient-LICENSE.txt
        |—-> commons-io-1.4.jar
        |—-> commons-io-LICENSE.txt
        |—-> commons-jxpath-1.3.jar
        |—-> commons-lang-2.3.jar
        |—-> commons-logging-1.1.1.jar
        |—-> commons-logging-LICENSE.txt
        |—-> configservice-api.jar
        |—-> configservice-impl.jar
        |—-> core-renderer.jar
        |—-> dms-client-api.jar
        |—-> fop-0.94.jar
        |—-> iText-2.0.8.jar
        |—-> jaxb-api.jar
        |—-> jaxb-impl.jar
        |—-> jaxen-1.1.1.jar
        |—-> jazzy-core.jar
        |—-> jdbc2_0-stdext.jar
        |—-> jdom.jar
        |—-> jsafeFIPS.jar
        |—-> json.jar
        |—-> jsr173_api.jar
        |—-> jstl.jar
        |—-> junit.jar
        |—-> log4j.jar
        |—-> mail-1.4.jar
        |—-> mail.jar
        |—-> mthdservlet.jar
        |—-> neethi-2.0.4.jar
        |—-> OpenContentCoreClient.jar
        |—-> open-overlay.jar
        |—-> OpenScan.jar
        |—-> regex4j.jar
        |—-> regexp.jar
        |—-> saxpath.jar
        |—-> spring.jar
        |—-> spring-webmvc.jar
        |—-> standard.jar
        |—-> tsgrp.jar
        |—-> wsdl4j-1.6.2.jar
        |—-> wstx-asl-3.2.4.jar
        |—-> xmlgraphics-commons-1.2.jar
        |—-> XmlSchema-1.4.2.jar
        |—-> xtrim-api.jar
        |—-> xtrim-server.jar
        –> openscan-servlet.xml
        –> tags
        |—-> autocompleteTextInput.tag
        |—-> beanForm.tag
        |—-> calendarTextInput.tag
        |—-> cascadingDropdown.tag
        |—-> searchForm.tag
        –> tlds
        |—-> tsg-web.tld
        –> web.xml

        6 directories, 118 files

        Reply
        • pmaccart says

          January 27, 2012 at 9:05 am

          Yan —
          The file listing you posted looks correct for the OpenScan war. From comparing what you have with what is currently available on our site, you may just want to grab a clean download — it looks like your webapps might have just been unzipped to the wrong locations.
          -Phil

          Reply
  5. Pathum says

    March 2, 2012 at 4:24 am

    Hi

    I’m also having the same problem. Did you find any solution to this.

    Pathum

    Reply
  6. George says

    March 2, 2012 at 9:21 am

    Pathum,

    For the two issues above, it appears the the first (method not found) is caused by a conflicting commons-jxpath-1.3.jar on the server’s classpath. For the second, it appears that somehow the download was corrupted and the solution was to grab a clean copy from our download page.

    Reply
  7. Raimundo Luiz Oliveira says

    March 28, 2012 at 3:20 pm

    I’m still waiting for a final settlement, there are two packages in the repository,
    1 – Documention – Error creating bean with name ‘openScanService’ defined in ServletContext resource [/ WEB-INF/config/openscan-core.xml]
    2 – Alfresco – Error: Exception fixing docBase for context [/ OpenScan]
    java.util.zip.ZipException: error in opening zip file
    java.util.zip.ZipFile.open at (Native Method)
    at java.util.zip.ZipFile. (ZipFile.java: 127)
    at java.util.jar.JarFile. (JarFile.java: 135)
    at java.util.jar.JarFile. (JarFile.java: 72)

    Reply
    • George says

      April 3, 2012 at 9:47 am

      Raimundo, please make sure you have a valid war file and be sure to deploy it to the correct location (ex: webapps folder in Tomcat). Are you trying to deploy OpenCapture for Documentum or Alfresco?

      Reply
  8. Greg says

    December 13, 2012 at 5:15 pm

    Is there any chance that OpenCapture will be updated to work with Alfresco 4.x? It seems like it is the best solution out there for my needs.

    Reply
    • George says

      December 13, 2012 at 9:31 pm

      Greg, since TSG is a consulting firm, we upgrade and improve our products as part of client projects as well as internal efforts, with client work taking precedence. If you would like to get OpenCapture working with Alfresco 4.x, you have a few options:

      1) Engage with TSG to implement connectivity to Alfresco 4
      2) Like all our products, OpenCapture is open source – you can download the source and make the necessary updates. Of course, we would love for you to contribute your updates back to us!
      3) We have this effort on our internal todo list, so it will be done at some point. But as I mentioned above, our client work take precedence, so most likely it will be done when a client project requires it.

      Reply
  9. Greg says

    December 14, 2012 at 4:09 am

    Hi George,

    thanks for your reply. Can you also tell me where can I find the connector for Alfresco? I have got openContent and openCapture but the documentation mentions another set of files with folders webscripts etc. I cannot find them anywhere in the file downloaded from SourceCode page. Is the Alfresco share connector not available anymore or have I just missed it somewhere?

    Reply
    • George says

      December 14, 2012 at 8:15 am

      Greg,

      The Share connector wasn’t fully tested before we released the Beta for OpenCapture on our downloads page, so that’s why it’s not included. If you want to take a look at it, you can fill out our license agreement here: https://tsgrp.wpengine.com/multimedia/Acknowledgement-Form.pdf and we’ll give you access to the source. I’m out of the office today, but I should be able to get you access on Monday.

      Reply
  10. Rajul Gupta says

    January 1, 2013 at 6:48 am

    Hi George,

    I also need Alfresco Share connector. Can you please provide us the access to source code?

    Reply
    • George says

      January 2, 2013 at 1:21 pm

      Rajul – see my response to Greg above.

      Reply
      • Rajul Gupta says

        January 4, 2013 at 2:49 am

        Hi George,

        Thanks for your reply. But i how should i send you agreement.

        Regards
        Rajul

        Reply
      • George says

        January 4, 2013 at 9:04 am

        Rajul – instructions for how to submit the agreement are in the PDF I linked to above.

        Reply
  11. Sergio says

    August 29, 2013 at 2:20 pm

    Hi, I am using alfresco community 4.2c, exists an alfresco share connector for this version?

    Reply
    • George says

      August 29, 2013 at 2:46 pm

      Sergio,

      We’ve deprecated this version of OpenCapture. The next version of our HPI product will have OpenCapture’s scanning capabilities embedded.

      Reply
      • Sergio says

        August 30, 2013 at 7:18 am

        Hi George,

        Thanks for your reply.

        Reply
  12. Sergio says

    September 2, 2013 at 4:16 pm

    Hi guys just installed HPI and wonder what the User and password default. Where can I set?
    thanks

    Reply
    • George says

      September 3, 2013 at 8:06 am

      Sergio,

      HPI uses the underlying repository, so when you’re on the login page, enter credentials for an Alfresco user (or Documentum user depending on your ECM platform).

      George

      Reply
      • Sergio says

        September 3, 2013 at 12:38 pm

        Thanks for the feedback.
        My Alfresco User is “admin” and password “admin”, this data inform the HPI login but invalid login error occurs. Where should I configure the HPI to recognize the user of Alfresco, I followed the instuctions installation file, please help me.

        Sergio

        Reply
        • George says

          September 3, 2013 at 12:47 pm

          Sergio – HPI uses OpenContent to connect to the repository. Make sure you have HPI configured to point to the correct OC base URL (in OpenContent.properties). Then, check the log files for both HPI and OpenContent.

          George

          Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • TSG Learning Zone Updated with HPI 2.1 Demos!
  • Alfresco Consulting – Documentum Disruptor #2
  • Microsoft Teams integration and the Alfresco Enterprise Viewer for Document Review
  • Alfresco Enterprise Viewer – Offline Annotation for Efficient Review
  • Redaction for AWS, Alfresco, Documentum and Hadoop – Bulk Redaction upon Ingestion or Migration
  • Suggested Redactions for Documentum, Alfresco or Hadoop using OpenRedact
  • ECM Roadmap – Thoughts on Planning for the Future
  • Documentum or Alfresco Reporting – Big Data to the Rescue
  • Top 5 Differences between Records Management and Document Management
  • Hadoop – Why Hadoop as a Content Store when Caching Content for ECM Consumers

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT