AnsweredAssumed Answered

[Half Solved] HTTP WCM deployment receiver subsystem

Question asked by bnordgren on Apr 2, 2010
Latest reply on Apr 7, 2010 by bnordgren
I'm trying to override or configure a new type of the wcm_deployment_receiver subsystem category, which will publish a deployment receiver engine over HTTP from within the Alfresco repository. (e.g., not standalone).

The details of what I did are here:

Note, however, that most of the contents on that page are my attempt to adapt the "standalone" configuration to the repository environment. Right now, it represents what I expect to work instead of what actually works. And so I now ask for help.  :D

My first problem with the instructions on that page is that the http subsystem is not recognized and is not started, according to alfresco.log. So I copied the "…/wcm_deployment_receiver/http" directory to "…/wcm_deployment_receiver/default". I believe it is now reading my configuration files (because the first thing it did was complain of a namespace error, which I fixed.) However…

I point my browser to http://localhost:8080/alfresco/deployment and get Tomcat's 404 page. Same story at http://localhost:8080/deployment. My issue, I guess, is that I really don't have a good grasp of how to declare what URL the receiver should use, and hence what URL to type into the authoring server (when I get to that point).

So, two questions:
  1. Why did the original attempt to configure a separate http instance of an existing subsystem fail?

  2. How can I fix the publication of the service such that the URL I need to type into the authoring server is known?
PS: On the way to this wiki page, I wrote a lot of individual reference pages on each of the components.  They are all listed on the WCM Deployment category page. Note that everything I wrote is intended to be a "good starting point", so feel free to fix whatever is wrong, or add more pages to more fully describe the DM/AVM deployment targets, etc.