nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to configure remote/test deployment alfresco runtime

tamilraj2003

I am trying to configure "Alfresco Server Receiver". Is the Deployment Receiver and "Alfresco Server Receiver" are same?

In my Alfresco (webapp, where I do create/maintain my content), how do I link the "Alfresco Server Receiver" with it.

If I choose "Deploy" action in my staging sandbox, it just shows only localhost. How can I change the config, so that it lists/shows me the new "Alfresco Server Receiver"?

Find more posts tagged with

Comments

kvc

The Alfresco Server Receiver (ASR) is an Alfresco server. This receiver creates a new repository (your web project live with the word "live" appended to it, visible via CIFS and the node browser), syncs it with the contents of your staging sandbox (the snapshot you are deploying), and then indexes the content (so you can query) and snapshots. Subsequent deployments all do an efficient diff and incremental deployment. You can see this best in 2.2 BETA, which gives you a running history of all your deployment reports.

The File-system Receiver (FSR) is just some remote file server that you've installed our lightweight, Spring-based Java application. It provides the same incremental, transactional deployment as to the ASR. You typically use this for your static websites and your application code.

You can refer to your Deployment page on our wiki for more details.

Kevin

tamilraj2003

hi Kevin,

Thanks for the reply. I am using alfresco 2.9B. I downloaded alfresco-community-deployment-2.9.0B.zip and trying to use it. Is it a ASR or Deployment Receiver?

From the alfresco web app, how can I deploy my content to this new remote service?

kvc

Ah, the deployment config wizard is part of our upcoming 2.2 Enterprise maintenance release - it was need to close some support cases. It'll make its way in Community next drop, which I believe should be in the March timeframe (a WIP in terms of planning still).

The file-system receiver is the separate installable AlfrescoDeployCommunity-2.9.0B-Setup.exe downloadable on SourceForge. The Alfresco server receiver is actually just part of the base server. When deploying between two Alfresco servers, the underlying mechanism is AVMSyncService. AVMSyncService is what's used to compare and sync any two files, file versions, diretories, directory versions, repositories, or repository versions. That what we use when commiting changes to a workflow sandbox (a repository with a layered directory on Staging to set a context of existing files and folders) and a staging sandbox. Deployment leverage SyncService over the wire to compare against a repository on some other machine - but it's essentially doing the same compare and sync operation.

The point of all this: you don't have to do anything to replicate content between Alfresco servers, other than specify the name of the remote server and click the deploy icon. It's kinda all done for you.

2.2 adds some nice GUI controls to showcase some more advanced capabilities (source path, exclude patterns, etc.). That'll once again find it's way into Community in some number of weeks.

You can read up on Deployment and how it works (at least the 2.2 version of it) on our Deployment page on our wiki.

Deployment is kinda cool. There's lots more coming here.

Kevin

tamilraj2003

hi Kevin,

There are too many names used in the Wiki & discussion forums, which are little confusing. This is my understanding, can you please validate?

'file-system receiver' and 'deployment receiver' are same. It is installable using the AlfrescoDeployCommunity-2.9.0B-Setup.exe or the alfresco-community-deployment-2.9.0B.zip. This is just to expose deployed file system as per the JCR 170. This is NOT a alfresco runtime. is that correct?

"Alfresco Server Receiver" is actually an alfresco runtime, to be used to access the deployed "content". It is not available as part of community edition, but will be available in few weeks.

The 'Deployment' documentation in Wiki is really very generic and not having any precise details (or explaining the step by step details to work with ASR or FSR.

My question is I am using Alfresco 2.9B community edition. What are the options I have for deployment and how to do it. (Please again don't redirect me to 'Deployment' documentation in Wiki, which I have done already and couldn't figure out much). I would appreciate your help on this.

thanks
Selva

kvc

'file-system receiver' and 'deployment receiver' are same. It is installable using the AlfrescoDeployCommunity-2.9.0B-Setup.exe or the alfresco-community-deployment-2.9.0B.zip. This is just to expose deployed file system as per the JCR 170. This is NOT a alfresco runtime. is that correct?

Yes, the file-system receiver and deployment receiver is the same. This receiver is used to incrementally deploy assets out of the Alfresco repository to a regular file-system. This is good for application code or static HTML pages, for example.

"Alfresco Server Receiver" is actually an alfresco runtime, to be used to access the deployed "content". It is not available as part of community edition, but will be available in few weeks.

No, actually that your Alfresco server receiver has been part and parcel of each Alfresco Community and Enterprise build since our April 2.0.1. So you are good to go here. The only difference for a future Community release would be the new deployment config wizard included in the Create Web Project Wizard.

My question is I am using Alfresco 2.9B community edition. What are the options I have for deployment and how to do it. (Please again don't redirect me to 'Deployment' documentation in Wiki, which I have done already and couldn't figure out much). I would appreciate your help on this.

For configuration options for the file-system receiver, you'll need to look at your application-context.xml Spring config file for your deployment receiver. For your Alfresco server receiver, the config options are hard-coded, and do require the either 2.2E or a future Community build.

Kevin

tamilraj2003

hi Kevin,

Thanks for the reply. Now it makes sense. I just have one more question.

is it possible for me to deploy from my "alfresco community edition 2.9.0B" to a remote alfresco? if so, how to do that?

regards
Selva

kvc

Yup. All you have to do is install Alfresco on a second server. Then, in your Web Project Settings, provide the name or IP address of that remote instance. Then, click the deploy icon next to any Staging sandbox. Then, you're done. You don't need to do anything else on the remote system other than install it and run it.

Kevin

sbarr

Can you help me understand the background process when deploying to an ASR? The Wiki explains that the two servers are using RMI, is that correct? My concern is that my ASR will be deployed in my DMZ and I'm not sure how much traffic this is going to generate.

Is the deployment process a batch/push or are both servers talking back and forth for synchronization? Also, I saw in the wiki that the user can initiate the deployment but can the deployment be scheduled and if so how can we configure that? I saw the section about 'auto deploy' is there a way schedule the deployment (after workflow approval) for a more favorable hour say, in the middle of the night when server traffic is low?

Thanks in advance… apologies to tamarilraj2003 if I'm taking this in a different direction.

damonsmith

I haven't found any docs for installing or configuring the File System Receiver.

I barely managed to find the downloadable package on sourceforge inside the WCM downloads

pmonks

There's a readme with installation / configuration instructions inside the FSR download bundle.

In a nutshell, all you need to do is extract the bundle to a directory of your choosing then run the "deploy_start" script. This will default to writing the deployed content to the directory "./target" - you can (and arguably should) reconfigure this to be the absolute path of the directory you wish content to be deployed to.

Cheers,
Peter

damonsmith

I missed the fact that it's the separate deployment package. I've installed it now and it's receiving files fine. I guess I should put in a bug that the run script still lists commons-logging-1.0.4, and the jar in the package is 1.1 though.