Using URI mapping to setup an Edge Reverse Proxy with Domino iNotes V6.5
 Technote (troubleshooting)
 
Problem(Abstract)
Configuring the Edge Proxy to work with iNotes using the Domino webmailredirector.nsf database.
 
Cause
Edge Proxy must be configured properly to work with Domino iNotes.
 
Resolving the problem
The following configuration works for HTTP or HTTPS client-side into the proxy; then, HTTP from the proxy to the iNotes backend servers.

In the ibmproxy.conf file, the following lines must be uncommented, so that they are processed:


On Microsoft Windows platforms:

# ===== Junction URL Rewrite Plug-in =====
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

On UNIX platforms:
# ===== Junction URL Rewrite Plug-in =====
ServerInit /opt/ibm/edge/cp/lib/plugins/mod_rewrite/libmod_rw.so:modrw_init
Transmogrifier /opt/ibm/edge/cp/lib/plugins/mod_rewrite/libmod_rw.so:modrw_open:modrw_write:modrw_close:modrw_error


JunctionRewrite On

SendRevProxyName No
RuleCaseSense on
NoProxyHeader Accept-Encoding

  1. Uncomment the proxy rules to uniquely identify each backend iNotes server:

    map /server1.com/*    /s1/*
    map /server2.com/*    /s2/*
    map /server3.com/*    /s3/*

    proxy /s1/*  
    http:// server1.com/*
    proxy /s2/*  
    http:// server2.com/*
    proxy /s3/*  
    http:// server3.com/*
    proxy /*    
    http:// server1.com/*

    ReversePass
    http:// server1.com/*  https:// proxy.com/s1/*
    ReversePass http:// server2.com/*  https:// proxy.com/s2/*
    ReversePass
    http:// server3.com/*  https:// proxy.com/s3/*

    This enables a client to go to http:// proxy.com, which sends them to the server1.com iNotes server. From there, server1.com authenticates clients using the Domino webmailredirector.nsf to redirect the client to the correct server.

  2. On each of the Domino iNotes servers you must disable the page compression through the Domino console:

    Domino > names.nsf > server configuration document > domino web access tab > Compress HTTP response dat


If you want to do HTTPS or Secure Socket Layers (SSL) throughout, SSL from the client to the Proxy and SSL from the Proxy to Domino iNotes, change the following:

proxy /s1/*   https:// server1.com/*
proxy /s2/*   https:// server2.com/*
proxy /s3/*   https:// server3.com/*
proxy /*      https:// server1.com/*

ReversePass https:// server1.com/*  https:// proxy.com/s1/*
ReversePass https:// server2.com/*  https:// proxy.com/s2/*
ReversePass https:// server3.com/*  https:// proxy.com/s3/*

If you have a layering of the URLs with broken pages in the client browser; for example:

https:// proxy.com/s1/server1/..... or
https:// proxy.com/s1/s1/......

you must add the following to the ibmproxy.conf:

NoJunctionUrlPrefix /server1.com/*
NoJunctionUrlPrefix /server2.com/*
NoJunctionUrlPrefix /s1/*
.....

If you are using a V4.0 proxy, you must be at V4.0.2.31 or at a higher fix level for this to work. If you are using V5.0, you must be at V5.0.2.10.

If you continue to have problems, take a Proxy trace and call IBM Support at 1-800-IBM-SERV.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Windows
Software version: Edge Server 2.0.x
Software edition:
Reference #: 1162818
IBM Group: Software Group
Modified date: Nov 13, 2008