> onto JRUN and how it all ties into IIS.
In general, the way it ties into IIS is the same as the way the standalone
CFMX "server configuration" does. When you run the web server configuration
tool, you associate one or more IIS virtual servers with a CFMX/JRun server
instance.
> Config Steps (as I did them):
>
> JRun Management console
> Created a new server called Test1
> Deleted default-ear from JRun4\servers\Test1\ Placed
> cfusion-ear into JRun4\servers\Test1\ JRun Management Console
> to start the Test1 server.
> Went into the J2EE components for Test1 and added CFMX as an
> Enterprise Application ColdFusion MX the context path is set
> to /TEST1 ColdFusion MX Document Root is set to D:\Web\Test1
Did you expand cfusion-ear and cfusion-war? I haven't tried doing an install
without manually expanding the EAR and WAR files as described in the MM
online documentation. When you expand the files manually, you shouldn't then
have to make any additional changes within the JRun management console, if I
recall correctly.
Did you edit the application.xml file within
\jrun4\servers\Test1\cfusion-ear\META-INF so that it has the correct context
root?
> I then opened up the JRun "Web Server Configuration Tool":
>
> JRun Host: localhost
> JRun Server: Test1
> Web Server: IIS
> IIS Website: ALL (for now)..until I understand how this all
> works Checked the "configure for CMFX box"
> Clicked OK.
>
> The site asnwers on: http://localhost:8101/Test1/index.cfm
> <http://localhost:8101/Test1/index.cfm>
>
> My questions are:
>
> How do I get the site to answer on port 80?
If you've configured IIS using the web server configuration tool, and your
IIS virtual server is listening on port 80, that should be all you need to
do.
> What If I want to deploy 3 instances of CFMX (1 per
> application) all answering on port 80?
>
> For example:
> http://localhost/Test1/index.cfm <http://localhost/Test1/index.cfm>
> http://localhost/Test2/index.cfm <http://localhost/Test2/index.cfm>
> http://localhost/Test3/index.cfm <http://localhost/Test3/index.cfm>
If you plan to have multiple applications within a single IIS virtual
server, each one will need a unique context root. You should then be able to
configure each to work with the same IIS virtual server using wsconfig. I
haven't actually done this too much, since most of the environments I work
with use a single application or a JRun cluster per virtual server, but it
should be pretty straightforward.
Alternatively, you could set up three different IIS virtual servers, and
configure each one to use a different CFMX/JRun instance. All three IIS
virtual servers could listen on port 80 as long as they use host-headers to
differentiate incoming requests.
You should've asked me this on Friday - I'd have been happy to demonstrate
it!
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]
