[opencms-dev] R: Question about OCEE Cluster and Replicator

[Marantelli Luca]

Hi Michael and thanks for your fast reply
What you wrote is very clear and you confirm my idea of environment. I have other some. Maybe I repeat myself but it's necessary to understand better some aspects before purchasing the module.
In documentation I read that the replication module must be installed on the workplace server. So in my environment this means that the editing server (the private machine where also admin can confirm contents network) is ALWAYS the workplace server (the blue circle in cluster documentation, that in my case is not a production server). Is this right?

In your previous post you wrote:
"The scenario you describe has one dedicated machine only for content 
editing. So this machine is not delivering content to the public. But 
as I said above, if your content editing machine is accessible from the 
web, you could use it for content delivery (=production) as well."

What is not clear is when you say that if the machine is accessible from the web, this machine can publish also contents to the 3 productions server. I don't think that this machine must be accessible from the web if it can "see" the 3 production servers with private ip. Am I wrong?

thanks

-----Messaggio originale-----
Da: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Per conto di Michael Emmerich
Inviato: mercoledì 14 aprile 2010 16:15
A: The OpenCms mailing list
Oggetto: Re: [opencms-dev] Question about OCEE Cluster and Replicator

Hello Luca,


> I downloaded the trial version of OCEE module
>
> I have an environment with 3 production servers with 3 OpenCms instances
> that are on the same database.
>
> I configured the cluster module on these servers. In documentation I see
> that one of these must be the workplace server. This means that editors
> must login on that to edit contents?

This is correct. In an OCEE-Cluster all content editing must be made on 
one of the cluster nodes.

 > And on the same server the users
> that have the role of "Approvers" for the contents must login and decide
> if publish or not?

This is correct.
The normal workflow in OpenCms is:
1) The content editor edits some content, but has no right to publish 
it. The content editor can see his changes in the Offline project.
2) The Project manager (=Approver) checks the cotnent and publishes it. 
The published content can then be accessed from the web.

So you could use the same OpenCms instance for content editing and 
approval in the offline project and for content delivery in the online 
project.

>So this is not a production server.

No, of course you can still use this machine for delivering the content 
as well. When you publish something on this machine, the content will be 
accessible.


> What I need is an environment where I have 3 production server and
> another server for editing and approving contents.

This would be a scenario which has a total of 4 OpenCms servers. Three 
for content delivery and one for content editig only.

 > Then from this server
> should be a replication of this contents on the 3 production servers. So
> I suppose I must have a editing server inside network (not public) with
> its own database where editors can edit contents and where
> administrators can approve these contents, and from this server Admins
> can decide to publish "online" the resources. At this point the OCEE
> replicator replicates these contents on the database of the 3 production
> instances.

You described it correctly, this is how most OCEE Cluster/Replication 
installations are set up: One internal server to edit the cotnent with 
its own database. Several external servers to deliver the content.
There are two ways how you can transfer content form the internal server 
to the external ones: This can be dome automatically when you publish 
the content on the internal system (most installations work like this) 
or this has to be done manually after you have published it.

> Is this right? Is this possible?

Yes, this is possible.

 > If I'm right why I need a workplace
> server on production environment (in OCEE documentation file
> documentation_ocee_cluster.pdf is the blue circle at page 3)? I suppose
> the blue instance is the one where editors edit contents and where Admin
> decide what to publish online, so not a production machine.

The scenario you describe has one dedicated machine only for content 
editing. So this machine is not deliviering content to the public. But 
as I said above, if your content editing machine is accessible from the 
web, you could use it for content delivery (=production) as well.


> So the right solution should be an OpenCms instance with its own
> database in the private network and 3 public instances of OpenCms
> pointing all to the same database (but different from the workplace
> server in the private network). Is this correct?

This would be a setup as it it mostly done with OCEE cluster/replication.

> So I need to install OCEE cluster module on the 3 production instances
> and the replicator on the other one (the private one) and tell the
> replicator that every content must be published on the production
> database after admin has confirmed that the contents are ok.

The cluster module must be installed on all servers. The replication 
module must be installed on the workplace server (= content editing server).

Of course you must take care that you firewall settings allow that the 
workplace server can communicate with all other servers in your OCEE 
Cluster.

Hope this helps.


-- 
Kind Regards,
Michael.

-------------------
Michael Emmerich

Alkacon Software GmbH  - The OpenCms Experts
http://www.alkacon.com - http://www.opencms.org


_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev

AVVERTENZE AI SENSI DEL D.LGS. 196/2003    . 

Il contenuto di questo messaggio (ed eventuali allegati) e' strettamente confidenziale. L'utilizzo del contenuto del messaggio e' riservato esclusivamente al destinatario. La modifica, distribuzione, copia del messaggio da parte di altri e' severamente proibita. Se non siete i destinatari Vi invitiamo ad informare il mittente ed eliminare tutte le copie del suddetto messaggio     .               

The content of this message (and attachment) is closely confidentiality. Use of the content of the message is classified exclusively to the addressee. The modification, distribution, copy of the message from others are forbidden. If you are not the addressees, we invite You to inform the sender and to eliminate all the copies of the message.