Strangely enough, although this setup seemed common and well documented, it took us more than one day and may problems solved to get it working right. The documentation on the net (how-to's and forums) is scattered and we had to collect informations from various sources.
We decided to document and publish here the complete setup and the list of problems we faced with their solution.
Goals
Placing JBoss behind Apache has several reasons:
- Various Net2Tel systems run on JBoss but we do not want a JBoss instance for each application because this would highly complicates system administration. On the other hand, having various applications on the same server implies that each application has its own application context
- User-friendly urls and subdomains: we want to map each application to the root of a different subdomain (igmc.net2tel.com.br, direto.net2tel.com.br).
- Ports: JBoss HTTP service uses port 8080 by default and we want to keep this. In particular we do not want to run it on port 80 for three reasons: (i) we do not want to run JBoss as root, (ii) we want to keep the flexibility to have some web content served from Apache (for example, PHP application), keeping port 80 for this (iii) it would be a configuration nightmare. On the other hand, we want to hide this port from the users (see above))
- Common and static content served directly from the web server, for obivous performance reasons
Clustering and load balancing are not (yet) amongst our goals. Our setup is limited to proxying and url rewriting. But load balancing should be easy to add and will be the next step.
Next step:
Apache basical setup
Posts
0 comments:
Post a Comment