Let's assume a scenario involving one ColdFusion MX 7
instance installed on host 192.168.0.1, listening on port 51000,
one ColdFusion 8 instance installed on host 192.168.0.2, also
listening on port 51000, and one IIS instance install on host
192.168.0.3. It's possible to have both versions of ColdFusion
running on the same host, but you would most likely need to deploy
one or the other using the J2EE deployment method, and that's
outside the scope of this post.
By default, JRun allows access from hosts matching the mask
255.255.255.0, so security shouldn't be an issue. Connection
security is configurable in lib\security.properties. A more secure
installation might look like this:
jrun.trusted.hosts=192.168.0.3
You can use hostnames in place of IP addreses. In a clustered
configuration, we would include the addresses of the cluster peers
as well.
The JRun proxy service is disabled by default. This is the
service the connector uses to send requests to JRun. The enable the
service, set the deactivated attribute for the
jrun.servlet.jrpp.JRunProxyService service to false in
servers\<instance>\SERVER-INF\jrun.xml, e.g. <attribute
name="deactivated">false</attribute>, and restart the JRun
instance.
We'll now create the necessary connector configuration.
Create the following directory structure on your IIS 6.0 server
(these are just samples--if you plan to leave logging enabled,
you'll want the directories on a volume with sufficient available
disk space):
C:\JRun4\lib\wsconfig\1
C:\JRun4\lib\wsconfig\2
Using WinZip or another PKZip archiving tool, extract the
jrun_iis6.dll and jrun_iis6_wildcard.dll files from wsconfig.jar to
the following locations:
C:\JRun4\lib\wsconfig\jrun_iis6.dll
C:\JRun4\lib\wsconfig\1\jrun_iis6_wildcard.dll
C:\JRun4\lib\wsconfig\2\jrun_iis6_wildcard.dll
Create the C:\JRun4\lib\wsconfig\jrun_iis6.ini file with the
following values:
verbose=true
#errorurl=
This will enable verbose logging for debugging purposes. If
you want to specify an error page, uncomment errorurl (remove the
hash) and enter an appropriate URL, presumably one that doesn't
require JRun or ColdFusion for rendering.
Create the C:\JRun4\lib\wsconfig\1\jrun_iis6_wildcard.ini
file with the following values:
verbose=false
serverstore=C:/JRun4/lib/wsconfig/1/jrunserver.store
bootstrap=192.168.0.1:51000
apialloc=false
ssl=false
#errorurl=
proxyretryinterval=600
connecttimeout=30
recvtimeout=30
sendtimeout=30
Create the C:\JRun4\lib\wsconfig\2\jrun_iis6_wildcard.ini
file with the following values:
verbose=false
serverstore=C:/JRun4/lib/wsconfig/2/jrunserver.store
bootstrap=192.168.0.2:51000
apialloc=false
ssl=false
#errorurl=
proxyretryinterval=600
connecttimeout=30
recvtimeout=30
sendtimeout=30
The interval and timeout keys have been populated with their
default values. You can delete them or leave them commented out if
you wish. I prefer to keep the values documented in the INI file
itself.
In Internet Information Services (IIS) Manager, perform the
following steps:
1. Right-click the Web Service Extensions node in the tree
view and select "Add a new Web service extension..." from the
context menu. Name the extension "Macromedia Server Extensions" (or
"Adobe Server Extensions" or "JRun Server Extensions" or whatever)
and add the following files to the list of allowed files:
C:\JRun4\lib\wsconfig\jrun_iis6.dll
C:\JRun4\lib\wsconfig\1\jrun_iis6_wildcard.dll
C:\JRun4\lib\wsconfig\2\jrun_iis6_wildcard.dll
2. Right-click the site or application (directory or virtual
directory) you want to connect to the first instance of JRun and
select Properties from the context menu.
3. Select the Documents tab. Add index.cfm to the list of
default content pages if you want that functionality.
4. Select the Home Directory tab. Set Execute permissions to
at least "Scripts only." Click the Configuration button. Click the
Add button to add ColdFusion and JRun file extensions to the list
of application extensions. For all extensions, the executable path
is C:\JRun4\lib\wsconfig\jrun_iis6.dll, "All verbs" is selected,
"Script engine" is checked, and "Verify that file exists" is
unchecked. The default list of ColdFusion and JRun extensions is
.cfc, .cfm, .cfml, .cfr, .cfswf, .jsp, and .jws.
5. This is where the magic happens. While on the Home
Directory tab, click the Insert button to insert a new wildcard
application mapping. The executabe path is
C:\JRun4\lib\wsconfig\1\jrun_iis6_wildcard.dll, and "Verify that
file exists" is unchecked.
Repeat steps 2 through 5 for the second site or application;
however, in step use
C:\JRun4\lib\wsconfig\2\jrun_iis6_wildcard.dll for the
executable path.
At this point, your sites and/or applications should be
configured to connect to either 192.168.0.1
(C:\JRun4\lib\wsconfig\1\jrun_iis6_wildcard.dll) or 192.168.0.2
(C:\JRun4\lib\wsconfig\2\jrun_iis6_wildcard.dll). It's important
that the wildcard application mapping be configured correctly;
otherwise, JRun requests will not be routed to the correct JRun
instance.
I'm getting a bit winded at this point, so give this a try.
I've used the terms ColdFusion and JRun to mean almost the same
thing throughout the document. The key points to note are the
values in the various jrun_iis6_wildcard.ini files, the
configuration of the JRun proxy service, and the wildcard
application mappings for the site or application.
Let me know if you need me to expand on any particular
topic.
10
Replies
AdChoices