[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13063237#comment-13063237 ] Piergiorgio Lucidi commented on CONNECTORS-221: --- Ok, I think that I have understood what ManifoldCF needs, so now I would like to continue in this way: - submit a new patch to remove the ACE form (creating a new issue) - submit a new patch with the CMIS Authority Connector (creating a new issue) Karl, could you please confirm this plan? Thank you. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-branch-java-patch.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, screenshot-8.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13063247#comment-13063247 ] Karl Wright edited comment on CONNECTORS-221 at 7/11/11 9:46 AM: - I think your plan is fine - but let's continue to work within the same ticket. I know the attachments are getting messy, but I am planning to merge the whole connector onto trunk when it is ready, so people will not need to rely on the patches in the ticket. So please, attach both new patches to CONNECTORS-221. was (Author: kwri...@metacarta.com): I think your plan is fine - but let's continue to work within the same ticket. I know the attachments are getting messy, but I am planning to merge the whole connector onto trunk when it is ready, so people will not need to rely on the patches in the ticket. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-branch-java-patch.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, screenshot-8.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
EC2 recommendation for SharePoint test instance
A colleague of mine who's been learning the cloud says that Amazon EC2 may offer the simplest way to test ManifoldCF with proprietary connectors. Specifically we'd want to start testing with SharePoint 2010. The steps are as follows: (1) Set up an instance. Amazon probably already offers a SharePoint installed instance. For other instances, we'd need to transfer the iso data into the Amazon file system, which may be time consuming but only need be done once. (2) Run the instance when needed. Amazon provides an API for this which means we can even write tests that turn the instance on or off during the test. This is probably also a good way to manage concurrency, since if the instance is already up the test can wait until it comes back down, etc. (3) Fees are 10-20 cents/hour, which is quite manageable, but somebody will need to cough up a credit card that can be billed for this (probably me). I'm going to start by testing our current SharePoint connector in branches/CONNECTORS-221 by hand to be sure that the jar changes needed by the CMIS connector did not have any unfortunate effects on Axis, and I'll post if this seems like a viable plan. Thoughts? Karl
Re: CONNECTORS-221 and ACLs
A repository connector supplies access tokens for each document. These access tokens can be either allow or deny, and are added to an appropriate index in Solr. An authority connector maps user name (and domain) to the user's access tokens, which are incorporated into the search query done to locate documents. All of this is explained quite thoroughly in ManifoldCF in Action. Karl On Mon, Jul 11, 2011 at 10:44 AM, Farzad Valad ho...@farzad.net wrote: At some point, I'll need to integrate security into my work. When are the access tokens mapped? Meaning when (which connector) do you map the token to users and files, before it can be ready to access? On 7/9/2011 10:59 AM, daddy...@gmail.com wrote: The way mcf works is that you supply access tokens, which are arbitrary strings, with the document. You then need a corresponding authority connector which obtains the access tokens for a given user. the search engine then intersects the two at query time. Karl Sent from my Nokia phone -Original Message- From: Piergiorgio Lucidi Sent: 09/07/2011, 9:14 AM To: connectors-dev@incubator.apache.org; daddy...@gmail.com Subject: Re: CONNECTORS-221 and ACLs Hi Karl, my main goal was to create indexes of ACL informations in Solr to allow users to execute profiled queries. This means that create indexes all the informations about ACL is needed to write an AuthorityConnector, but I tried to take a look at the authority interface and I didn't see any way to get ACL using CMIS without the information about the current document. So I need the current documentIdentifier to get ACL from a content. Is this the correct approach or am I missing something? Thank you. Piergiorgio 2011/7/9 daddy...@gmail.comdaddy...@gmail.com Hi Piergiorgio, I am out of town this weekend so I cant comment fully and i havent yet looked at your new patch. However, you will need to rethink how the acls work with the cmis connector. MCF is designed to support multiple connectors, with their own security arrangements, all working at the same time, which means the cmis connector must operate within mcfs security framework to be valid. If you have signed up for the ManifoldCF in Action book, I can send you a number of chapters which will help. Based on what youve done so far I would guess you will need to write a cmis authority. You want chapters 4, 7, and 8, seems to me. Karl Sent from my Nokia phone
Re: EC2 recommendation for SharePoint test instance
Started to do some research on this. (1) I can't find a dedicated SharePoint instance that you can just buy. While that's a shame, I do have access to SharePoint 2010 via an MSDN iso. I'll need to download it and figure out how to install it remotely. Luckily download of data seems to be free. (2) The base instance that seems right for us is this one: http://aws.amazon.com/windows/ . There's not much on its domain affinity, etc, however. It's going to be a bit of a learning curve clearly. (3) The instance size needed is determined by the SharePoint requirements. My .iso is 64-bit only. So at the minimum, we need this: Large Instance 7.5 GB of memory, 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform (4) Pricing. For this instance size, with Windows, it starts at $0.48 an hour. The windows instances is Server 2008 R2, which is the right one, and comes with IIS for free and with what sounds like the MSDE version of SQL server. They state you can use the local SQL instance for free, but also say that if you want SQL Server it's $1.08 an hour. So I'm not quite sure I know what to get yet, and until I actually try it I am not going to know. My best guess is that this is going to take quite a bit of time to learn and assess, probably 10-15 hours conservatively. But I think it's well worth the cost of exploration. Karl On Mon, Jul 11, 2011 at 8:32 AM, Karl Wright daddy...@gmail.com wrote: A colleague of mine who's been learning the cloud says that Amazon EC2 may offer the simplest way to test ManifoldCF with proprietary connectors. Specifically we'd want to start testing with SharePoint 2010. The steps are as follows: (1) Set up an instance. Amazon probably already offers a SharePoint installed instance. For other instances, we'd need to transfer the iso data into the Amazon file system, which may be time consuming but only need be done once. (2) Run the instance when needed. Amazon provides an API for this which means we can even write tests that turn the instance on or off during the test. This is probably also a good way to manage concurrency, since if the instance is already up the test can wait until it comes back down, etc. (3) Fees are 10-20 cents/hour, which is quite manageable, but somebody will need to cough up a credit card that can be billed for this (probably me). I'm going to start by testing our current SharePoint connector in branches/CONNECTORS-221 by hand to be sure that the jar changes needed by the CMIS connector did not have any unfortunate effects on Axis, and I'll post if this seems like a viable plan. Thoughts? Karl
