January 4, 2013

How to Install JBoss EAP 6.0.1 Native Components and Webserver Connector Natives for RHEL 6

When I wanted to install the JBoss EAP 6.0.1 native components and Webserver Connector natives on RHEL 6.3 I had some hard time. The only thing I knew was that I wanted to install them via RPM package, so I could get the nice built in management support for upgrades, reinstall and uninstall. But finding the correct packages was not that obvious.

As usual when knowing the answer everything is easy, which I'm going to present to you below.

First install JBoss EAP 6.0.1 via yum. That is described in the JBoss EAP 6 Installation Guide, which you can find here https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Installation_Guide/Install_JBoss_Enterprise_Application_Platform_6_using_the_Red_Hat_Network_RPM_installation.html

If you then grab the yum group info for that group package and then the list the installed file, you will see that the JBoss EAP 6 native components are already bundled in the jboss-eap6 group package.

If you do not want install the JBoss EAP 6 via yum, you can do that manually which for example is described here - http://www.opensourcearchitect.com/tutorials/instaling-eap-600-rhel-6x. But I do not recommend that for JBoss EAP 6, because it is already nice packaged. If you are installing JBoss EAP 5.x, you probably want to take that path, but no for JBoss EAP 6.

The next thing is to install JBoss EAP 6 Webserver Connector Natives, but before doing that you need to install Apache Web Server, which I have earlier described here, http://magnus-k-karlsson.blogspot.se/2013/01/install-apache-web-server-on-red-hat.html

After you have installed Apache Web Server you only need to install two packages.

After installation you can list the installed files.

As you can see from the list of installed files, the mod_cluster-native package have already added a configuration file for the Apache Web Server - /etc/httpd/conf.d/mod_cluster.conf. After restarted you Apache Web Server you can test you mod cluster, by open a web browser and point it to http://127.0.0.1:6666/mod_cluster_manager.

3 comments:

Zippisan said...

Great post. I like it and it was very clear to follow.

Thanks!

Magnus K Karlsson said...

mod_cluster.conf
--------------------------------------
# mod_proxy_balancer should be disabled when mod_cluster is used
LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
LoadModule slotmem_module modules/mod_slotmem.so
LoadModule manager_module modules/mod_manager.so
LoadModule advertise_module modules/mod_advertise.so

MemManagerFile /var/cache/mod_cluster


Listen 6666


KeepAliveTimeout 300
MaxKeepAliveRequests 0
ServerAdvertise on http://127.0.0.1:6666
AdvertiseFrequency 5
#AdvertiseSecurityKey secret
AdvertiseGroup 224.0.1.105:23364
EnableMCPMReceive


SetHandler mod_cluster-manager
Order deny,allow
Deny from all
Allow from 127.0.0.1


Anonymous said...

Since there is not a lot of search returns for Yum install freezes during JBOSS installation, I thought I would drop a solution in case it helps. There was an issue we couldn't resolve with our JBOSS expert from Redhat, so we removed the install of 6.1. I re-installed the customized version of base jboss, and there is another package for the JMS side (jboss-eap-6.1-rhel-native-1.0-1.el6.x86_64) which kept hanging up during install (via yum). Turns out there was a separate process for the cli that needed to be killed prior to running reinstall of the JMS package. Disabling the cli process was not included with removal of the install or shutdown of the JVM's and it was the middle of the night, so I missed it at first. The rpm dependencies didn't check for this. Once I hard killed (-9), the second install was successful, and we were able configure and load our test app successfully.
My little contribution to the community.