topic Re: Is Deployment Engine running? in Alfresco Archive

Is Deployment Engine running?

tagany — Thu, 13 Aug 2009 22:37:19 GMT

Following the instructions in Getting_Started_with_WCM_for_Alfresco_Community_Edition_3_2.pdf I've gotten to deployment, and when I try to deploy I get\\localhost:44100Deployment Failed07130021 Could not connect to remote FSR, transportName:default, hostName:localhost, port: 44100sudo ss -lnp shows

Re: Is Deployment Engine running?

mrogers — Thu, 13 Aug 2009 23:02:29 GMT

Doesn't look like it.

By default it is the standalone deployment reciever that uses 44100 and is a separate executable that you will have to start. It will typically be run on a remote machine.

For testing purposes 3.2 comes with a filesystem target built into the repo now on 50500 that you may be able to use.

Re: Is Deployment Engine running?

tagany — Thu, 13 Aug 2009 23:13:47 GMT

Thank you,

David

Re: Is Deployment Engine running?

godber — Fri, 14 Aug 2009 12:43:07 GMT

Doesn't look like it.

By default it is the standalone deployment reciever that uses 44100 and is a separate executable that you will have to start. It will typically be run on a remote machine.

For testing purposes 3.2 comes with a filesystem target built into the repo now on 50500 that you may be able to use.

So the Deployment server included with Alfresco by default is for "testing" only? Is it then recommended to install the standalone deployment server along with the Alfresco server? Or is it generally recommended to have run the stand alone deployment server on a separate host?

Austin

Re: Is Deployment Engine running?

mrogers — Fri, 14 Aug 2009 13:50:57 GMT

I was not careful enough with what I wrote.

You choose what options suit you and your environment.

For testing, demo and evaluation people tend to like running everything as a single process on a single machine. But it is unlikely that this is how the live environment, which has to worry about all sort of administrative concerns, will be used.

The inbuilt filesystem target was added in 3.2 to preview via a test server. Only time will tell how it gets used or whether it is a good idea to have it there.

Re: Is Deployment Engine running?

tagany — Fri, 14 Aug 2009 16:22:21 GMT

Well, I got to deployment, everything seems good, attempted to deploy rev 3 and …

\\localhost:50500
Deployment Failed
07140144 No such target: default

the catalina.out log has this …
08:39:26,583 ERROR [avm.actions.AVMDeployWebsiteAction] Deployment Error
org.alfresco.service.cmr.avm.AVMException: 07140146 Deployment exception, unable to deploy : srcPath:alfrescosample:/www/avm_webapps, target:default, version:3, adapterName:default, hostName:localhost, port:50,500, errorrg.alfresco.service.cmr.avm.AVMException: 07140145 Error during deployment srcPath: alfrescosample:/www/avm_webapps, version:3, adapterName:default, hostName:localhost, port:50,500, errorrg.alfresco.deployment.impl.DeploymentException: 07140144 No such target: default
at org.alfresco.repo.deploy.DeploymentServiceImpl.deployDifferenceFS(DeploymentServiceImpl.java:1179)
(stack trace continues)

Searching didn't bring up anything that seemed pertinent.

David

Re: Is Deployment Engine running?

jarinys — Mon, 17 Aug 2009 12:24:25 GMT

Well, I got to deployment, everything seems good, attempted to deploy rev 3 and …

\\localhost:50500
Deployment Failed
07140144 No such target: default

David

I think you have to specify target "avm" in the "Configure Deployment Servers" wizard for your Web Site. It is supposedly possible to configure, but
the docs I've read failed to mention how.

Jari

Re: Is Deployment Engine running?

mrogers — Mon, 17 Aug 2009 12:51:13 GMT

When deploying as well as saying where you want to deploy your content you also need to specify which target you want to deploy to. You could have one project to one target or many projects to one target or one project to many targets, the choice is yours.

Out of the box there are two targets defined on the newly introduced repo based receiver called "avm" and "filesystem".
On the standalone deployment reciever there is a single target which for backwards compatibility with the old FSR has the name "default".

You should see an INFO message when the deployment system starts which tells you the names of the targets that have registered with it.

To define a new target you need to add a new target definition.

There's some documentation here but I agree it needs to be expanded.
http://wiki.alfresco.com/wiki/WCM_Deployment_Engine#Targets

Re: Is Deployment Engine running?

jarinys — Mon, 17 Aug 2009 14:07:51 GMT

Ah, thanks for the link- I think i saw it earlier, but assumed it was some really low-level customization due to all the xml/bean wiring and stuff.

I'll try it out and cleanup the docs if I can.

Re: Is Deployment Engine running?

rosa_martin — Wed, 19 Aug 2009 12:00:11 GMT

Hi

I had the same problem, but the document at http://wiki.alfresco.com/wiki/WCM_Deplo … ne#Targets since too much work for me, so I deleted the FSR Deployment Receiver configuration and I added it again.
At least I could deploy. But it only works with PORT=50500 and to type a "TARGET NAME" is mandatory.

Rosa

Re: Is Deployment Engine running?

abbeydom — Fri, 28 Jan 2011 13:19:28 GMT

Had same issue with 3.4c community edition and resolved it. On the deployment servers configuration page state the ff:

Configure deployment servers
——————————————-
Transport Name:   default
Host:   localhost
Port:   50500
URL:   –
Type:   Live Server
Username:   admin

Source Path:   –
Excludes:   –
Target Name:   avm
Include In Auto Deploy:   No

Key input :
port: 50500
target : avm
( target must be specied).
Contrary to the getting started with WCM documentation that says 44100 for the server port and nothing for the target. And no separation between the above configuration for a local vs a remote deployment server.

/D.