Hello Ard, First of all thanks a lot for clarifying my queries. To be Frank , since there are so many open source in the market,so it becomes difficult to evaluate.So depending on our project requirement I came up with these questions, which you have undoubtedly clarified mine queries already listed.
Now my biggest concern is Jackrabbit. Which version of Jackrabbit is being used? According to one of the site ,in Jackrabbit there are issues with remote access, large batch operations and heavy concurrent write access. The details is available in following link: http://www.theserverside.com/news/thread.tss?thread_id=48137 Details from the above site are pasted below Remaining issues: * We haven't done a thorough review of internal locking to proactively prevent potential unknown deadlock issues * After the ISM locking improvement we still face a problem with many of the database persistence operations being synchronized and need to switch to connection pooling (see my previous comment) to reach full concurrency * Remote access is still relatively slow To summarize, we feel that Jackrabbit is already quite ready for most typical web and other applications with relatively fine grained and mostly read access patterns. There are issues with remote access, large batch operations and heavy concurrent write access, so you may want to wait at least for Jackrabbit 1.5 before considering Jackrabbit for production use. In our case minimum concurrent users will be 100.So there is a chance of concurrent write access(As mentioned in the site.)How do we achieve it?Is it the situation you were talking about data structure(The way we store data)? Your reply to it is most awaited. Thanks & Regards, Dhiren Chandra Sharma ________________________________ iGATE Global Solutions Ltd | Office: +91 80 4104 1336 | Mobile: +91 9731244337 | [EMAIL PROTECTED]| | 158-162 & 165-170, EPIP Phase II, Bangalore - 560 066 India | Website: www.igate.com | -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ard Schrijvers Sent: Monday, August 25, 2008 4:02 PM To: Hippo CMS development public mailinglist Subject: RE: [HippoCMS-dev] Need some clarification Hello Dhiren, To start with, what is your planning regarding this. We have been working for a few years with a slide based repository and webdav based connection to it to have a cms / dms. Now, we are finishing our layer on top of Jackrabbit being entirely jsr-170 compliant, and when jsr-283 is final will become compliant to this one as well. So things like versioning you are asking below is supported by default. The production release is planned in short notice. See below for my further comments: > Hi, > > We are looking for a DMS feature open source software. It would be > really great help if any one can let me know about some of my queries: > > Our project requirement is: > > To create document automatically(50%) or manually(50%) and do some > data Entry based on the document. Yes, on top of our repository, we provide a pluggable cms based on apache wicket. > > 1.Is is possible to use only versioning > mechanism(i.e.Check-In/Check-out/create/Add/Delete/Latest Version)? Yes, this is default jsr-170 behavior which is supported > 2.What type of documents does it > support?(eg.:*.doc,*.pdf,*.tiff,*.gif,*.jpeg,etc) Any binary can be stored. Also searching for *.doc, *.pdf , *....is supported because text is extracted and indexed and searched using Apache Lucene. Meta data of documents and binaries like gif and jpeg are extracted as well, indexed and searchable (extracting done with Tika and Sanselan, both Apache incubators) > 3.Do you have any Load test result?We are looking for around 300000000 > documents/Year of size ranging from KBs to 3MB (backend Oracle). We do not yet have these. Jackrabbit users are storing these kind of numbers in the repository, but you need to think about how to model your data. Jackrabbit is a hierarchical store of content, where obviously, you should for example not store one million nodes direct below a single node, but create some structure. > 4.What is the maximum size(in MB) of the documents that can be > created? I am not sure if there actually is a limit. Obviously, if it is some binary file, it is probably the limit set by the container as maximum upload size, but for just text...i do not think there are really constraints here. > 5.Do you have some functionality for Repository Backup or > Restore(Import and Export)? There is support for export / import through xml (also partial tree parts). Furthermore, the backing storage is done in some (oracle, derby, mysql, microsoft sql, postgresql, .... ) database or filesystem, so backup is also possible through backup of the database > 6.Does it supports clustering? Yes > 7.Does it support Bulk Upload of files(Documents)? The cms interface has some plugins for for example uploading documents. But furthermore, you can upload a bulk of documents by just importing some xml representing documents, or, just write ten lines of code iterating over some folder structure, and save them with simple jcr (jsr-170) calls. We have some examples of importing your filesystem in the repository, and exposing it through faceted navigation (which you get out-of-the-box as well, all exposed through jsr-170 compatible calls) Hope this answers your questions, and don't hesitate if you have more questions, -Ard > > > > Thanks, > Dhiren > > > iGATE is Ranked No. 3 in DQ-IDC best IT employer survey and Ranked > No.6 by Business Today-Mercer Human Resource Consulting-TNS in a > cross industry survey of Best Companies to work for in India > -------------------------------------------------------------- > --DISCLAIMER--------------------------------------------------------- > Information transmitted by this EMAIL is proprietary to iGATE Group of > Companies and is intended for use only by the individual or entity to > whom it is addressed and may contain information that is privileged, > confidential, or exempt from disclosure under applicable law. If you > are not the intended recipient of this EMAIL immediately notify the > sender at iGATE or [EMAIL PROTECTED] and delete this EMAIL including > any attachments > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html iGATE is Ranked No. 3 in DQ-IDC best IT employer survey and Ranked No.6 by Business Today-Mercer Human Resource Consulting-TNS in a cross industry survey of Best Companies to work for in India ----------------------------------------------------------------DISCLAIMER--------------------------------------------------------- Information transmitted by this EMAIL is proprietary to iGATE Group of Companies and is intended for use only by the individual or entity to whom it is addressed and may contain information that is privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient of this EMAIL immediately notify the sender at iGATE or [EMAIL PROTECTED] and delete this EMAIL including any attachments ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
