Hello Siju. The process is essentially the same for JRun 3.x. You can run
the "Connector Wizard" from the JRun Management Console (JMC), and that will
establish the connection (ISAPI filter installation) with IIS.
Also, the ISAPI filter doesn't "redirect" to the JWS HTTP port. In other
words, requests are only received over EITHER IIS's HTTP port (default 80)
OR the JWS's HTTP port (in your example, 8100). If you connect JRun to an
external Web server, then below the surface JRun is "listening" for HTTP
connections to IIS over a port (jcp.endpoint.main.port in local.properties),
but that's not an HTTP port.
HTH,
Patrick Quinn
Allaire Consulting
-----Original Message-----
From: [EMAIL PROTECTED]
To: JRun-Talk
Sent: 2/26/01 10:41 AM
Subject: How can the request be redirected by my web server directly to th e
servlet engine!
Hi All,
How can the request be redirected by my web server directly to the
servlet
engine!
i e say if my IIS/PWS 4.0 or onwards is running on port 80 and I have a
JRun
installation
i want to be able to type in http://myServerIP/servlet/MyServlet and not
http://myServerIP:8100/servlet/MyServlet
It finally means the requests made at port 80(IIS) would be redirected
to
the servlet engine which is running at a different port say 8100.
I think this facility was there in 2.3.1 and 2.3.3 and if I am not
wrong it
used to happen through installation of JRun as ISAPI Global Filter to
IIS...
thanks all!
bye
Siju.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
