So I take it you mean you go to
http://yourhost/index.jsp and get a tomcat-served page, and go to
http://yourhost/svn/ and get a subversion repository? Or something like that?
Basically, what I'd suggest is ... if you want to replicate the old behavior, try to do a bit of analysis on what it's actually doing. See if you can see running apache processes ("ps -ef | grep httpd" or "ps -ef | grep apache" depending on what you're doing).
If you access your svn over http/https, then you
do have an apache2 instance on the old server. In which case, it's probably got config files in /etc/httpd, /etc/apache2, /usr/lib/apache2, /usr/lib/httpd, or /usr/local/apache2. If you have slocate installed and maintained, you could try "locate httpd.conf" to find that out. The meat might also be in included conf files (eg: a "vhosts" or "modules" directory).
If all your requests are handled on the same incoming port (ie: it's all
http://yourhost/something), and you've got both apache and tomcat, then more likely than not you've already got an instance of the JK connector working too. Check your apache config files for more details.
I'm making a lot of guesses about how your other system is set up though. Since you've got one that appears to be doing what you want, it'd be great to reference that one. If you can't for whatever reason, then I'd say, start out by installing apache (in rhel4, just use up2date to install that), then get the
subversion module working, then get tomcat working on a different port (like 8080 ... I'm guessing you know how to do that), then the JK connector forwarding the requests that you want forwarded from apache to tomcat.
There's a lot of documentation for
apache,
subversion, and
the tomcat JK connector out there. Without more specific questions, I don't think it's really possible to elaborate too much more. There's a bit of system research you need to do if you want to replicate your other system's functionality.