Content not depoying to web server

[aadhikari]

Environment:
OS: Ubuntu 8.04
Alfresco Version: Alfresco Enterprise 3.2.0
Webserver: Apache2

I installed (unzipped) the fsr in /usr/local/bin/alfresco/deploy directory. Modified the deployment.properties file:

; Stand alone deployment receiver properties
;
;

; filesystem receiver configuration
deployment.filesystem.datadir=depdata
deployment.filesystem.logdir=deplog
deployment.filesystem.metadatadir=depmetadata
deployment.filesystem.autofix=true
deployment.filesystem.errorOnOverwrite=false

; default filesystem target configuration
deployment.filesystem.default.metadatadir=${deployment.filesystem.metadatadir}/default
deployment.filesystem.default.rootdir=/var/www/staging
deployment.filesystem.default.name=default
deployment.filesystem.default.user=admin
deployment.filesystem.default.password=admin

; sample target configuration (used by unit tests)
deployment.filesystem.sampleTarget.metadatadir=${deployment.filesystem.metadatadir}/sampleTarget
deployment.filesystem.sampleTarget.rootdir=sampleTarget
deployment.filesystem.sampleTarget.name=sampleTarget
deployment.filesystem.sampleTarget.user=Giles
deployment.filesystem.sampleTarget.password=Watcher

; Deployment Engine configuration
deployment.rmi.port=44100
deployment.rmi.service.port=44101

; Stand alone deployment server specific properties
deployment.user=admin
deployment.password=admin
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The deployment server properties in the alfresco web client are:

Transport Name: default
Host: localhost
Port: 44100
URL: –
Type: Live Server
Username: admin
Source Path: /ROOT
Excludes: –
Target Name: default
Include In Auto Deploy: No
‍‍‍‍‍‍‍‍‍‍‍‍

I have not modified anything else. At this point, depoying from the web client, I get all my deployed content in the directory "target" under the fsr install directory. I would really like the content to be deployed to /var/www/staging, where my apache2 webserver is waiting for it.
What am I doing wrong - or what do I need to change for the content to be deployed to the web servrer?
Everything is on the localhost.

[mrogers]

There were some problems e.g. ETHREEOH-2332 on early versions of 3.2 with the deployment.properties file not being picked up.

From memory it was due to an error in the start up script and was fixed last year.    You should be able to take the latest scripts and use them for 3.2.

[aadhikari]

I just did a diff on deploy_start.sh from both alfresco-enterprise-deployment-3.2.0.zip and alfresco-enterprise-deployment-3.2.1.2.zip and I did not see any difference.
1. Do I need to overwrite specific files from 3.2.1.2 to 3.2.0? which ones should I overwrite?
2. Or will it work if I just used deployment server for 3.2.1.2 with Alfresco enterprise 3.2.0?

[aadhikari]

So i just installed alfresco-deployment-3.2.1.2 instead of alfresco-deployment-3.2.0.zip and ran the test again, and I still get the same thing - deploys to a directory "target" inside the deployment install directory, but not to /var/www/staging, which is the value of rootDirectory.
Even enterprise support can't figure this one out.

[mrogers]

Your config looks fine.   And a similar test of the current community download works for me…

Please post your deployment.log file.

You could also try an experiment by changing your default-target.xml file directly to remove the dependency on the deployment.filesystem.default.rootdir property just hard code /var/www/staging

[aadhikari]

Yes, I was able to get the deployment to work by modifying the rootDirectory property value in the default-target.xml directly. I changed the following line:
<!– Where too store content –>
<property name="rootDirectory">
<value>${deployment.filesystem.default.rootdir}</value>
</property>
to
<!– Where too store content –>
<property name="rootDirectory">
<value>/var/www/staging</value>
</property>

and that worked.