Publisher: Changing transfer/browser path? [Kaboom]

Question

Hello -
We've been having a bit of a time with changing Publisher's transfer and browser path(s).
* ALUI 6.0
* Publisher 6.2
- one master publishing node
- 3 "read only" published content nodes
* All content written to a Windows share
* Publisher service(s) all execute as a Windows user with writes to the share
Works great, but...We need to change path Publisher is referencing to write to / read from.
EX: today it writes to "SERVER\OldShare\" - we want it to instead map to "SERVER\NewShare\"
I'm not sure the appropriate way to go about this and the support team seems as stumped as we are.
Steps we're going through now:
* Open Publisher Administration portlet
* Right-click on the top-level "Plumtree" folder so the context menu opens up
* Choose "Publishing Target..."
* We're using "Transfer Using: File Path" (Windows share)
* Transfer path is set to "file://localhost///MyFileServer/publishedcontent/publish"
* Browser path is set to "http://publisher.mycompany.com:7087/publishedcontent/publish"
We want to modify this to be...
* Transfer path is set to "file://localhost///MyFileServer/newpublishedcontent/publish"
* Browser path is set to "http://publisher.mycompany.com:7087/newpublishedcontent/publish"
Kaboom.
Once I update these settings and click "Test Publish Target" I get the following:
"Site specified by browser path does not match transfer path location."
I don't get it. Not saying it doesn't make sense, but I certainly don't get why or what to do ;)
Not even sure where to look on this one in terms of exceptions. I'm not seeing any exceptions in PTSpy (actually, I'm not seeing anything in PTSpy) and the logs only seem to contain basic info and no explicit "this was bad" messages.
Any ideas on how to pursue this would be most appreciated :)
Thanks,
Eric

Answer 1

Thank you for your reply :) You inspired me to validate everything and kind of revisit this from scratch. Instead of trusting the system I busted out Textpad and scanned ALL of Publisher's appilcation files for instances of my publishing path. That did the trick and I found where the little bugger seems to get some of its less obvious configuration values.
* First I found...
\\MyPublisherServer\d$\Program Files\Plumtree\ptcs\6.2\container\conf\jboss.web\localhost\publishedcontent.xml
This looked promising, but it wasn't, really. This file will be rewritten by the jboss service startup, but it was an indicator of the issue as it contained the pesky (old) physical publishing path I wanted to replace.
* Finally we hit gold
\\MyPublisherServer\d$\Program Files\Plumtree\ptcs\6.2\container\deploy\jbossweb-tomcat50.sar\server.xml
This file contains...
<Context path="/publishedcontent" appBase=""
docBase="//MyFileServer/publishedcontent" debug="99" reloadable="true">
</Context>
We changed it to something on the order of...
<Context path="/publishedcontent" appBase=""
docBase="//MyOtherFileServer/newpublishedcontentpath" debug="99" reloadable="true">
</Context>
OK - that actually seemed to help a LOT. Now I can get at the old content and Publisher seemed way, way happier. Cool!
* Next we hit issues creating folders/portlets in Publisher -
"Error: Portlet creation failed: Error accessing file in database ("Document not found: id=F046C0A1/D31E34DD.ACT"). "
This is indicating that Publisher cannot find/access the files or folders from the document repository associated with the (original) Publisher folder structure. To get past this, find your new document repository and copy/restore the files to it from the old document repository.
EX:
FROM \\MyOldDRServer\H$\Plumtree\ptdr\documents\PTContent\Active
TO \\MyNewDRServer\D$\Program Files\Plumtree\ptdr\documents\PTContent\Active
That should do it :)
For those needing to change paths, do a disaster recovery exercise or just find a less obtrusive way to move some things around environments (EX: prod->dev refresh) I hope this helps.