Question

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

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

February 29, 2016 - 12:08pm

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

March 1, 2016 - 5:44am
Response to ericosman_GCS

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.

March 1, 2016 - 9:51am

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

March 1, 2016 - 9:50pm
Response to ericosman_GCS

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

customise-service-export-directory-dynamic-system-setting.JPG

Restart server and uploaded a RAP package. The file was uploaded to the new location.

customise-service-export-directory-before-delete-extract-marker.JPG

Remove extract marker file, restart server again. Then the uploaded file was deleted.

customise-service-export-directory-after-delete-extract-marker.JPG

Chunzhi