Thanks Jeff & Jay! I will talk to the architects about IBM Content Navigator, it may be that they weren't aware of that option!
michael lucas | Senior Software Developer | Great-West Life From: Jay Brown [mailto:[email protected]] Sent: May 29, 2014 10:24 AM Cc: [email protected] Subject: Re: good use case for OpenCMIS Server? I agree with Jeff. It depends on what you would be adding to the CMIS services that are already there. Have you considered using the IBM Content Navigator (CMIS) client as your common ECM client / mid tier service? Since it already talks to CMIS repositories (including SharePoint 2013, Alfresco, etc.) and you are already licensed to use it if you have a FileNet system. Jay Brown Senior Engineer, ECM Development IBM Software Group [email protected]<mailto:[email protected]> www.linkedin.com/in/parityerror/<http://www.linkedin.com/in/parityerror/> [Inactive hide details for Jeff Potts ---05/29/2014 08:00:34 AM---I guess it depends on what you want the Common Document Servic]Jeff Potts ---05/29/2014 08:00:34 AM---I guess it depends on what you want the Common Document Service to look like to the clients calling From: Jeff Potts <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]>, Date: 05/29/2014 08:00 AM Subject: Re: good use case for OpenCMIS Server? ________________________________ I guess it depends on what you want the Common Document Service to look like to the clients calling it. If you want it to look like a repository, it could be implemented as a server. But I suspect you'd rather have it look like a higher level service and that you'll have a fair amount of needs in your Common Document Service API not covered by CMIS. Jeff On Thu, May 29, 2014 at 8:56 AM, Lucas, Mike <[email protected]<mailto:[email protected]>> wrote: > Hi! I'm pretty new to CMIS and OpenCMIS so please bear with me. > > We are building a Web Service whose purpose is to be the Common Document > Service for our enterprise. It will provide an abstraction layer in front > of multiple different content repositories in the enterprise. The API to > this Common Document Service will be CMIS. > > For now, we just have to build it to talk to (sit in front of) IBM FileNet > and Microsoft Sharepoint. Both of these support CMIS APIs so we will almost > certainly use those (unless we run into problems with them, then we can use > native APIs). In the future we may also integrate non-CMIS content > repositories. > > My question is, is this a good use case for the Apache OpenCMIS Server > product? It seems like it may be based on what I have read in the Server > Development Guide (https://github.com/cmisdocs/ServerDevelopmentGuide). > On the other hand, it may be overkill if the back-end repositories are > already speaking CMIS (as FileNet and Sharepoint do) -- since our service > would be doing a lot of translating from CMIS to objects then back to CMIS > again. > > Thanks in advance, > michael lucas | Senior Software Developer | Great-West Life | > [email protected]<mailto:[email protected]> > "Say not in grief that she is no more, but say in thankfulness that she > was. A death is not the extinguishing of a light, but the putting out of > the lamp because the dawn has come." - Rabindranath Tagore > >
