|
Home > Archive > WebLogic installation support > March 2006 > Weblogic 9, Coldfusion 7, Apache 2
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Weblogic 9, Coldfusion 7, Apache 2
|
|
| nathan.affleck@gmail.com 2006-03-25, 11:47 am |
| A bit confused on the proper setup of the above mentioned services.
Currently trying to create a development environment, so the developers
have a sandbox like environment. I would like to give them full access
to an httpd.conf, a weblogic admin console/domain, and coldfusion admin
page. Currently there are j2ee apps in development, and we are
migrating and moving towards using j2ee applications. Currently,
however, 90% of our web applications are written in coldfusion. My
thought was to create one big web environment utilizing all these
technologies.
I've successfully expanded and deployed the cfusion.war under weblogic,
with a context-root a name of "cfusion" (eg.,
http://hostname:7003/cfusion --- If I drop .cfm files in this context,
yes they are rendered properly. However I'd like apache to handle all
the front end requests, and when files end in .cfm, I'd like the
requests to be sent to the coldfusion application hosted under weblogic
for parsing. However, this seems to be different then when setting
coldfusion up as a standalone server. In this environment, and when
using the apache connector provided w/ coldfusion, you can basically
specify any root directory, so long as it's defined in apache's
httpd.conf. The .cfm is basically proxied. In weblogic, you can do
something like:
<IfModule mod_weblogic.c>
WebLogicHost xxx.xxx.xxx.xxx
WebLogicPort 7003
MatchExpression *.jsp
MatchExpression *.cfm
</IfModule>
<Location /cfusion>
SetHandler weblogic-handler
Debug On
PathTrim /cfusion
WLLogFile /webdev/inst1/httpd/logs/web_log.log
</Location>
But it's not quite giving me the desired effect of a standalone
server.
I would like to have this same behavior, but using weblogic. So that,
I can separate web applications, and not necessarily have to locate
them all under /cfusion/ --- I can sort of do this, by deploying
multiple coldfusion instances under weblogic (one for each separate
application), but it would be nice to just have one coldfusion
deployment that apache could forward it's request to (just like in a
standalone coldfusion setup) --- I don't want to setup the standalone
environment, because I would like to have multiple coldfusion instances
--- but just one for each developer.
Hope that makes sense - hope someone can help.
Nate
|
|
|
|
|