Author:


“Content Enabling” your 3rd party Applications with Crafter Rivet

Posted by on October 29, 2012

This article covers the various ways you can integrate your 3rd party applications with content managed and deployed by Crafter Studio and Alfresco.

Before we dig in to the specific approaches let’s take a quick look at the high level architecture of Crafter Rivet.

The architecture for Crafter Rivet is decoupled.  This means that by design your authoring and delivery infrastructures are separate infrastructure.  With Crafter Rivet authors work in a safe environment equipped with the tools they need to create and manage content.  When content has been approved via workflow it is then and only then published to entirely separate production environment where your live audience can access it.

We have put this architecture in place for several reasons:

  • Authoring and delivery systems serve different purposes and audiences and thus they have different SLAs, security, performance requirements and so on.
  • By decoupling the delivery environment we allow an implementation to use the authoring (Crafter Studio) and delivery (Crafter Engine) components independent of one another.  We have seen several cases where only Studio or Engine was used to meet specific need.
  • By decoupling the delivery environment we natively enable multi-channel publishing.

As a direct result of its architecture, Crafter Rivet, through its authoring component known as Crafter Studio can be used not only to manage content served directly by a Crafter Engine environment but also to 3rd party systems.

Now that we have architectural context, let’s take a look at a number of approaches for content enabling your 3rd party applications using Crafter Rivet.

Content Enable Your Existing Application via Crafter Core

At the heart of Crafter Engine is a Spring MVC application integrated with a middle-ware library we call Crafter Core.  Crafter Core is the main integration between the delivery tier and Alfresco. The Crafter Core library provides services that understand how to consume content (xml) and assets published Crafter Studio and Alfresco and to make them available to your application through a service oriented architecture.

To illustrate this architecture consider the diagram on the right which demonstrates this model though the architecture of Crafter Engine.

While Crafter Engine is constructed with Spring MVC and a Freemarker based presentation tier, Rivet Logic has previously content integrated many platforms including:

  • JBoss Seam & JSF Facelets / Spring Bean Framework
  • JSP / Pojo / Spring Bean Framework
  • JRuby / Spring Bean Framework
  • Quercus PHP / Spring Bean Framework
  • Grails / Spring Bean Framework

All that is required for integration is that you include the Crafter Core library, properly instantiate the content services and then tie the services to the view layer either directly or through your controller layer.  If you choose to use Spring Bean factory with in your application, instantiation is all but taken care of for you by existing Spring context files which are packaged with-in the jar.  You can find the binaries for the jar as well as Maven package details here.

This type of integration is typically done for existing applications which require deep integration with content and where there is a need to have exact control of the placement and presentation of the content across the entire application.

Content Enable your application via Crafter Engine’s ReST APIs

Crafter Engine provides access to content, metadata and structure through a ReSTful API.  You can find documentation for this API here.

As we can see from the diagram above the architecture uses Crafter Engine to provide the content services for content deployed from Alfresco which is then surfaced with in the 3rd party application via ReSTful API.  The 3rd party application may consume the ReSTful services on either the client layer (via JavaScript) or from with in the application.

This architecture is usually see when lightweight development is required and/or when it is adventitious to create a solution which can be integrated on one or more sites via the same code base.

When To Serve Content Directly From Alfresco

There is no hard and fast rule about when to serve your content to your application or website directly from Alfresco and when you should not.  Because Alfresco is an enterprise class content platform we typically find that it is the system of record for many different types of content including web, documents, records and so on.  For this reason we also find Alfresco is typically found behind one or more firewalls when the installation is on-premise.

When your site serves content from Alfresco directly you create a dependency on Alfresco in doing so you link the SLA (Service Level Agreements) of both your site/application and Alfresco.  This approach may have an impact to your IT requirements and infrastructure, licensing, and security. The decision to undertake this approach needs to be made deliberately with these factors in mind.

The main use case we see for applications and in particular applications pulling content from Alfresco directly centers around document management like use cases typically with-in an intranet.  When surfacing documents and interacting with workflow it is natural to link directly to the repository.

If you do decide to content enable your application this way there are several mechanisms for interacting with the repository:

  • Via custom web scripts: Using Alfresco’s web script facility is it possible to construct extremely lightweight, purpose built services for your 3rd party application.
  • CMIS (Content Management Interoperability Standard): Alfresco has extensive support for CMIS standards based ReSTful interface.
  • RAAr (Remote Alfresco API rivet): RAAr is a remote interface that provides your Java based applications with the exact same interfaces Alfresco provides for in-process integration.  You can learn more and download RAAr here.
  • File System projection: For simple integration you can read and write to and from Alfresco as if it were a standard file system.  Out of the box Alfresco supports the following file system projections:  CIFS / Shared Drive, FTP, WebDAV

Extending Crafter Engine with Java backed functionality

Posted by on October 06, 2012

Crafter Engine is the high-performance website / web app delivery engine for Crafter Rivet Web Experience Management. Out of the box Crafter Engine ships with support for many of the types of engaging functionality you have come to expect from a WCM/WEM platform.  However, there are times when we want to add additional capabilities to integrate with internal and 3rd party systems to meet specific business objectives.  In this article we’ll demonstrate how you can create Java backed plug-ins for Crafter Engine.

To illustrate the integration process we’ll integrate a simple RSS reader based on the ROME RSS processing library
You can download this example (and others) at the following SVN location: https://svn.rivetlogic.com/repos/crafter-community/ext/engine

To begin let’s start with some background on Crafter Rivet, Crafter Engine and how a plug-in is organized structurally:

Crafter Rivet

Crafter Rivet is web experience management solution based on the Alfresco Content Management platform with a de-coupled architecture.  This means that the authoring environment and the production delivery environment are separate infrastructure integrated by workflow and deployment from authoring to delivery.  Crafter Rivet components power some of the internet’s largest websites.  A decouple architecture makes things easier to support, more flexible and very scalable.

Crafter Engine

Crafter Engine owes its performance characteristics to its simplicity.  Content is stored on disk and is served from memory.  Dynamic support is backed by Apache Solr. At the heart of Crafter Engine is Spring MVC, a simple, high performance application framework based on one of the world’s most popular technologies: Spring framework.

What is a Crafter Engine Plug-in

A Crafter Plug-in is a mechanism for extending the core capabilities of Crafter Engine, the delivery component of Crafter Rivet. Plug-ins allow you to add additional services and make them available to your template / presentation layer.

An example plug-in as we suggested above might be an XML reader which would function as specified below:

  • The plugin would expose a in-process Java based service like Feed RssReaderService.getFeed(String url)
  • Your your presentation templates would then simply call <#assign feedItems = RssReaderService.getFeed(“blogs.rivetlogic.com”) />

Anatomy of a Crafter Engine Plug-in

You will note from the diagram above that plug-ins are simple JAR files that contain both Java code, configuration and an Spring bean factory XML file that loads and registers the services with Crafter Engine.

Loading the plug-in

1. When the container loads the Crafter Engine WAR the shared classes lib folder is included in the class path.

2. When the Crafter Engine WAR starts up it will scan the class path for its own spring files and any available plug-ins. At this time the services described in the Spring bean XML file with in your plug-in will be loaded. Your service interfaces are now available in the presentation layer.

Interacting with your service

A. The user makes a request for a given URL

B. Crafter Engine will load all of the content descriptors from disk for the page and components needed to render the specific URL. Once the descriptors are loaded the templates for the page and components will loaded from disk.

C. The templates may now call your service interfaces to render from and interact with your back-end code. Your Java backed service may then do whatever it was intended to do, returning the results to the template for processing. Once complete, the responses are then returned to the user in the form of a rendered web page.

A simple Example

Now that we have a bit of background, let’s get down to the nuts and bolts of the matter and build, install and configure our RSS reader integration.

The Java Service

/**
 * Reads a RSS or Atom feed from a specified URL and returns a data structure that can be accessed from a template.
 */
public class RssReaderService {

    public SyndFeed getFeed(String url) throws IOException, FeedException {
        SyndFeedInput input = new SyndFeedInput();
        XmlReader reader = new XmlReader(new URL(url));

        try {
            return input.build(reader);
        } finally {
            try {
                reader.close();
            } catch (IOException err) {
                // handle error
            }
        }
    }
}

The Configuration

/crafter/engine/extension/services-context.xml:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.1.xsd">

    <bean id="rssReaderService" class="org.rivetlogic.crafter.engine.rss.RssReaderService" />
</beans>

Packaging and Install

The compiled class and spring configuration file must be found in the class path.  To facilitate this we build these objects and their dependencies in to a single JAR file.  You can find the build process for these at the SVN location above.  Place the JAR file that is produced by the build process in to your shared class path for example: /TOMCAT-HOME/shared/lib and restart the application.

Now that you have restarted the application your service is available to your presentation layer.  This means that in any template you can now add the following:

<#assign feedItems = RssReaderService.getFeed(“blogs.rivetlogic.com”) />

Using the Plug-in:

Web Ninja: Create a RSS Feed Component for Authors

Create a new content type as a component:

Create a template for the RSS Widget by clicking on the type canvas and editing the template property:

Author: create and configure a RSS Component

Modify the component properties through the content type form:

And insert the widget in to a web page:

Save and close and the configured component is now showing on your web page!

Resources for Crafter Rivet – Web CMS for Alfresco 4

Posted by on April 16, 2012

Last week was a busy week for those of us working on Crafter Rivet, the WEM/WCM extension for Alfresco 4.0.  We’re extremely excited about this release and are busy scheduling events and demos as word is starting to get out!

You can download Crafter Rivet here:

If you missed our Webinar last week that was co-hosted with Alfresco you can check it out here:
http://www2.alfresco.com/Crafter0412

For existing Alfresco WCM customers on Alfresco version 2 and 3 using the AVM based solution, we’ve put together a couple of blogs to help you think about your migration to Alfresco 4 and the core repository:

For everyone who wants to learn more about this exciting and powerful open source solution for web content and experience management that sits on top of Alfresco, the world’s most open and powerful content management platform, we’re hosting a Crafter Rivet Roadshow in a city near you in May!  Come on out for content packed presentations, demonstrations, Q & A and free lunch!

Sign-up for the Crafter Rivet Roadshow here!

Crafter Roadshow Dates:

San Francisco
Tues. May 8

Los Angeles
Wed. May 9

Chicago
Tues. May 15

New York
Wed. May 16

Boston
Thur. May 17

Washington DC
Tues. May 22

Alfresco User Group: Boston

Posted by on April 12, 2012

We had a strong and turnout with a pretty diverse set of Alfresco customers, community members and partners at tonight’s Alfresco User Group for New England (hosted in Boston.)  Thanks to all who turned out for the event!  Also a special thanks to Alfresco’s Gavin Nathan for helping to pull the event together, kicking off the evening and for the drinks afterwards!

I presented on the new Alfresco 4 Architecture and improvements to Alfresco Share application as well as Crafter Rivet; a 100% open source WEM solution built on top of Alfresco 4′s core repository. The meeting was held in an informal setting with a lot of great discussion and Q & A.

Most importantly we had a lot of face to face time to talk shop on Alfresco technology and how each of us are putting it to good use.  It was a blast.

If you are in the Boston area please sign up for the Alfresco User Group for New England.  We’re off to a great start this year and we’d love to see you at our next meeting!

Web CMS on The Alfresco Core Repository (Part 2 of 2)

Posted by on April 10, 2012

In yesterday’s post we covered the fact that Alfresco stopped selling the AVM based WCM solution to new customers.  Existing customers using the AVM based approach will continue to receive support until the AVM reaches end of life status.  New customers looking to Alfresco for WCM/WEM capabilities who read this will naturally wonder what is the approach to WCM on Alfresco.  Existing customers will want to know how to migrate off the AVM and in to Alfresco’s core repository.

As we have seen in yesterday’s post, the core repository has had the benefit of continuous innovation through which it has grown as a platform now capable of supporting use cases critical to WCM/WEM with key features like remote file deployments and form based content capture.  Along with features clearly directed at the WCM use cases, the core repository is host to an amazing array of features and capabilities that make it ideal for all manner of enterprise management, WCM/WEM included.

At Rivet Logic we have made a significant investment in a web content and experience management extension to Alfresco that we call Crafter Rivet. Crafter Rivet is a 100% open source,  full featured application that powers 100s of websites and has over 40 man years of development effort invested in it. Initially Crafter Rivet’s authoring and management capability was based on the AVM. When Alfresco made the decision to direct the full force of its innovation on the core repository we knew it was time to covert. Just released, Crafter Rivet 2.0 is 100% based on the core repository, Solr search and Actviti workflow for Alfresco 4 CE and EE.  Making the switch from the AVM to the core repository required a deep examination of our use cases and the features we would have on hand within the core repository.

Now that we have a background understanding of both the AVM and core repository features we discussed yesterday it is time to look at the use cases that the AVM was designed to address.  We will discuss the use case and how these gaps were addressed by Crafter Rivet.  Let’s get started!

Use Case: Sandboxing
As described in yesterday’s blog, sandboxing is a feature but there are use cases that drive this feature. In a Web CMS context we have times when we need to modify templates, CSS and other assets that have far reaching effects on our sites. There are three common use cases that point to sandboxing:

  • Development:  As a developer I want to work with a template, a CSS file, a JavaScript library, etc. without worrying that the bugs I will inevitably create will interfere with the rest of the teams ability to produce, manage, preview and publish content.
  • Timing: On websites of significant size and complexity, there are often times when projects are created to update the look and feel of the site.  These projects with future delivery dates need to be able to take place without interfering with daily publishing.  Further, it’s important that the project be able keep up with on-going updates to reduce the headache of last minute merges.
  • Playground:  Sometimes we just want to play.  Sandboxes allow us to enable team members to innovate and play around without fear of impacting the live website.

It’s clear that the ability to sandbox (or branch/merge) your website code base can be pretty handy. In my mind there are several key questions:

  • Is the support for this use case a “must have” for my specific environment?  How often do I run in to the use cases above?
  • What granularity of sandboxing do I need?

Many popular Web content management systems do not natively support sandboxing. In a lot of cases the need for the branch merge capability is handled through the development and deployment process. In general I think it safe to say this feature is a rather strong “nice to have” unless you have an site with look and feel components which are literally being constantly updated and where the traditional development process would add too much time to the effort.

When you do need sandboxes the next question is granularity and how sandboxes are used. The AVM UI dictates sandboxes for each user. In my experience accumulated over many Alfresco WCM engagements; is that this was too fined grained for the needs of most engagements.  Most users want to work directly in context with other users.  They need basic locking on individual assets to keep work safe during their edits but they don’t require an entirely separate and parallel universe.  The ability to create a sandbox ad-hoc for a specific purpose maps more directly to the needs we see on the ground. In other words, a sandbox is too granular but a sandbox for a project to update the look and feel of the entire site where users could work together would more aptly address the kind of needs we see.

Crafter Rivet starts with the first finding, that sandboxing is not a “must have” feature and that in-fact when it is applied it should be done so to facilitate specific projects and specific ad-hoc needs. If you look at the way we have structured our content in the core repository you will see we have left room to support one or more draft copies of the site.  In v2.0 we do not support layering in the default configuration; however, Crafter Engine, our content delivery and preview tier, is able to sit over top of multiple hierarchical stores and present them as one store much in the same way the AVM did.

Use Case: History and Reversion in a Web CMS Context
As a user, when I want to preview a version of a specific asset, let’s say a page,  I want to see the page as it was on that day. That means I want to see exactly the same components and assets (images, CSS, js etc) as they were on that given day.  This is a real challenge in the core repository because there is no native support linking assets together under a common version; each asset is individually versioned and the links between objects (associations) do not capture version.

Now to be honest, I have simplified the problem a bit to make a point.  I said that pages, for example, are compound assets and that you are always interested in seeing their dependencies at a given point in time.  This is often the case when we’re talking about images and components that are specific to the page but it’s not really the case when we’re talking about shared assets like templates, CSS, JavaScript, and shared components and shared collateral.  Think for a moment about why users want to look at and ultimately revert to previous versions of content.  They are doing so either:

  • In the short term because they have made a mistake, or
  • in the long term because they need to revert messaging to a previous point in time.

In the first instance there is likely to be no issue.  Common assets are likely going to be the same as they where at the point in time of the version.  However, in the second case, we really want to see the old content in the context of the current templates, etc.  If we revert, it’s to get the older content, but we’re going to deploy it in the context of the latest look and feel of our site.

Handling versioning in Web CMS is a must have, must do capability.

In Crafter Rivet we considered these use cases fully and drew a distinction between two types of relationships.  Those relationships which are page only  and those which are shared commonly amongst other objects in the system.  When you revert a page or any other object, those relationships which are “page only” will revert to a point in time, while other relationships that are common will continue to align to the latest version of the asset.

To accomplish this we leverage both the native versioning capability of the core repository as well as file organization and patterns.  In short, we organize page-only assets in folder structures that represent the page. Page objects are given names that are based on a hash of the object to guarantee a unique name which means in effect that the versioning of the page only object is “horizontal” in the repository. By horizontal I mean that a new file path is used rather than relying on the version store.  Shared objects like pages or other common assets are stored regularly and rely on the native versioning support.  If you revert a page you will revert to an a state where the page points to a different set of file / file paths — achieving a solution for both use cases we mentioned above.

Snapshots
There are several Web CMS use cases that could require snaphsots and version diffs.  For example, some websites have compliance related issues and thus must maintain versions of their sites so that in the event of a dispute over information communicated via the site they can easily prove what the site looked like at a particular moment in time.  The question for snapshots is:

  • Is this something your organization must have?
  • And if so, is it something that the repository has to do for you?

Our experience shows that this feature, for the general market, is a nice to have.  Most customers don’t take advantage of this capability.  When we looked at this capability in Crafter Rivet, we decided it was not important to support natively within the repository itself.  If a customer needs a snapshot every day we simply include a deployment target that would produce a snapshot.

For those wondering about snapshot rollback; our experience has shown that this particular feature is really not relevant to most customers in day to day operation.  The feature has come in handy as a mechanism for bailing out people who have made sweeping changes to a site (100s of files) and deployed them with little or no QA only to find a broken website after the fact.  In such a case, snapshotting a rollback is a life saver.  With a click of a button you can revert 100s of files.

Crafter Rivet, by design is 100% file based. In such a crisis scenario, a simple file based backup could be used to restore a Crafter Rivet based site to a former state.  In the repository, you are unlikely to desire an actual rollback.  It’s more likely that you will want to keep the broken state and simply fix what is wrong and then redeploy the working site.

Moving Forward

Alfresco v4 is an incredible platform and the move to the core repository unlocks all of that capability and innovation. Crafter Rivet is a platform that made use of all of the functionality in the AVM.  And with our new release, we made the move.  You can as well.  More importantly, if you are using the AVM with Alfresco v3 (or even V2), then Crafter Rivet is the perfect solution for your upgrade.  We can provide parity for most needs with a much better user experience that goes way beyond basic Web CMS needs with the coverage of WEM use cases like integrated analytics and reporting, native mobile application authoring, preview, and presentation, content targeting and personalization, multi-channel publishing and much more.  If you’re new customer to Alfresco looking for Web CMS solutions, Crafter Rivet is a comprehensive WCM/WEM solution, with features that rival some of the major players in the industry.

Click here to learn more about Crafter Rivet

Click here to sign up for a our webinar “Crafter Rivet – The WEM Solution for Alfresco 4″ on April 12th at 1pm

Web CMS on The Alfresco Core Repository (Part 1 of 2)

Posted by on April 09, 2012

I was on a call today with a long time Alfresco WCM customer who would like to upgrade from 3.x to 4.x.  They have been using the Alfresco WCM solution provided by Alfresco in 2006 for many years. As many of you know Alfresco’s original WCM solution is based on a technology called the AVM – Alternative Versioning Model.  The AVM is a separate repository and associated user interface that was constructed to handle a number of WCM related use cases. Alfresco has since enhanced their offering in their “Document Management” repository, which now handles WCM use cases.  As a result, Alfresco has now announced that  the AVM will no longer be offered to new customers.  In discussing the upgrade with our clients on the call today. “It’s time to move to the ‘DM’” was the most responsible message to provide. Existing customers won’t lose support over night, but eventually the AVM will hit its end of life.  You want to migrate at your earliest convenience rather than procrastinating and allowing pressure to build.

It’s also important at this point to abandon the use of the term “DM repository”. DM was used to differentiate from the AVM.  At this point there is only one repository.  The “core repository” is much more descriptive of the architecture going forward.  As Jeff points out in his blog and as I will elaborate here, there are differences in the the AVM and the core repository in terms of features. That said, features and use cases should not be confused. The core repository is every bit as capable of providing a platform for Web content management use cases as the AVM.

At Rivet Logic we have made a significant investment in a Web content and experience management application for Alfresco that we call Crafter Rivet. Crafter Rivet is a 100% open source,  full featured environment that powers 100s of websites and has over 40 man years of development effort invested in it. Initially Crafter Rivet’s authoring and management capability was based on the AVM. When Alfresco made the decision to direct the full force of its innovation on the core repository we knew it was time to convert. Crafter Rivet 2.0 is now based on the core repository, Solr search and Activiti workflow for Alfresco 4 CE and EE.  Making the switch from the AVM to the core repository required a deep examination of our use cases and the features we would have on hand within the core repository.

I thought it would be helpful to share some of that thinking.  Today we’ll look at the differences in these repositories and tomorrow, in a second post we’ll discuss the actual Web CMS use cases that need to be addressed and how we addressed them in Crafter Rivet. Let’s explore!

Unique Features of the AVM

The first thing I want to do is address the question of what the AVM can do that the core repository cannot.  Because we’re comparing repository to repository we’re going to discuss features and not use cases. Note that for simplicity, on occasion we’ll collapse the features of the AVM repository, supporting UI and supporting integration into the single term AVM.  It’s also fair to note that what we’ll discuss here are the aspects of the AVM which exposed through the associated user interface and thus applicable to customer engagements.  There are features/capabilities of the AVM repository that were not fully exposed by the UI.

Sandboxing (more accurately, layering)

Sandboxing is the ability for a user to work on any asset or group of assets within the site without interfering with another user’s work.  For example, a user could modify and even break a template or CSS file and no one would know until and unless the user promoted that broken asset out of their work area.  For non-technical readers, a sandbox is best described as your own copy of the website.  For the technical readers, you can think of a sandbox as a long running transaction — in source control terminology, a sandbox is like a checked out branch of the site.

Sandboxing is a high order feature born out a lower level feature called “layering.” The AVM is constructed of lightweight stores.  Stores can be layered one on top of the other.  The store on the top appears as though it contains the assets within the store layered below it.  If a user places an changed in the top store it appears to over-write the asset at the same path below it.  If we have a base store we’ll call “the stage area” and then a store for each user; say Bob and Alice,  and both Bob and Alice’s stores are layered on top of  the staging area you can see how we create the concept of sandbox.  Alice can see everything in the staging area, but nothing in Bob’s store. Alice’s work is in a “sandbox.”  If Alice pushes her change from her store to the staging area, Bob sees it immediately as if it were in his store.

Multi-Asset Versioning

In the AVM, versions are taken at the store level not per asset. When you place a change in the store, a lightweight version is created for all assets at that moment. Because of this, it is possible to know the state of every object at a point in time relative to a given object. For Web CMS applications, we deal with compound assets all the time.  Consider a webpage. A webpage is not typically a single file asset,  it’s a document that points to other documents: components, images, css, javascript, etc.  When you version a page, you generally intend that entire collection of assets to be versioned along with the page.

The core repository manages each individual asset’s version history independently.  If page X points to component Y there is no innate support within the version system to know what version of Y was in use at any given point of X’s history.

Snapshots / Comparison and Rollback

In the AVM you can label a version and compare one version to another. It is easy to see what files have changed.  Because of this it is possible to create “diffs” from one version to another.  Once you have a diff you can roll back entire check-ins very easily.

Content Forms (Now supported in core)

The AVM user interface used to support a forms capability that was not available for the core repository. The forms engine made it simple to create content capture interfaces through mere configuration.  Today the core repository has a forms capability that is more powerful than what was provided for in the AVM user interface.

Content Deployment (Now supported in core)

An AVM project could be configured with remote content receivers.  There was out-of-the-box support for repository to file system deployment (FSR) and repository to repository deployment (ASR).  Today the core repository provides two deployment mechanisms; Transfer Service and Channel Publishing framework, which combined now exceed the capabilities of the AVM content deployment framework.

Unique Features of the Core Repository

Now lets look at what the core repository has going for it that the AVM repository and supporting UI never got around to implementing.  Again we’ll look at features rather than use cases.

Rules Support

The core repository allows you to attach rules to a folder that execute based on lifecycle events and configurable conditions.  This is extremely powerful and its a feature that was sorely absent in AVM.

Stronger Modeling Support

Both repositories allow us to create types and (more commonly) aspects which contain metadata.  However the core repository allows for associations at the modeling layer. In the AVM, associations were kept only as paths within files.  This turns out to be fine for content delivery but bad for managing the content due to move and rename operations because of the unbounded number of updates you may have to perform. Associations in files also makes it difficult for supporting user experience features in your content management platform.   Users expect a platform to understand it’s assets and how they relate to one another in a way that can be quickly accessed through query.  The core repository can do this innately through it’s use of associations.  The AVM cannot.

Strong Transformation and Metadata Extraction

The transformation and metadata extraction frameworks integrated with the core repository greatly exceed the capabilities of the those integrated with the AVM.  The AVM is only integrated with an XML metadata extraction and transformation. The core repository on the other hand has integrated support for all kinds of metadata extraction and transformation including Microsoft Office documents, images, PDF and many many more.

Powerful, Fine-grained Permissions

The core repository gives us the flexibility to create and manage user access to content in a way that best fits an individual engagement through the use of ACLs (Access Control Lists.)  While the AVM was based on a similar scheme under the hood, these were never exposed through the UI and thus it were not practical to deploy on engagements.  Out-of-the-box AVM exposed a few roles that could be applied broadly to the entire site in each sandbox.

API support

The core repository has much better remote API support.  The core repository supports CMIS, webscripts, and RAAr.  AVM only supports a remote API based on RMI.

Workflow Engine

The core repository has 3 workflow engines integrated with it: Simple, JBPM, and Activiti. Activiti is based on standards and has parity with JBPM, but incorporates a far better management console. The AVM provides workflows based on JBPM integration only.

Search

Full text search support is based on indexing. You index a store. In the AVM universe every web project was made up of many (layered) stores.  It was not practical to index every store.  Although you can configure individual stores for indexing, if every author in the system wants to be able to search their sandbox, you will hit obvious limitations to the approach. The core repository content has only one store which is constantly tracked by a search index which means that search is very current with work in progress.  Alfresco 4 has introduced Solr as one of its search subsystems.  Solr provides capabilities that greatly exceed Lucene, the indexing engine used by the AVM.

Integrations

The core repository has many integrations that allow users to interact with content on their own terms, be it email, WEBDAV, FTP, shared drive, Sharepoint and so on.  With exception to the filesystem projections, these are simply not made available in the AVM.

Native support in the UI and APIs for taxonomies, folksonomies and collaboration features

The core repository has repository service and UI support for

  • Hierarchical taxonomies
  • Tags
  • Comments
  • Content lists

Making Sense of the Differences

By this time you should have a pretty good idea of how the repositories compare from a feature perspective.  Two observations are obvious:

  • The core repository has a had the benefit of deep continuous innovation.
  • The AVM has certain features intended for WCM use cases that will need to be addressed in a solution that leverages the core repository.

Join us tomorrow for a blog post that will demonstrate the use cases that these features were intended to cover and how we addressed all the Web CMS use cases with Crafter Rivet using and capturing the full power and innovation of Alfresco 4 and the core repository.

Click here to learn more about Crafter Rivet

Click here to sign up for a our webinar “Crafter Rivet – The WEM Solution for Alfresco 4″ on April 12th at 1pm Eastern for a further discussion and demos!

WCM Goodie: bash script for validating web redirects

Posted by on March 01, 2012

Today a client and I needed to validate a large list of redirects for their site so I created this simple bash script. I thought it was worth sharing! Unix is such a great tool :)


INPUT=links.txt
OLDIFS=$IFS
IFS=,
[ ! -f $INPUT ] &while read link
do
resp=$(curl -L –write-out “%{http_code} | %{num_redirects} | %{url_effective}” –silent –output /dev/null $link)
echo “$link | $resp ”
done < $INPUT
IFS=$OLDIFS

To use this script just put each link you want to run on a separate line in the file: links.txt

With a links.txt file like:

http://rivetlogic.com/
http://blogs.rivetlogic.com/
http://www.google.com
http://www.sesamestreet.com/

You will get with the following pipe delimited output (URL, Status Code, # of redirects to destination, final destination)

http://rivetlogic.com/ | 200 | 0 | http://rivetlogic.com/
http://blogs.rivetlogic.com/ | 200 | 0 | http://blogs.rivetlogic.com/
http://www.google.com | 200 | 0 | http://www.google.com
http://www.sesamestreet.com/ | 200 | 1 | http://www.sesamestreet.org/

Confluence Alfresco Integration for the Enterprise

Posted by on October 05, 2010

Today organizations of all sizes are adopting wiki solutions as a way to facilitate communication and collaboration around planning, projects and departmental matters. Wiki solutions allow users to attach documents to pages and to hyperlink to those documents from other pages. This is extremely useful, however documents, which have traditionally been stored and secured on corporate shared drives are now living in separate places. Some now live within the wiki, while others continue to live on file servers. This is an example of an age-old issue in technology; as we bring in new tools that provide us with more options and better ways to work we are faced managing the side effects of a growing technology footprint.

This issue is not new technology, but instead, one of architecture. As our needs grow we need to adjust our architecture to accommodate new demands. In this case, what we need to do to solve the problem is to separate a few concerns. Some users want to access the document through a file server (shared drive) while others want to access it via the wiki. Traditional shared drive technology doesn’t do a great deal to help us accommodate this. Traditional shared drives provide file system access to documents but lack APIs that allow us to get to our content by more sophisticated means. Further, most wiki technology is one sided as well; while a wiki solution may provide web based access via pages and services they tend to lack file system access. Finally, even if the wiki could “project” its store as a shared drive it’s not likely to be the proper system of record for your documents. By separating the issues of storage, management and delivery we can articulate a solution that allows us to serve documents through a traditional shared drive interface via a proper system of record while at the same time, providing APIs that allow us to get to that content as a service so we can incorporate better ways of working with the document through new technologies as they emerge.

Enter Alfresco. Alfresco is architected from the ground up to be a system of record. It’s designed to provide API / service based access to your documents and content, as well as traditional shared drive access. Alfresco supports three different remote programming APIs including SOAP, webscripts and CMIS. And in addition to presenting itself as a file server so users can connect to it as a file share, Alfresco also mimics an FTP server, a WEBDAV server and even a Microsoft Share Point server. Alfresco is designed to store, secure and manage your documents and to provide access to those documents in the way that best suits your users.

If we use Alfresco to store our documents and integrate our wiki solution to read and write documents though Alfresco’s APIs rather to the wiki itself we satisfy our objectives:

  • Store documents in a proper system of record
  • Allow file-share access to the documents
  • Allow API level access to client applications like wiki

confluence attachments integrated with alfresco

hlgh architecture

Alfresco’s capabilities go far beyond security and content retrieval. Once your documents are in Alfresco they can be searched, workflowed, transformed, translated, versioned and so on and so on, no matter how they are accessed; all through stock capabilities provided by Alfresco out of the box.

At Rivet Logic we see real value in allowing knowledge workers to interact with their content though tools and in whatever process that fits their needs best. At the same time, it’s important to manage content or the same efficiencies that are gained through productive tools and well-designed process are lost due to stove-piped information. The need is real, and given that, we set out to create an open source project that demonstrates a more appropriate architecture and provides a stepping-stone for much greater integration going forward. Najy Nicolas, a “Riveter” from our Boston office has integrated one of the most popular wikis, Confluence, with the management capabilities of Alfresco, the leading open source document repository. We’re calling this project the Confluence Alfresco Integration rivet or CAIr for short. CAIr is open source. You can find downloads, source code and documentation here: http://wiki.rivetlogic.com/display/CAIR/Home

Open Source Licensing and Community

Posted by on January 16, 2010

Open source licensing, community and contribution are important topics. This week there were a number of interesting blog posts and tweets on the subject which might be summarized by a tweet from Matt Asay (#mjasay)

@maslett moral of story? platforms flourish on permissive licensing. GPL is a capitalist’s best friend. Apache/EPL are a community’s

Related blogs (along with several others):

I agree, license and copyright are factors in creating and fostering communities but I don’t think it’s the most important set of factors. License and community, while related are very much separate issues. Open source tends to fetish license and thus it’s over-emphasized in conversations where it at best a contributing factor.

Apple, Google, Drupal, Linux, Microsoft and many, many other examples demonstrate just how little restrictive license and copyright of the core software matters to the size and contribution of the community. Permissive licenses can increase adoption as well as forks and closed derivative works, all of which cannot so simply be considered community.

Relevancy, utility, inclusion, opportunity, transparency, recognition and common vision / interests are what drive the size and output of community. It’s leadership in a project that sets the tone for the priority of these aspects. A small or under-performing community (proportionate to its potential) is more likely related to its leadership than its license.

Related:

An incomplete identification and factoring of some areas around open source that support the ideas in this post:

Boston area Alfresco user group meeting on November 17th to cover Alfresco Best Practices

Posted by on November 05, 2009

Join us in Waltham MA (Greater Boston area) and learn best practices for approaching and implementing projects with Alfresco ECM suite

  • Determining your business use case
  • Architectural best practices
  • Development best practices
  • Operational best practices

Our presentation was co-authored by Russ Danner of Rivet Logic, Jeff Potts of Optaros and Peter Monks of Alfresco

Where?
Rivet Logic Developer Forge, Boston
1050 Winter St
Waltham , MA
617.834.2781

When: 6:30 PM

Pizza, coffee and soda will be provided.

RSVP here to attend