Red Hat Bugzilla – Bug 852705
DOC: 7.2.1. Configure a JBoss Enterprise Application Server 6
Last modified: 2012-11-08 17:11:07 EST
7.2.1. Configure a JBoss Enterprise Application Server 6 Worker Node
We work with Tomcats and Httpd in the scope of EWS2.
So the EAP6 configuration should be removed entirely? Copying Jean-Frederic as SME to confirm this.
Np it must be there as the EWS can be used as a frond-end to EAP6.
Just to clarify, Jean-Frederic, does this mean that we need to add content for Tomcat and Httpd as well, or can we just leave it at EAP6 only?
We need to add the configuration for Tomcats.
Jean-Frederic, could you point me to a working configuration for Tomcat Worker Node?
Hm your 7.2.2. Configure a Tomcat Worker Node in the doc looks ok now so I don't see what you need.
But the chap8 is still not ok: JBOSS_EAP_DIST/jboss-as/server/PROFILE/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml is wrong. in EAP6 there is only one file to configure the whole thing standalone/configuration/standalone-ha.xml. Note that the <mod-cluster-config/> are all OK except the first one:
<mod-cluster-config advertise='false" connector="ajp">
because it needs a proxy-list=something which you describe later in the doc.
chap8 in fact it is in 8.1.
Thanks, Jean-Frederic. Closing this bug now that 7.2.1 is OK and the issue in section 8.1. is tracked at the following:
It seems ok
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.