Hi Douglas,
The clustering setups in Jahia are a bit limitating for the moment and
we will introduce as soon as we can more options. The problem is that
Windows itself is not that flexible for clustered file systems. All the
setups we recommend for the moment involve mostly UNIX type of setups.
Regards,
Serge Huber.
Douglas Doyer wrote:
Hi Serge,
I do not have the intention of mixing different OS (or softwares) in a same
cluster. I currently experienced two Jahia farm (Windows and Linux).
On the Jahia-Linux farm, the solution is perfect and it does not seem to have
limitation. On the Jahia-Windows farm, I note that the solution is not as well
adapted. I understand that UNC path of Microsoft is not a universal solution,
but without it I don't believe that the Cluster-Windows solution is an
acceptable solution (for big organization).
I can conclude from these tests that Jahia can only be put in cluster with
Linux (in a context which the solution functions and which it is well
integrated with the other products and the operating system).
If an organization is ready to live with these limitations, she will be able
put Jahia in cluster with Windows.
This email does not aim to degrade the solutions offered by Jahia, but to
expose the problems in order to share my experiment. I understand that
creating solutions for multiple platforms is something very difficult. I I
appreciate your answer.
Thank you.
-----Message d'origine-----
De : Serge Huber [mailto:[EMAIL PROTECTED]
Envoy� : 13 mai 2005 05:05
� : [email protected]
Objet : Re: Running Jahia with a Windows Server Account and Having Jahia in
clustering
Hi Douglas,
All the recommended configurations for clustering are based on the
assumption that you used the EXACT same software configuration on all
nodes. We do not recommend mixing operating systems, and even different
versions, as you may run into unexpected problems.
In the case of clustering just under Windows, I must say I have little
experience with it. The support of UNC (by the way UNC is not really
"universal", it is Windows SMB specific) paths is dependant not on Jahia
but on the possibilities of file system access by the Java JVM.
If you have the opportunity, I would recommend setting up the cluster
with RedHat nodes rather than Windows ones. You will have less trouble
with setup.
Regards,
Serge Huber.
Douglas Doyer wrote:
Hi,
I currently experienced Jahia in "Load Balancing" with Windows 2003
and Linux Redhat. While following documentation "Jahia Clustering
how-to ", I note that we must change some variables path of Jahia in
order to work (See section " Microsoft Windows Sharing ".
Windows Context
--------------------------------------------------------------------------------------
In a context that we would like to have both:
- Jahia under a Windows service account
(http://www.jahia.org/jahia/Jahia/devzone/pid/454#3 ) ;
- And Jahia in cluster.
The solution that I considered was this one:
1. Create a network drive on another server or via DFS (in order to
obtain reliability);
2. Assign a letter to this new drive (by using the net use command
with a logon script) for the service account of Tomcat;
3. Assign a service account to the Tomcat service (for all server
member of the Jahia farm) in order to authenticate to the
network share.
The problem is on mapping a network drive for a service account. In
reference to the Microsoft article � Q180362 INFO: Services and
Redirected Drives � http://support.microsoft.com/kb/180362/EN-US/ :
A service should not directly access local or network resources
through mapped drive letters. Additionally, a service should not use
the WNet/XXXXXXX/ APIs to add, remove, or query any mapped drive
letters. Although the WNet/XXXXXXX/ APIs may return successfully, the
results will be incorrect. A service (or any process that is running
in a different security context) that must access a remote resource
should use the Universal Naming Convention (UNC) name to access the
resource. UNC names do not suffer from the limitations described in
this article.
The question is:
Is this possible to specify a UNC (universal naming convention) path
instead in the Jahia.properties file? I don't see any workaround.
I tested a logon script to the service account, but without success
because the session was not open by the GUI interface (Windows Console).
If Jahia does not support UNC path, do I have to understand that the
only way of running Jahia in cluster is by leaving an open sessions on
the console for every server? By reading documentation, I thought that
the only limitation was the failover support for the shared folders
Thanks.
