DJ, what are you attempting to accomplish?  What process are you planning for?  2-way or single direction integration?  More details would be helpful.

We are trying to integrate Agile with CMS so as to manage and support documents, images etc. No process has been defined yet and so would like to know any existing approaches in do so like using ACS with web services or any. Currently as per the plan, this would be a 2-way directional integration but may change to single direction if there is no much use in using 2-way.

And why are you not interested in using Agile PC to manage these docs?  I do not expect you would get the same functionality nor security in the event you use a third-party CM.
Can you provide a storyboard scenario so we can completely understand what you expect the functionality to be.

PC is being used now to manage docs but business team is planning to go for it, and so finding out ways/approach to accomplish it. Of course, we are going on rounds to see both pros and cons with this integration. Pls share your thoughts so that we can rethink or continue to move on further.

DJ,
Moving away from PC as the CM defeats the purpose of the process.  If the business wants something easier then I suggest they do not approach Agile PLM (I find some business units simply do not want to be straddled down by change control or have dynamic documents that may change multiple times per day).  For these instances I suggest using something like SharePoint or utilize the intranet process already in place.  You will need to weigh the requirements of the business and the complexity or entering Agile PC.

I know that there are various “bridge” applications out there (google “PLM Bridge”) that would work given what you are asking, but they are not cheap. The point that Patrick makes is a very good one, why have a CMS system when Agile can do the same stuff very well, and that eliminates the need for an interface and the CMS system. Keep things as simple as possible to meet the business needs. Adding an interface and CMS system just introduces headaches, cost and issues unless there is a very real need to keep things separate and distinct.
 But to directly answer the question, ACS can be used to extract and send data from Agile to a CMS system. You can write a PX to do this, and put the files in a specific directory.  Then you have a very simple program on a schedule to check the extract directory and send the extracted files to your CMS system. Over there, you would need a similar setup, have a scheduled program to look at the FTP directory every 5-10 minutes, and if anything is there, import it into the CMS system. Going the other way is much the same.
 It may sound simple to do, but it ISN’T. You need adequate logging/notification in the event of errors, etc., as well as what should happen when an error occurs (re-process, send an email, ??). You will need someone who knows how to program using the Agile SDK to do any of this. If you expect large files, then you have to make the schedule interval long enough to be able to process everything. Do you process each file individually and then reset, or do you process everything in the directory until done??   LOTS of things to consider in doing this right.

Completely agree with you Kevin and Patrick. Thanks for providing deep insight on this. We’ll see and plan further what to be considered.

DJ,
I also completely agree with Patrick and Kevin. Another CMS next to Agile PC would make life just more complicated.
We sometimes see this request for the management of content for technical publishing (e.g. user manuals, pictures, etc.). Here, the authoring systems often work with external content management systems. It always requires an costly integration (as described by Kevin) or high “manual” efforts.
The better approach is to keep everything in just one system. So all importent content can always be accessed and all other PLM benefits (e.g processes, user roles, …) do also apply.

If your business unit should be looking for a way of better supporting their technical authoring / publishing I would reccomend a tool like XPLM Publisher.
If they are looking for a more loose or dynamic way of managing office documents I would agree with Patrick on something like SharePoint.

Thanks Marc, really helpful.