Getting content from the WCM

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.

mvlach

Hi, is there possible this ?

I have Server A (S1) with instaled jboss + alfresco + alfresco virtual tomcat. This is located in net 10.0.0.0. I would like to deploy WCM content (live web application) to the productive server on the net 88.8X.XXX.XXX. But there is no access to the net 10.0.0.0 - security reason.

Alfresco Store ———————> Live Productive Server

How can I access to the Alfresco Store, how to use ContentLibrary from the WSF project ? I have implemented my own content library which locate the XML documents in the classpath and check XPath queries, but this is not good solution - the search couldn't be possible.

Can somebody tell me, how to do ? Is the solutions the Alfresco 2.2E Beta (with alfresco to alfresco deployer ?)

Thanks Mila

pmonks

Can servers on the 10.x.x.x subnet access servers on the 88.x.x.x subnet?  If so you should be fine - Alfresco's deployment functionality (both to FileSystem Receivers and to Alfresco Runtimes) is pure push.  When a snapshot is deployed, the authoring instance connects to the deployment target(s) and pushes the content out.  The deployment target(s) never connect back to the authoring instance.

This works well with the typical network topology for an internet site, where the authoring instance and virtualisation server are located on the internal network, while the FileSystem Receiver(s) and Alfresco Runtime(s) are located out in the DMZ, along with the front end application server and web server.  To support Alfresco in this scenario you need to have outbound holes in your firewall, but don't need any inbound holes in your firewall (which is usually acceptable to network security folks).

Also, Alfresco to Alfresco deployment has been supported since 2.0 and Alfresco to Filesystem deployment was added in 2.1, so you don't need 2.2 in order to leverage these components.  In fact the only significant deployment related changes in 2.2 were some UI optimisations - the core functionality is still much the same.

Cheers,
Peter