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.

Multiple Web Projects - Deploying to File System Receiver

bshort

We have a situation where we have multiple Web Projects that we'd like to deploy to the same file server using the File System Receiver. We're using Alfresco Enterprise 2.1.1 with the WCM.

Is this possible? If so, how do I configure this?

I see the "entry" nodes in the application-context.xml for the FSR, but is this for multiple Web Projects deploying to the same file server or to deploy one Web Project to multiple locations on the same server?

I also tried putting in a path in the "Deploy to:" field in the Web Project Details, but that didn't work at all. It looked like "\\localhost\test", btw.

Is this scenario even possible? Do we have to wait for 2.2 for this functionality?

Thanks,
-Brian

Find more posts tagged with

Comments

pmonks

This functionality is part of 2.2 - FSRs have always supported multiple targets, but the authoring side UI was only updated in 2.2 to allow different targets within the same FSR to be configured for deployment. There's a screenshot showing the new UI at http://wiki.alfresco.com/wiki/Deployment#Multi-server_Deployment.

Cheers,
Peter

bshort

We don't want to deploy one web project to multiple locations.

We want to deploy multiple web projects to different directories on the same file server.

Is this what 2.2 offers? Because that screenshot doesn't look like it does.

Thanks,
-Brian

pmonks

Alfresco WCM has always supported 1-to-many deployment to FSRs, but 2.2 adds support for many-to-1 deployment to FSRs. This is achieved via the (new in 2.2) "Target Name" configuration option visible in the screenshot - the intention being that different Web Projects may deploy to the same physical FSR (as identified by a hostname and port) but would deploy to different targets configured within that FSR.

Cheers,
Peter

bshort

Ah, I see. So then the TargetName fields would just match up with the key attribute on the entry node within the targetData block in the application-context.xml file in the deployment directory?

This is the snippet I'm talking about:

<property name="targetData">
            <map>
                <entry key="Data">
                    <map>
                        <entry key="root"><value>/opt/www</value></entry>
                        <entry key="user"><value>admin</value></entry>
                        <entry key="password"><value>admin</value></entry>
                        <entry key="runnable"><value>org.alfresco.deployment.SampleRunnable</value></entry>
                        <!–
                        <entry key="program"><value>/path/to/program</value></entry>
                         –>
                    </map>
                </entry>
                <entry key="default">
                    <map>
                       <entry key="root"><value>/opt/www2</value></entry>
                         <entry key="user"><value>admin</value></entry>
                        <entry key="password"><value>admin</value></entry>
                        <entry key="runnable"><value>org.alfresco.deployment.SampleRunnable</value></entry>
                        <!–
                        <entry key="program"><value>/path/to/program</value></entry>
                         –>
                    </map>
                </entry>
              
            </map>
        </property>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Neat!

Thanks,
-Brian

pmonks

Yep that's exactly it. Those snippets in the FSR's application-context.xml file have been there all along, but the authoring side UI couldn't deploy to anything but the "default" target in 2.1.

Cheers,
Peter