We are planning to integrate PEGA with CMS which is CMIS complaint; When PEGA access files stored in CMS, it writes file at app server - default path is "file://default/CMIS_Documents/*" and sends file contents to browser using sendfile function.
Now, I'm trying to understand what benefits we will have by keeping CMS in place, since PEGA is still writing file at app server folder.
Some of the benefits I can think of is,
- since attachments are bulkier and consume maximum space in DB, so by having CMS system, PEGA DB size won't be growing too much, and this will lead to improved performance, because DB operations operate on attachment table.
- Reduce in space requirement for the DB.
Apart from OOTB capability for CMIS, can we alter this design to retrieve only DOC link from CMS, and redirect to this link which opens items in a new browser window?
Are you using Connect-CMIS to write files such as WO attachments to the external CMIS server? In that case the files will be written to your CMS repository. Pega might be temporarily writing files to the app server filesystem before sending it over to the CMS system.
And with regards to be benefits, yes you won't have to burden Pega DB with large attachments and instead leverage a software that is built to store them.
Now when you try and open the attachment for the WO, is Pega bringing the file over to the temporary application server filesystem before displaying it in the browser? I think that is what you are saying and I believe is the way this works right now.
Your suggestion about retrieving the doc link only and not the actual file is a good idea and is potentially an enhancement request. Perhaps we can spin one off for you.
PEGA Posts document to CMS repository and stores object ID as part of attachment metadata in attachment table (pc_data_workattach)
In above operation PEGA don't write file at app server
- Reading file from CMS
PEGA does a connect call with object ID as request and accesses file from CMS. During this process PEGA first writes file at APP Server directory (file://default/CMIS_Documents/*) and then uses sendfile Js function to send file contents to browser for display.
1. Using OOTB capabilities of PEGA (itemized above), whether we’d see performance degradations in application, having said that PEGA is writing file at APP server, during retrieval process ?
Can you please let me know how to put forward an enhancement request?