Question
Prime Therapeutics
US
Last activity: 5 May 2016 9:13 EDT
DSS or prconfig.xml file settings does not work.
HI Team,
I am trying to change pxserviceexportpath to dir. I have created DSS and and have put it in prconfig.sml file. But it still does not show up. Version is 7.2
Any help?
prconfig.xml:
DSS: 
Configuration Settings:
Accepted Solution
Updated: 5 May 2016 9:13 EDT
I worked with Premal on SR-A23979 that was entered for this and this is the conclusion we arrived at:
The only way to change the ServiceExport directory is to change the entire "file://web:" storage class path by adding the following in prconfig.xml (replacing your_path with the path you wish to use):
<env name="storage/class/web:/rootpath" value="your_path"/>
It's worth noting that this is not exactly the same as if the initialization/pxserviceexportpath setting did work; It will move more items than just the ServiceExport directory. But, as long as the pega application has permission to use the specified directory and it is not shared between multiple nodes or applications, this should not cause any issues.
Pegasystems Inc.
IN
Can you try as follow:
initialization/pxserviceexportpath = file://web:/app/pegafiles/import_export/
Kindly take backup of prconfig.xml before doing this.
Prime Therapeutics
US
Hi Arvind,
It did not work . please see below
prconfig.xml
<env name="Initialization/pxServiceExportPath" value="file://web:/app/pegafiles/import_export/"/>
Configuration Settings:
Pegasystems Inc.
IN
Hi Premal,
file://web: in pxserviceexportpath is substituted by temp folder ( $pega.tmpdir ) specified in your environment.
Therefore, kindly check you Pega temp folder.
and you can see folder structure /StaticContent/global/ServiceExport in that.
With this, you can play around to have your desired location.
Updated: 13 Apr 2016 12:45 EDT
Prime Therapeutics
US
I do have $pega.tmpdir set. I do not want to change this.
I just want to change pxserviceexportpath to /app/pegafiles/import_export path.
I have it figured out the alternate path based on other discussion on PEGA Mesh. here How does PRPC interpret "file://web:/" or "file://default:/"
For Example:
If I do following changes in prconfig.xml file. it changes file://web: = /app/pegafiles/import_export/ and it creates following folder structure /StaticContent/global/ServiceExport.
prconfig.xml
<env name="storage/class/web:/rootpath" value="/app/pegafiles/import_export/"/>
This will change default path for file://web: for all file storage.
Question is will it change anything else or break something with it?????
Further more if you look at 7.2 help they have topic names
I do have $pega.tmpdir set. I do not want to change this.
I just want to change pxserviceexportpath to /app/pegafiles/import_export path.
I have it figured out the alternate path based on other discussion on PEGA Mesh. here How does PRPC interpret "file://web:/" or "file://default:/"
For Example:
If I do following changes in prconfig.xml file. it changes file://web: = /app/pegafiles/import_export/ and it creates following folder structure /StaticContent/global/ServiceExport.
prconfig.xml
<env name="storage/class/web:/rootpath" value="/app/pegafiles/import_export/"/>
This will change default path for file://web: for all file storage.
Question is will it change anything else or break something with it?????
Further more if you look at 7.2 help they have topic names
Changing the ServiceExport directory
By default, the ServiceExport directory is a subdirectory of the temporary files directory on the server.
You can change the default location of this directory through the prconfig.xml setting:
<env name="Initialization/pxServiceExportPath" value="<directory>"/>
where <directory> is the new location.
This should work but it is not working.
Updated: 4 May 2016 12:40 EDT
Pegasystems Inc.
US
See SR-A22301 || 7.1.9 || Service export directory location which explains that this property is not used. I am looking into getting the documentation fixed.
Pegasystems Inc.
US
Reposting this as the specified mesh thread is internal.
initialization/pxserviceexportpath will not take effect as the ServiceExport location is hard coded to StaticContent/global/ServiceExport in the temporary directory.
Only the location of the temporary directory is configurable using the Initialization/explicitTempDir setting.
Accepted Solution
Updated: 5 May 2016 9:13 EDT
I worked with Premal on SR-A23979 that was entered for this and this is the conclusion we arrived at:
The only way to change the ServiceExport directory is to change the entire "file://web:" storage class path by adding the following in prconfig.xml (replacing your_path with the path you wish to use):
<env name="storage/class/web:/rootpath" value="your_path"/>
It's worth noting that this is not exactly the same as if the initialization/pxserviceexportpath setting did work; It will move more items than just the ServiceExport directory. But, as long as the pega application has permission to use the specified directory and it is not shared between multiple nodes or applications, this should not cause any issues.