Question
Pegasystems Inc.
JP
Last activity: 1 Mar 2016 21:50 EST
7.1.9 How to preserve Exported/Imported RAP package files that reside in the "Service Export" directory, even in the cases that Extract Marker file has been deleted?
Are there any ways to preserve those Exported/Imported RAP package files that reside in the "Service Export" directory, even in the cases that Extract Marker file has been deleted? In other words we wanted to treat those Exported/Imported RAP package files NOT temporary files, instead treating them as persistent files as the evidence of system operations.
Posted same question on PDN, https://pdn.pega.com/forums/general-questions/service-export-directory-path#comment-130356
Pegasystems
US
I thought that deleting the extract marker file merely signaled that functions should be recompiled, not that imported rap-zip files should be deleted. Are the two things really affecting each other ? /Eric
Pegasystems Inc.
JP
Yes they are affecting each other according to the PDN discussion that I mentioned above, and on which I posted my own question as well.
Pegasystems
US
I took a look at that pdn writeup, and two things come to mind:
1) The comment in there about seeing why you have to clear the extract marker. Why do you ? If you can avoid doing so, that would be a simple solution.
2) If you really can't find something better, you could try renaming the static content folder to another name, do the extract marker clearing, system restart, then rename the static content back. I'm not 100 percent sure this will work well, since if the system restart depends on some new static content, you will be throwing that away. /Eric
Pegasystems Inc.
JP
Hi Eric,
Thanks for your advice.
We've had experienced some trouble with Rue-Binary-File cache problem on production instance, and the suggested approach is clearing the extract marker to regenerate cached contents for Rule-Binary-File records.
if there isn't any PRPC configuration option available to control "remove / not remove" the contents of the service export directory, perhaps we have to write our own script to "back up service export directory" as restarting the application server.
By the way, I've tested "customizing prconfig setting" approach, but couldn't make it.
Add DASS prconfig/storage/class/web:/rootpath/default
Restart server and uploaded a RAP package. The file was uploaded to the new location.
Hi Eric,
Thanks for your advice.
We've had experienced some trouble with Rue-Binary-File cache problem on production instance, and the suggested approach is clearing the extract marker to regenerate cached contents for Rule-Binary-File records.
if there isn't any PRPC configuration option available to control "remove / not remove" the contents of the service export directory, perhaps we have to write our own script to "back up service export directory" as restarting the application server.
By the way, I've tested "customizing prconfig setting" approach, but couldn't make it.
Add DASS prconfig/storage/class/web:/rootpath/default
Restart server and uploaded a RAP package. The file was uploaded to the new location.
Remove extract marker file, restart server again. Then the uploaded file was deleted.
Chunzhi