Posts Tagged 'CMIS'

Ephesoft CMIS Export plugin using Alfresco’s Aspects

Ephesoft is a great tool to process scanned pages, construct documents again (no separator pages anymore), gather metadata, and read barcodes and line items. Next to that it is build on a wide diversity of open standards. CMIS is one of them, and it is a perfect standard to use to get the document and metadata as a whole to a content management system of choice (as I described before). The major document management solutions implemented this open industry standard in their latest releases. The ‘biggest’ downside is the CMIS standard is bound to Document Types being transfered. Alfresco is focused on the concept of an Aspect, a bundle of metadata and behavior that one could assign to any object. Alfresco has created an CMIS extension that supports these Aspects. This blog post describes how to use this extension to allow Ephesoft to export Alfresco Aspects using CMIS. Continue reading ‘Ephesoft CMIS Export plugin using Alfresco’s Aspects’

Ephesoft and Alfresco in one Tomcat instance

In the past I already tried to get Ephesoft (The open source, web based mailroom automation tool)  and Alfresco (the open source content management solution) running in a single Tomcat instance. On Ubuntu, and starting with the Alfresco instance, copying Ephesoft into there. For all kind of distracting reasons (among others writing 4 blogs simultaniously) this failed. This blog will describe a successful attempt to install both into a single Tomcat on Windows.

Why? Because it seems convenient for a demo, not to have to start a VMWare image next to two applications.
First, install Ephesoft. I did an Enterprise install (2.0.0.2) against a previously installed MySQL (running as a service on my laptop). We are going to use the Tomcat as installed and configured by Ephesoft. Continue reading ‘Ephesoft and Alfresco in one Tomcat instance’

Open Source scanning with Ephesoft and Alfresco

A document management solution is good in managing ‘content’, control access, process the flow of content, perform transformations, give overview and control. But how does the content enter the system? One stream into the system can be fully digital; integrations with other IT systems, from email, from the office environment. However, there is a world of paper to manage as well. And how does the paper end up in a DMS? Scanning.

Wouldn’t it be great to have a full blown open source stack from scanning, through validation and indexing, pushed into the DMS and managed until it can be destroyed? Now you can, and Ephesoft is the entrance! Continue reading ‘Open Source scanning with Ephesoft and Alfresco’

Configuring Ephesoft and Alfresco for CMIS integration

This blog is the result of my discoveries in integrating Ephesoft, the open source mailroom automation, and Alfresco, the open source document management solution. Ephesoft is able to export to a CMIS-enabled repository, and Alfresco is the CMIS repository, and both are open source! In this blog I configure a default install of Ephesoft (using the Ephesoft installer) and a default install of Alfresco Community (using the installer). I installed each application on a different VM, I don’t like to make a mess of my laptop, and don’t want to spend time on getting both to run smoothly on a single VM image. Continue reading ‘Configuring Ephesoft and Alfresco for CMIS integration’

Activiti, the enterprise grade open source BPM promise

(Find the Dutch version in this article)
(Find the Spanish version in this article)
This article has been published before on allesovereim.nl

 

Some time ago, Alfresco, Signavio and Camunda started Activiti, an open source alternative for enterprise BPM. The

first question that crossed my mind was “why a new BPM engine”? Basically, there are some reservations about the jBPM Alfresco implementation in the areas of developing and controlling processes. Alfresco had more reasons to reconsider an (embedded) BPM engine. There are customer considerations against limitations to the LGPL license (or the perception thereof) which is why the Activiti project is developed under the Apache 2 license.

Vision

JBPM is a ‘technically oriented’ BPM engine. The Activiti project’s vision is that it should be a lightweight engine, easy to use (for Java developers) and that ‘workflow’ could also be social. Remind the could be. The Activiti project does not prescribe how an organization should use BPM, but it wants to facilitate collaborating around the business process.
Traditionally, the development of (business) processes is the ‘analysts’ domain. This role develops process diagrams, defines the flow of jobs, defines to what role a job is assigned, and what automated steps take place. Next in line, the ‘developers’ create “executable code” of it. Activiti has a number of elements in it which can facilitate collaboration among the roles involved like analysts, managers and developers.

First, Activi utilizes BPNM2.0, the now widely accepted open standard for process modeling. The beauty of this 2.0 version of the standard is that next to the schema language, the underlying defining XML standardized as well. Activiti can directly execute this XML. This has the advantage that the analyst and the developer work on the same process scheme and therefore underlying XML. They can read each other’s work, and actually work on the same schema’s. That will do a lot for the effectiveness of communication. Activiti also provides an additional module where all roles involved are facilitated to collaborate in a ‘2.0’ style, and improve the process of developing business processes, and improve existing ‘running’ process definitions. I will elaborate on this later in this article.

Continue reading ‘Activiti, the enterprise grade open source BPM promise’

CMIS 1.0 approved by OASIS

“The OASIS Content Management Interoperability Services (CMIS) TC has submitted the following specification, which is an approved Committee Specification, to be considered as an OASIS Standard:

Content Management Interoperability Services (CMIS) Version 1.0”

Meaning, we have ‘SQL for ECM’. Now we can query (and update) any repository cross vendor, cross programming language. Alfresco (one of the contributors to the new standard) is one of the early (Open Source) vendors to provide the full set of features already. The 3.3 release of Alfresco is shipped with the approved 1.0 version, the 3.2 versions have been shipped with the latest version available at their release dates.

The standard is created as a joint effort of Microsoft, IBM, EMC, Alfresco, OpenText, SAP and Oracle, the bigger players in the ECM field. Hopefully all will stick to the standard and make life easier. I am looking forward to investigating Drupal on top of Alfresco using CMIS!

See: http://lists.oasis-open.org/archives/tc-announce/201004/msg00000.html