Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently setting up operational environment for our company, which includes installing Crowd for SSO, JIRA for bug tracking, and Confluence as our wiki. My idea is that all these products should be available via HTTP 80 on our internal development server (kinda http://dev/crowd, http://dev/jira, etc.) and will be available from the outside (for instance, Google Apps requires publicly available SSO server, so should work there).

I'm currently at a loss trying to choose good appserver for all these products. What I need is a Windows Server 2008 x64 R2-compatible appserver which is easy enough to set up and administer (GUI administration utilities will be nice, but I'm quite comfortable with console and configuration files) and wich can handle some 5+ applications for a 10+ people organization.

share|improve this question
up vote 5 down vote accepted

I've just been through this process (literally in the last week) with JIRA+Crowd+Confluence on a WinXP box. (not a 64-bit server OS but probably very similar)

It's not hard to set up Apache + the appropriate proxy info so from the outside you are accessing these via HTTP 80, but internally they run on Tomcat 8080 (or whatever your tomcat port is).

For most of Atlassian's features the install documentation is very good (I had a painful experience with installing the Apache::CrowdAuth connector, otherwise all has run smoothly). I'd suggest you look at their Apache+JIRA integration page for example.

share|improve this answer
Thanks, but no. Tomcat is well over my head. Plus, I'm planning to use Apache to only manage SVN repository, nothing more (yes, this might seem stupid, but Crowd requires Apache to work). – Anton Gogolev Oct 15 '09 at 14:02
Tomcat is pretty easy! I'm not even a real sysadmin, just a HW/SW developer experimenting around. If I can figure it out, you can too. – Jason S Oct 15 '09 at 14:05
I'm not a sysadmin either, but I really don't want to dig through piles of XML that Tomcat configuration is. – Anton Gogolev Oct 15 '09 at 14:06
Tomcat can be a pain in the butt, no doubt, but the XML configurations that comes with it is intrinsic to JSP...If you're looking to deploy some JSP apps, you're going to need to dig in it, at least a little bit. – Satanicpuppy Oct 15 '09 at 14:15
Atlassian apps aren't JSP (as far as I know), but they are .war files. – Jason S Oct 15 '09 at 14:32

If you are looking for a solution with all web-based administration, consider the Sun Java Web Server. It does the same job as Apache+Tomcat, including many advanced features such as WebDAV access and virtual servers. There are both free and commercial support options.

I don't have a lot of personal experience with the platform but I have heard good things about it's ease of use for non-admins

share|improve this answer

I setup Jira and Confluence on a windows machine some time ago. I used IIS as the basic web server and used ajp_iis to redirect specific URLs to the tomcat instances running on different ports. Works pretty well and was easy enough to set up.

share|improve this answer

JBoss is supposed to be able to run on any platform.

share|improve this answer

I agree with Jason S. Since, the Java-based application is doesn't include any EJB (enterprise Java beans) you can live without an application server like JBoss or WebSphere. All you need is a Web Container (Tomcat). In order for Apache to process Java request you need to compile Apache with mod_jk. Apache does not handle Java request out-of-the-box. All this stuff is pretty straightforward on *nix O/S.

Also, keep in mind Tomcat is a Web Container and not a Web Server. If you use JBoss, the front end that you use to connect to with your browser is actually stripped-down version of Tomcat- web container. Web Container isn't build to handle heavy requests. So, for production systems, you should always have load balanced web servers talking to tomcat/jboss instances.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.