Thanks Patrick! It worked like a charm. The piece I missed was in not
noticing that the default website had a virtual directory /SCRIPTS
pointing at the InetPub/scripts. As soon as I added a "scripts"
virtual directory for my second website it started to work.
-----Original Message-----
From: Pat Quinn [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 02, 2000 9:16 PM
To: Hammon, Randy; 'JRun-Talk '
Subject: RE: JMC Connector Wizard Problem:If you don't select to install
i t as global filter, it doesn't add any filter
Hey Randy. The key to making this work is that you must create virtual
scripts directories under any new sites that you create in IIS. And each
virtual scripts directory must map to a unique physical scripts directory
under IIS. So, for example, create a /scripts2 dir under IIS, then map a
virtual scripts dir to that unde your new web site. When you run the
connector for a JRun server, you specify the unique scripts dir, and you're
all set.
Then, when you send a request to that new site's unique HTTP port, it
executes the jrun.dll in its own unique scripts dir (scripts2, in this
example), and points the request at the proper JRun server.
Try that.
HTH,
Patrick Quinn
Allaire Consulting
-----Original Message-----<SNIP>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
