I have requirement to develop DMS(Document Managemen System) with some initial requirements:
If possible DMS should be open source
Initially DMS should support up to 500 users
System should be scalable in sence od users or content
Docuemtns/Content should be stored on a file system
Document should be able to be marked for later destruction
Mandatory to have workflow capabilities
Mandatory to have version control capability
Nice to have SSO(Single Sign On) with Liferay portal
Nice to have posibility to expose some of funccionality via portlets in Liferay
Document management should be done via the web interface
Nice to have shared drive capability
Nice to have events and notifications about add/change content
At the moment I am in doubth to choose between Alfresco and Nuxeo.
I will appreciate any help to choose between them.
Thanks in advance
I have not much experience with Nuxeo, but here is for Alfresco:
1.If possible DMS should be open source
Yes.
2.Initially DMS should support up to 500 users
Yes, if you have a good server.
3.System should be scalable in sence od users or content
Yes.
4.Docuemtns/Content should be stored on a file system
Yes. Only metadata is stored in a database.
5.Document should be able to be marked for later destruction
The free Records Management module has retention capabilities.
6.Mandatory to have workflow capabilities
Yes.
7.Mandatory to have version control capability
Yes.
8.Nice to have SSO(Single Sign On) with Liferay portal
Yes.
9.Nice to have posibility to expose some of funccionality via portlets in Liferay
Alfresco and Liferay work very well together.
10.Document management should be done via the web interface
Yes.
11.Nice to have shared drive capability
Yes.
12.Nice to have events and notifications about add/change content
Not sure about this one. The Share module has this feature, but not sure about the main DM application.
Don't know the Nuxeo system, but we are using Alfresco as a document storage and session server. We have our own GUI and only use it as a back-end system. So far we had no problems. Plus Alfresco has a nice REST interface which makes it easy to integrate into any existing system.
Related
We have a python based server that uses mongodb database. Our server programs uses RabbitMQ to exchange request/reply packets with many Android apps and perform actions accordingly. In addition to this, now we also need to create a web portal for the admin staff to let them manipulate the database, upload/download files, view data/statistics and trigger actions for android clients. So, the database is going to be common for the portal and the existing server programs.
For the web portal development, I got a recommendation for using Plone. We are comfortable in using traditional Node.js. Could anybody guide me on the use of Plone within this context. Is plone able to communicate with mongodb and existing server side programs?
Plone is a CMS designed around managing web based content and is tightly integrated for storage of its data in the ZODB, a NoSQL database. If data is very custom and isn't all about webpages and website nagivation etc, or if you have a need for the data to live in a different kind of DB then Plone probably isn't the right tool for you. This isn't to say it can't be made to do these these things but you would have to learn a lot about it's internals to make it do these things.
A question regarding the integration of the document management system Alfresco into Oracle Application Express (APEX) based on CMIs-repository:
The aim is to use APEX as the portal-page and Alfresco showing it's results (document lists) based on search parameters coming form APEX.
A search result from a CMIS-query should be displayed in an APEX page-region.
Unfortunately I have no experience in this sector (REST, CMIS) - so any advice would be welcome!
A related question regarding user authentication and authorization via CMIS does also arise.
Has anyone out there implemented something like this or used these components together, yet?
The first thing that pops into my mind is making the choice where you want your communication with the repository to take place: client side or server side?
Alfresco supports Web Scripts, so I would be possible to create a javascript-heavy thick client which connects to your repository, get information about your files and redirect to their download links.
The alternative would be to design some way to connect to the repository from the database server. Again there are many ways to do this. You can connect to the repository during your page load and use PL/SQL regions to fire scripts that connect to your repository, get the data you want, and render your region with that information.
Another way would be to periodically check the repository for changes, and maintain a 'shadow copy' of the repository within your oracle database tables.
Of course all of these solutions have their own drawbacks.
I have been trying to find an open source or affordable platform / CMS that is distributed.
And by distributed I mean that there is a single control panel with all the content, but you can have multiple websites on multiple web hosts that query an API that holds this content. Not the usual "one install, multiple websites" as you can do with Wordpress MU.
Ideally there would be an API that the website can connect to and get the data, or use push technology from the control panel once new content is added.
If there is no client side platform built but there is a sophisticated content management platform with an API that allows me to build my own client/website connecting to it, that would be fine too.
Does anyone have tips if there is such a thing?
Govento CMS is a distributed CMS, that allow you, to manage all projects with a single installation and present your content via push publishing dynamic and current on different remote delivery-platforms.
german: http://goventocms.com
or english:
http://translate.google.de/translate?hl=en&sl=de&u=http://govento.de/&prev=search
I have a couple of questions regarding IBM Portal Portlets.
I have just stumbled into the realm of Portlets - and as far as I am concerned was dropped into the deep end. Having to work on a IBM WebSphere Portal 6.1
We are still in the evaluation stage - and three things that I haven't been able to find clear answers to yet.
Database - is there one single Database that also gets used by the installed Portlets - or do you configure DB individually on a per Portlet Basis?
Authorization and Authentication - how can a Portlet get hold of the User and the rights the user has?
Are there any known constraints in using JSR-301 compliant JSF Bridges instead of bog standard Portlets?
Thanks in advanced.
I haven't used Portal 7 yet, but I have used pretty much every other version, so my apologies if you are using 7 and this information doesn't fit exactly.
1) Database: when you install portal, you configure a database it uses to store portal configuration (and sometimes user rights as well, although this aspect can be set up using a custom user registry like LDAP). If you don't have an already dedicated DB, Portal will use its packaged DB, Cloudscape/Derby. This DB can be completely separate from the DB that the portlets use to manipulate data unrelated to configuration. E.g. if your portlet is displaying inventory for a bike shop, the DB holding that info can be accessed in the normal web application way through a datasource set up in the WAS GUI.
2) For a lot of scenarios, your portlet doesn't need to know the user's rights, it won't render the portlet unless the user has been assigned the correct rights via Portal Administration. But in the cases in which you would need to know the user's rights, they can be accessed via the Portal User Management Architecture. Here's a good whitepaper on the subject: http://public.dhe.ibm.com/software/dw/websphere/PUMA_scenarios.pdf
3) Known constraints? You may have to google for that specifically, but I will say that unless you use IBM's custom JSF bridge, there may not be a lot of support from IBM's technical issue team if you come up against a problem. However, the support guys are usually pretty helpful, I find. Don't let that stop you from trying though :)
The two resources that I use pretty exhaustively are the InfoCenter http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp and the developer forums on IBM Developerworks.
Best of luck, and welcome to the dark side!
We're currently using the SSO component of Oracle 10g App Server to authenticate users on our external / internet facing client "portal" (think similar to online banking)
SSO uses Oracle Internet Directory to store it's data, and we've been able to use PL/SQL and Java to access and modify the data held in OID (e.g create/drop users, change/verify passwords etc)
With the advent of 11g, Oracle appears to have "orphaned" SSO… it is available, but only as an add-on, and it appears to have been superseded by Oracle Access Manager. I'm guessing that it will have been dropped together by 12g. Plus it looks pretty difficult to install and get running correctly.
So, I'm wondering if anyone has any experience of having had the same migration problem as us? If so, what did you do?
Alternatively, does anyone have any experience of doing something similar using Oracle Access Manager? Do you think it will do what we want?
Or is there a better road to go down? Is there something else I should be considering?
Sorry for the very broad question, but it's one of those situations where a person's experience of what does + doesn’t work can make an enormous difference to us making some progress in a timely fashion. Thanks.
From my knowledge, Oracle Internet Directory (OID) is an LDAP compliant directory whereas Oracle Access Manager (OAM) is much more complex and consists of two main systems:
Identity System (users, groups,
workflows)
Access System (single/multi domain
SSO solution for Web and non-Web
based applications).
Access Manager relies on an Identity Server which is a stand-alone server process that communicates with any Directory Server (AD, OID, Sun Directory server..).
So you can use the new OAM and link it with your existing OID... to retrieve users/groups and metadata. All that you could do with OID will be doable with OAM as it brings more abstraction layers.
But in my opinion, and considering your case, directly accessing LDAP servers (OID, AD, etc) and using a light and "home made" SSO system is cheaper than relying on those big systems.... I think OAM is a usefull solution when you have lots of heterogeneous applications (web, non web, mobile, ...) and/or multiple organizations/domains with links and/or you need a very scalable approach.