Services corresponding to DM and WCM features

[satej_sirur]

Hello,
    I am trying to get a better understanding of how Alfresco implements Document Management and Web Content Management features at the level of the repository. After much poking around the repository sources, I have found little more than FileFolderService (which seems relevant to Document Management) and AVM (which seems relevant to Web Content Management). Are there other core services in the repository that are implemented specifically to support DM and WCM features? Or are these two "applications" built on top of existing 30-odd services (Node, Content, ML, and so on)?

[mrogers]

You are right to think about WCM as an "application" built on the Alfresco core services.  The other major applications of Alfresco are DM and Share.  

In fact WCM uses both content stores together, but you are right that most of the web content managed by WCM goes into the AVM store where it benefits from features like sandboxes.  While most of the DM content goes into the non AVM store.    And there are services like deployment which are WCM specific.

Share uses both content stores together too.

[satej_sirur]

And there are services like deployment which are WCM specific.

Thanks for your prompt reply. I would be interested in knowing about other repository services, such as deployment as you mentioned, which were added to provide DM and WCM features. What I mean by services is either public repository services (those annotated with @PublicService) or their implementations (e.g. AVMNodeService that implements NodeService which, in turn, is a public service).

[satej_sirur]

Am I correct in understanding that there are no services beyond FileFolderService, and DeploymentService (and maybe the non-PublicService AVMNodeService) that implement DM and WCM features? I am trying to find out more information about repository services rather than content stores.

PS: Would this post be more appropriate in the forum for Repository Services?

[mrogers]

You are right that the Applications are built on the 30 or so "core" services.

We're are in the middle of adding some "application layer" facades for WCM to make things a little easier to use and test, but that's very much work in progress.      There is also some WCM stuff (like permissions and locking) in the AVM Implementation that should probably be moved upwards.     The crucial difference between DM and WCM is whether content is sandboxed.   And sandboxes have their own permissions and workflow rules.

Here's a length list of the services.

SERVICE_REGISTRY     Core
DESCRIPTOR_SERVICE  Core
TRANSACTION_SERVICE Core
AUTHENTICATION_SERVICE Core
NAMESPACE_SERVICE Core
DICTIONARY_SERVICE Core
NODE_SERVICE Core
CONTENT_SERVICE Core
MIMETYPE_SERVICE DM
CONTENT_FILTER_LANGUAGES_SERVICE ?
MULTILINGUAL_CONTENT_SERVICE ?
EDITION_SERVICE ?
SEARCH_SERVICE Core
CATEGORY_SERVICE Core
COPY_SERVICE ?
LOCK_SERVICE DM
VERSION_SERVICE DM
COCI_SERVICE DM
RULE_SERVICE DM, Share
IMPORTER_SERVICE Core
ACTION_SERVICE Core
PERMISSIONS_SERVICE DM
AUTHORITY_SERVICE ?
TEMPLATE_SERVICE Share
FILE_FOLDER_SERVICE Core
SCRIPT_SERVICE Share
WORKFLOW_SERVICE DM
AUDIT_SERVICE Core
OWNABLE_SERVICE ?
PERSON_SERVICE Core
SITE_SERVICE DM
AVM_SERVICE WCM
AVM_LOCKING_AWARE_SERVICE WCM
AVM_SYNC_SERVICE WCM
CROSS_REPO_COPY_SERVICE ?
ATTRIBUTE_SERVICE Core
AVM_LOCKING_SERVICE WCM
VIRT_SERVER_REGISTRY WCM
THUMBNAIL_SERVICE     DM, Share
TAGGING_SERVICE        DM, Share
DEPLOYMENT_SERVICE  WCM


And please don't cross post.

[satej_sirur]

Perfect! This is exactly what I wanted. Many thanks.