i have just started learning adobe cq and i see terms(and api) like tenant being referred to.
what does a tenant refer to in CQ terminology.
also is there any good tutorial any one can refer.
An Apache Sling Tenant supports this sort of model: one CQ5 instance provided by a hosting service, multiple sites for multiple customers of the service using the same instance, each customer sees and controls only his own content. There's not much documentation that I can find. There is a draft design page for the feature. I doubt that CQ5 fully supports the feature.
Related
I want to build a JavaEE GED application using alfresco and activiti Workflow engine which manages and monitors the mail of an organization (Letter, Fax, mail etc.). Since I am new with alfresco I want to know the best way to communicate with alfresco in my case : the use of CMIS or web scripts (I'm building a third-party application ) .
I can suggest two solutions using Using the REST API or CMIS with a library like Apache Chemistry
Apache Chemistry is very well documented and you can find good pointers on the official website for pretty much any thing you would want to do !
If you want to get a session from your Alfresco Repository for example follow this post : How to retrieve 'repository root' id/children from CMIS repository?
Alternatively, you can find a lot of resources around for interacting with alfresco using REST (either the new REST API, or old restful endpoints). Check the platform integrations portal from the official docs, it would be a very good starting point.
We need Magnolia 5.5 integration with Microsoft Dynamics(CRM) but as per the following magnolia documentation the integration is not available out of the box with Magnolia. Magnolia Documentation
How can we build that functionality in Magnolia, please advice.
Thanks in advance..
All depends on what kind of API Dynamics exposes for such integration. And what features of Dynamics exactly do you want to integrate.
If there is any REST based API, you can have a look at similar integrations (those for SugarCRM, Eloqua or SalesForce come to my mind) and do what needs to be done. Source code for the above integrations provided by Magnolia is AFAIK available to all Enterprise customers.
Typically you have two parts of the integrations
- backend one where you create content connector for an app and the app directly to allow your editors to interact and select items from Dynamics, and
- some templating functions that allow templates to understand items previously selected by the editors and retrieve those from Dynamics when rendering the template.
- typically you will also have to deal somehow with authentication between Magnolia and Dynamics and (unless all is super fast) with caching items retrieved from Dynamics in Magnolia in some form of volatile cache.
But really, any more details on what to do and how depends on the use case. It would be different for building customer self service portal and for e.g. just listing phone number of the sales/support rep closest to visitor of the site based on geolocation.
I have a Spring MVC application that connect with Alfresco using CMIS libraries, actually I can upload documents and download it but I need integrate Alfresco's WebPreviewer to preview documents in my app.
I found some code here but I don't know how to do it
It's hard to say for certain because of the limited amount of information that you've provided, but I think that the problem that you're going to be faced with when trying to use any of the existing previewer code is one of authentication. If you're using only using CMIS then you won't be able to use any of the WebScript based REST APIs that the Alfresco widgets will be using.
There are two possible previewer widgets that you can use - the older YUI2 based previewer (that you'd currently find in the document details page and the Document Library film strip view, and the newer Aikau component that you'd find in the faceted search previewer (from version 5.0 onwards).
I suspect that you won't be able to re-use either of these components without either authenticating against Alfresco in a way that allows you to access the WebScript based REST APIs or extending and customizing those widgets.
You've said that you have your own Spring MVC application, but you haven't said whether or not that is using the Surf extension - if it is, and you're using the authentication capabilities provided by Surf then you will be authenticated to use those REST APIs - as the Surf authentication provides access across all APIs (including CMIS) via a single authentication.
If you are able to access those APIs then you should be able to follow the steps outlined in both the form post and the blog posts in your own question and the previous answer, however - based on your question I suspect that you can't do that.
If you've not come across it, you might be interested in the Aikau archetype that builds a ready-made Alfresco client using Surf (see this link) and that tutorial also shows how to use the Aikau previewer (see here).
Because this is providing you with a Spring MVC client that is preconfigured to authenticate against Alfresco, you might be able to port your application to use it.
Otherwise, as I said earlier - chances are you'll need to extend the existing widgets to use the CMIS APIs to render the previewers. Again, Aikau is easier to extend that the old YUI2 widgets - but is reliant on Surf.
I am comparing Alfresco, Magnolia & Joomla especially specific to following features:
a. Ease of Integration of user created templates.
b. JCR (JSR-170?) or CMIS compliance.
c. Scalability in architecture.
d. Mobile site deployment.
I used cmsmatrix.org to compare features but I could not get some of the specific information related to above mentioned points.
Any insights based on your experience on working with one or more of the above CMS products will be helpful.
Thanks,
Krish.
While these four products are branded as CMS I don't think they are really comparable. Drupal and, for what I know, Joomla are web publishing CMS (or WCMS), they are designed to create web sites and manage their content. They are not designed as generic CMS, DMS or ECM. Alfresco, and probably Magnolia, are ECM/DMS designed to manage enterprise contents.
For instance, while manageable in Drupal (given enough effort and custom PHP code), complex multi-states multi-actor workflow for multilingual documents (PDF, Office, etc.) are probably easier to manage with Alfresco. And Alfresco is probably not suitable to manage web content with lightweight publishing workflow and user generated content.
Having the managed content published on a web site does not means it has to be managed by the same tools that the one used to manage the web site. For instance, using the Drupal CMIS module, you can bridge it with Alfresco (or any CMIS compliant ECM) to manage your enterprise content in the suitable tools but publish parts of it on a Drupal site.
Summarizing inputs I received here along with what I found in my search from various discussions so far (thanks #mongolito404 and bkraft).
For web content management features - Drupal / Joomla is recommended.
For Enterprise Content Management / Document Management features with minimal web publishing features - Alfresco / Magnolia is recommended.
For specific requirements the best of different tools can be used - Drupal to publish web content via CMIS support. Alfresco as solution for workflow & document management.
Alfresco already supports & continues to have CMIS in product roadmap (contributes to CMIS community).
Drupal is CMIS compliant (OOTB) with strong web content capability.
Leveraging best of both (Alfresco & Drupal) could also be one of the options depending on the requirement. Refer: http://www.optaros.com/blogs/drupal-alfresco-integration#
Another interesting option seems to be Liferay (v6+ specifically) with their CMIS integration capability: http://www.liferay.com/web/jonas.yuan/blog/-/blogs/integrating-alfresco-through-cmis-in-liferay
Thanks,
Krish.
Can't speak for the others, but from Magnolia's perspective, ease of integration is certainly a core feature. It runs on the Java platform, so integration is a given from the platform side. In addition Magnolia has been rated the most flexible CMS on the market today by independent analyst Tony White of Ars Logica download his free report (always worth a read, and other reports are also available).
JCR: Magnolia is based on JCR, and was so since the first line of code
CMIS: not implemented yet, but planned for Magnolia 5 to be shipped late this year
Scalability: Magnolia's got it covered. See our case studies
Mobile site deployment: again, comes naturally to Magnolia thanks to its architecture and rich out of the box functionality.
Regards
- Boris
Update: CMIS is available as a community module since Magnolia v4.5
Is there an open rbac framework for asp.net? there a few solutions for rails but i cant find a simple rbac system for asp.net. is there something that can be used and extended?
This article looks like a good place to start (it is best to drill into the links the author references for more information, but make sure that you read the article as well):
Implementing RBAC on .Net:
Recently I worked on RBAC (Role based
access control) implementation within
.Net. A comprehensive work on this
topic is done by Mark Strembeck XoRBAC
Home Details on RBAC concept can be
found at NIST RBAC
While the design approach given in
Strembeck's work was comprehensive
enough to be realized on .Net, the
default implementation (done on XoTcl)
used extensive patterns from the
language (e.g. ability to use an
object as a class!), so a quick port
of that to a complete .Net
implementation of the design would
have taken a bit of an effort in my
current project. Well, instead of then
implementing the solution, I selected
MS Authorization Manager (I know folks
will say, Dah... that would have been
a no brainer). This is a small library
and a management console prrovided on
Windows 2003 and 2000 that implements
most of the RBAC requirements.
Maybe I've missed the point here, but ASP.NET ships with a pretty robust Role Provider framework - it should be very easy to find many open source implementations, if you really don't want to use the implementation that it comes with.
A comprehensive article on RBAC was found on RBAC Wikipedia. Instead of researching on how to implement the features mentioned in the article, I tried to find security framework which allows a non-technical guy like me to apply security on asp.net applications and found following frameworks:
Portal Guard
Visual Guard
Member Protect