Lance JSP Stuff Bill Theseus

JRun 2.3 Multihoming on NT IIS

Wednesday, June 09, 1999 3:36 PM

Here is some information I posted to the livesoftware.jrun newsgroup a while back. It seemed to help the fellow there (though he says he "disinstalled IIS4 and reinstalled again, now everything works perfectly.").

Here is what I did (from memory):
  1. set up virtual hosts in IIS4 with explicit, fully qualified host names (virtual.host.com).
  2. gave each virtual host a /scripts mapping to inetpub/scripts
  3. in jrun admin for jse service, added a line-item to the "Multihome" tab for each virtual host. Enter the fully qualified host name, the full path to the servlets/jsp directory you want, and the full path to the log directory you want. Note: I set these up *outside* of the JRun directory, so that they wouldn't get touched in the event of an uninstall/reinstall later (c:\servlets\host1\, c:\servlets\host1\logs, for example).
  4. Note: the above applies if you want each vhost to use the same jsm. If you want each one to use a different jsm, see "Multihosting" below. (added 09/20/99).
BTW: The ISAPI filter for jrun.dll is set in the Master WWW properties, not in the "children". A long time ago (when we first installed Jrun) we saw the "red arrow" problem, but I don't recall how it was resolved. Make sure that you are placing the correct jrun.dll (from /connectors/intel-win) in the scripts directory. Also, confirm that the .jsp extension is properly mapped: in Home Directory tab, click Configuration. There should be a mapping for ".jsp" to "scripts/jrun.dll".

JRun Multi-Hosting for IIS

Darren Jerrard (ed: Lance Lavandowska)
  1. First, read "Multi-hosting sites using JRun and IIS 4.0"
  2. When you add a 'connector' to IIS, a '.dll' and a '.ini' file are written to the 'scripts' directory you specify. The '.ini' contains the port number for the connector proxy of the JSM.
  3. If you have only the one 'scripts' directory and add a connector for 'jsm-default', 'jsm-server2' and then 'jsm-server3', what will happen is 'jsm-server2' will overwrite the '.ini' (including the connector proxy port number) from 'jsm-default' which will in turn be overwritten again by 'jsm-server3'. The end result is that all jsps will compile and execute through 'jsm-server3'.
  4. each site under IIS needs its own '/SCRIPTS' virtual directory.
  5. I've got four 'scripts' directories and four 'jsm-xxx's. Each JSM has had a connector added to a different 'scripts' directory. This works fine. The .jsps compile into their own directories.
  6. Note: In JRunAdmin, you must put different port numbers in the EndPoint Settings for the 'jcp' and 'jws' for each JSM. The 'jcp' port number is the one that gets written out to the '.ini' file. Also, in the General tab of JrunAdmin, set a unique 'Service Manager Admin Port' number.
  7. Additional Resources From Allaire
Click Here!