[opencms-dev] OpenCMS 6 contet distribution/delivery options

[Arash Kaffamanesh]

Hello,

 

We are working on a very large OpenCms WebSphere integration project, where
we distribute content statically to the filesystem and synchronize it with
WebSphere Portal Filesystem via rSync as XHTML definition, after that the
content Portlets use this content with regard to the metdata written in the
metatags of the exported data and present it to different users with
different roles. For that someone has to write a custom AfterPublishHandler
which provides also the Navigation Structure for the Portal as XML
Definition. The Portal will have more than 10.000 pages provided through 100
Editors for 120.000 Users. The System is installed on 12 Production and QA-
Systems and near to 10 local Dev. Servers :-)

 

Viva OpenCms!

 

Kind Regards,

 

--

arash kaffamanesh 

http://www.pomegranate.de

global portal & content management solutions

 

 

 

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Harri Johansson
Sent: Dienstag, 22. August 2006 11:17
To: opencms-dev at opencms.org
Subject: Re: [opencms-dev] OpenCMS 6 contet distribution/delivery options

 

 

basically there are two things coming to my mind:

1 - opencms has a static export feature. Content that is published, can 
be written out to the filesystem and then served statically


Yes, I'm aware of the export feature and I have studied that as an option.
 

 

2 - there is a commercial module from Alkacon that allows to do staging
between opencms servers. This allows to do content creation on one
server and then the content can be replicated to a productive server (or
 several of them as this module is also said to support clustering of
opencms servers). I have no experience with it, however.


I'd like to keep OpenCMS as far from the actual on-line transaction ie.
last-mile content delivery as possible. To keep architecture clear and to
eliminate all unnecessary failure points and performance bottle necks the
separate application server will handle the content delivery to the users
from separate repository to which OpenCMS should deploy it's content. 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20060822/e2006591/attachment.htm>