You're right, it's not that easy.
Of course your first question is answered by the original K.B., which tells you
to install JRun on both machines but only run the connector wizard on one.
Anyway, here are some more JRun 3.0-specific instructions for IIS and Apache:
Here's what you need in your web host's jrun.ini file (for IIS). For NES, it's
pretty much the same idea. For specific NES instructions, reply here and I'll
put some up unless someone else can figure it out:
The general config info needed for a distributed JRun/web server combo is:
#JRun host's IP (i.e., cannot be 127.0.0.1)
#JRun host's proxyport
#path to a local copy of local.properties
#Line or section to load the filter
*******
* IIS *
*******
Create a jrun.ini file in your scripts directory and manually install an IIS
connector using the metaset utility or using the IIS MMC controls to add an
ISAPI filter:
proxyhost=n.n.n.n #JRun host's IP (i.e., cannot be 127.0.0.1)
proxyport=nnnn #JRun host's proxyport
scriptpath=/scripts/jrun.dll #path to virtual scripts dir for this host
rulespath=C:/JRunProps/local.properties #path to a local copy of
local.properties
verbose=false
- Note that scriptpath needs to point to a _virtual_ scripts directory.
For this server I have a directory called Inetpub\scripts2 that this
particular virtual scripts dir is mapped to.
**********
* Apache *
**********
For Apache, at the bottom of your httpd.conf:
LoadModule jrun_module "/path/to/JRun/connectors/apache/OS/mod_jrun136.dll"
<IfModule mod_jrun.c>
JRunConfig Verbose false
JRunConfig ProxyHost n.n.n.n
JRunConfig ProxyPort nnnn
JRunConfig Mappings "/path/to/JRun/servers/server-name/local.properties"
</IfModule>
****************
* General Info *
****************
- verbose=[true|false] is optional as is the errorurl property
- proxyhost and proxyport need to point to your remote JRun host and its
proxyport
- rulespath/Mappings needs to point to a local copy of a local.properties file.
All the connector needs to read is the rules mappings for the JCP, so
UNIX/Windows
differences in the rest of the actual local.properties are irrelevant.
- jvmlist and jrun.rootdir properties in the web server config should be
commented out or removed.
- On the remote JRun server, proxyhost and proxyport have to match the
jrun.ini/httpd.conf, and you need to set jcp.endpoint.main.bindaddress to either
*
or the real IP (not the loopback) of the remote JRun server.
- JSP -- If you need to run JSPs off the web server machine, you need to
do a little more work, see below:
***************
* For JSP --> *
***************
You need to coinfigure the pathtrans properties for each JSP
directory/subdirectory concerned. The pathtrans section of global.properties is
somewhat ambiguously documented. What you need to do is put each
from dir of the web server and the to dir of the JRun machine. In this
case I already have a bunch of JSPs in my Apache docroot on Linux. So
I'm going to tell JRun that all requests for JSPs in /jsps/ should be
remapped to the Apache htdocs' /jsps/ dir. The names don't have to
match, though they happen to in this case:
1. Copy the pathtrans section from your JRun's global.properties to your
JRun's local.properties (I just stuck it at the bottom). Remember, the
local.properties on the local web server is just used for the rules
mappings. This change needs to be made on the machine hosting JRun, not
the web server machine's copy of local.properties.
2. Put in from and to dirs
3. Increment pathcount to n number of pathtranslations
4. All the JSPs being requested must be stored in the "to" dir(s) on the
JRun machine. If you want to put stubs for them on the web server machine,
that's fine. Then their names will show up if you have directory browsing
allowed, but they won't actually be served up if you click on them. Here's an
example section of pathtrans:
### pathtrans.properties
webapp.pathcount=2
webapp.path0.from=C:\\Inetpub\\wwwroot2\\jsps
webapp.path0.to=/usr/local/apache/htdocs/jsps
webapp.path1.from=C:\\Inetpub\\wwwroot2\\jsps\\sub1
webapp.path1.to=/usr/local/apache/htdocs/jsps/sub1
One problem: I tried mapping the IIS root to a dir on the JRun
machine. That doesn't work. I don't know if it will work with Apache. It may
be that I have to mapo a default JSP document for the web server or something.
The safest bet is to use subdirectories of the document root for JSPs for now.
Scott Stirling
-----Original Message-----
From: Louis [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 15, 2000 4:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Installing web server and Jrun on different machines
I don't think is that easy, how you configure httpd.conf in other mechine?
Jrun cannot access the other mechine and modify that file. Follow the
Jrun2.3 Faq doc,
We need to install Jrun on both mechine.
I wrote mail to Jrun support, what they reply is :
This is becoming a FAQ. I'll write up instructions on how to do this next
week. In the meantime, referring to the following Knowledge Base article
may help. The principle is pretty much the same for JRun 3.0 as for 2.3.3:
http://www.allaire.com/Handlers/index.cfm?ID=12420&Method=Full
But this is for Jrun2.3 not Jrun3.0. So, I still don't know how to
configure it.
If someone did it, please kindly give me details instruction.
Thank You.
Regards
Louis
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
