iNotes Webmail with reverse proxy server
EDUAN
I Am trying to set up a reverse proxy using Websphere edge server's Cache
Proxy component sitting on a DMZ accessing multiple Domino servers on the
internal network using iNotes. On the reverse proxy ibmproxy.conf file I
have added the following:
ServerInit
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_init
Transmogrifier
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_open:modrw_
write:modrw_close:modrw_error
JunctionRewrite on
Proxy /xxx/* http://xxx.mydomain.com/*
Proxy /yyy/* http://yyy.mydomain.com/*
But when I access http://reverseproxy.mydomain.com/xxx/mail/mailfail.nsf it
tells me that it can't find my mail file if I do a right click on the error
page and go to properties and look at the actual URL it shows e.g.
http://reverseproxy.mydomain.com/mail/mailfile.nsf/iNotes/Welcome/?OpenDocum
ent&ui=inotes instead of
http://reverseproxy.mydomain.com/xxx/mail/mailfile.nsf/iNotes/Welcome/?OpenD
ocument&ui=inotes
Any ideas on how I can sort this one out. I Have load Websphere Edge Server
version 2.0 with PTF2 on Windows 2000. According to the PTF documentation
this issue was sorted out in this fix.
Regards
Eduan Naude
email: eduan...@tcm.co.za
JLee
Try using the cookie implementation of the JunctionRewrite. The
standard (page rewrite) version only handles certain types of links, and
unfortunately Domino uses other types in various places. That causes
those links to be skipped and passed through to the client, causing the
failed GET later on. The cookie version doesn't rewrite any data, just
adds a proxy cookie so that the Proxy can recognize the rule that should
be applied for subsequent requests. The doc for PTF2 should describe
how to enable that option, I think it was something like
"JunctionRewrite on usecookie" ...something like that.
Jeff
EDUAN
Thanks for the info, but I have basically spent a whole day searching
Websphere Edge Server update documentation, Websphere Edge Server support
web site, Notes.net and basically the internet in general and could not find
any other options for "JunctionRewrite [on|off]". These are the only two
options available according to the documentation and I agree fully with your
solution, but where can I find some documentation on this additional
parameter "usecookie" and the correct format to enter this parameter.
Regards.
Eduan.
"JLee" <le...@NOSPAMus.ibm.com> wrote in message
news:3F030AF3...@NOSPAMus.ibm.com...
JLee
Hmm...I believe when a new version is installed, there should be an
ibmproxy.conf.new file created (not sure under what directory). That
should have any new directives or comments added to the standard config.
Check and see if that exists on your machine, if not, let me know and
I'll find a copy of the current config file and send it to you.
Looks like the PTF2 doc only has the base JunctionRewrite information
and not the cookie enhancement data.
Jeff
EDUAN
Thanks for input so far. I searched the ibmproxy.conf file and it did not
even contain the standard "JunctionRewrite [on|off]" directive in it after I
installed PTF2 I had to manually add the following:
ServerInit
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_init
Transmogrifier
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_open:modrw_
write:modrw_close:modrw_error
JunctionRewrite on
I Found this odd as the PTF2 update info stated that these directive are
added by the installation of PTF2. So I seached the entire system for any
other ibmproxy.conf file and did not find any. I Thought that something had
gone wrong with the install of PTF2 and then removed everything, installed
the product and the PTF again. Same results.
So I would really appreciate it if you could mail me a ibmproxy.conf file
with all the correct directives to get this working.
Regards.
Eduan.
"JLee" <le...@NOSPAMus.ibm.com> wrote in message
news:3F09F66...@NOSPAMus.ibm.com...
JLee
I sent you an email with the access information for service2; however,
it turns out the fix I mentioned (4.0.2.14) is for the rewrite plugin
version of JunctionRewrite and not the cookie version. You should be
fine with PTF2 code. Also, as I say in the email, if you continue
experience problems with this, I would recommend opening a PMR with the
IBM L2 support team. They can provide direct phone support to debug
faster and if a code fix is necessary, then it will have to come through
their team and not through this newsgroup.
Jeff
JLee
Sorry, I meant to also mention that the Edge Server V2 package (which
contains Caching Proxy v4) is the last version of Edge Server. That has
now become the Edge Components of the WebSphere Application Server. WAS
V5 was the first version of that and it contains the Caching Proxy v5
code (released late last year). Edge Components also contains the Load
Balancer v5 code (used to be Network Dispatcher v4 in Edge Server v2).
Jeff
EDUAN
I Though just for the purposes of the newsgroup I would post the resolution.
What is quite interesting though and I thought I would just mention it to
you is that there are two instances of the Cache proxy out there but they
are not at the same level. The first one is the one I was trying to use
which is bundled with the Websphere Edge Server package. With this version
the Caching Proxy Server falls over when you try and use the "UseCookie"
directive, even with PTF2 loaded. The second instance of the Cache Proxy
Server comes bundled with Websphere Application Server V5.0 on the Edge
Components CD, but you have to load Fixpack 1 for this version which takes
you to V5.0.1 of the Websphere Edge Components package and this works with
the "UseCookie" directive and is documented in the Fixpack documentation
You need to coment out the JunctionRewrite plugins
#ServerInit
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_init
#Transmogrifier
C:\Progra~1\IBM\edge\cp\lib\plugins\mod_rewrite\mod_rw.dll:modrw_open:modrw_
write:modrw_close:modrw_error
And Add
JunctionRewrite on UseCookie
Also enable the
SendRevProxyName yes
and add mappings
Proxy /server1/* http://server1.mydomain.com/*
Proxy /server2/* http://server2.mydomain.com/*
and once you have done this it should work.
Regards
Eduan.
"JLee" <le...@NOSPAMus.ibm.com> wrote in message
news:3F0DBD19...@NOSPAMus.ibm.com...