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.

configuring deployment targets in WCM

btmspox

I'm running Alfresco "Version: Community Network - v2.9.0 (B 683)" and WCM 2.9. When I create a site, I get a single 'deploy to' line where I want to have the ability to specify a target name so I can use multiple targets on one server like what is shown here: http://wiki.alfresco.com/wiki/Deployment#Configuration.

What am I missing?

Find more posts tagged with

Comments

pmonks

Alfresco 2.9 is still using the old 2.1 configuration UI for Web Projects, where the "Deploy To" field contains a comma separated list of hosts to deploy to. The format for data in this field is explained in more detail in the online help (the little blue question mark button to the right of the field).

Cheers,
Peter

btmspox

Alfresco 2.9 is still using the old 2.1 configuration UI for Web Projects, where the "Deploy To" field contains a comma separated list of hosts to deploy to. The format for data in this field is explained in more detail in the online help (the little blue question mark button to the right of the field).

Is the new WCM configuration UI only in Enterprise and not in a Community edition at this time?

A comma separated list of servers to deploy the website to. Each entry either represents the location of a Deployment Receiver or an Alfresco Repository.

A file server entry must be prefixed with \\. Each server can be represented by a host name or an IP address and may also contain an RMI port number. If an RMI port number is not specified for a Deployment Receiver the default of 44100 will be used. If an RMI port number is not specified for an Alfresco Repository the default of 50500 will be used.

Example: \\liveserver1, \\liveserver2:44200, liverserver3, liverserver4:50900

Does this mean that Alfresco 2.9 does not support targets and instead I have to run a separate receiver on a separate port for each deployment directory?

pmonks

Is the new WCM configuration UI only in Enterprise and not in a Community edition at this time?

It's currently in 2.2E (which was released after 2.9C, hence the weird history of version numbers vs functionality), and I believe it was merged into community HEAD some time ago (but I might be wrong on that - you wouldn't believe how complex the merge history is! :wink

Does this mean that Alfresco 2.9 does not support targets and instead I have to run a separate receiver on a separate port for each deployment directory?

The FSR and deployment APIs have always supported multiple deployment targets, the limitation simply relates to the authoring side UI in 2.1 (both C & E) and 2.9C. You can either use a newer build that includes the new and improved configuration UI, or roll your own UI extension that exposes the underlying multi-target deployment support on any build (including 2.1C and 2.9C).

The wcm-deployment project on the forge (http://forge.alfresco.com/projects/wcm-deployment/) includes an example web script that programmatically initiates deployment. It doesn't specifically address this issue, but it wouldn't be too difficult to adapt to this case. Note that I haven't had time to prepare a downloadable AMP or anything for that project, so you'll need to checkout the code from SVN and build it yourself.

Cheers,
Peter

btmspox

It's currently in 2.2E (which was released after 2.9C, hence the weird history of version numbers vs functionality), and I believe it was merged into community HEAD some time ago (but I might be wrong on that - you wouldn't believe how complex the merge history is! :wink.

E being Enterprise, and C being community, which version numbers aside we consider separate branches that attempt to merge between each other, right?

Is 2.9B on SourceForge the same as 2.9C?

The FSR and deployment APIs have always supported multiple deployment targets, the limitation simply relates to the authoring side UI in 2.1 (both C & E) and 2.9C. You can either use a newer build that includes the new and improved configuration UI, or roll your own UI extension that exposes the underlying multi-target deployment support on any build (including 2.1C and 2.9C).

Using a newer community build amounts to trying to build from HEAD and seeing if the UI changes have been merged then? I only see the 2.9B release on Sourceforge from December 2007.

http://sourceforge.net/project/showfiles.php?group_id=143373

pmonks

Is 2.9B on SourceForge the same as 2.9C?

Yes. By "2.9C" I mean "version 2.9 Community edition, any patchlevel".

Using a newer community build amounts to trying to build from HEAD and seeing if the UI changes have been merged then?

You could do that, or you could download and install a nightly build (available from http://dev.alfresco.com/downloads/nightly/dist/).

Cheers,
Peter