> through JRUN... Which might be an issue.
I have no idea whether you can autodeploy CFMX in that way. I was under the
impression that you couldn't, because if you could, why would MM tell you to
go through all the manual hassle?
> This too might be a problem, because I have the following
> path to the applicatiion.xml file
> C:\JRun4\servers\Test1\SERVER-INF\temp\cfusion.ear1555075785\META-INF
> (yikes!)
Actually, I'm not sure that by itself will cause a problem, but I really
don't know too much about how autodeployment of J2EE applications works. I
do know that the MM instructions tell you to rename "cfusion.ear" to
"cfusion-ear" when deploying manually. I'm not sure whether this is because
you can't use dots within directory names, or because those instructions
also tell you to use the name "cfusion-ear" for your directory and the
values simply have to match.
But in any case, I'd just stick to the MM deployment instructions, as they
do work well enough.
> I guess I need to get my terminology straight... I am looking
> to have each application run in its own environment
> (context?) (separate cf admins for each application) and at
> the same time be listening on port 80. I'll start over and
> see if I can make some headway.
If I recall correctly, this shouldn't be a problem. Each instance will have
its own CF Administrator interface, and you'll get to those interfaces
through the context root:
http://servername/contextroot/CFIDE/administrator/index.cfm
However, by default, I'm not sure that these paths will work through IIS.
Even if they do, you might want to use the JRun web server for accessing the
CF Administrator interfaces, rather than using IIS - you'd only use IIS for
public access to each instance in that case. That's generally how I've
handled it, in the few cases that have come up.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
