Configuring IIS with Websphere Plugin to access Domino webserver

Here is my revised version of Lotus’s Help File.It may help answer a few questions.

Hopefully!.

To install the Websphere plug-in on an IIS Server


Before beginning know about IIS and its configuration.

  1. Create the following folders on IIS machine (use any drive)

    :\websphere\appserver\bin

    :\websphere\appserver\config

    :\websphere\appserver\etc

    :\websphere\appserver\logs

  2. Copy from domino folders to newly created folders from step 1.

    • \domino\plug-ins\plugin-cfg.xml

      to

      :\websphere\appserver\config

    • \domino\plug-ins\w32\iisWASPlugin_http.dll

    to

    :\websphere\appserver\bin

    • \domino\plug-ins\w32\plug-in_common.dll

    to

    :\websphere\appserver\bin

  3. On IIS server, Open ‘Internet Information Service’

    i.e Right Click (r/c) on ‘My computer’ - Manage

    Expand 'Services and Applications'
    
    Click on 'Internet Information Service'
    
  4. Select Virtual Web Site and add ‘Virtual Directory’

    i.e R/c Default Web Site - New - Virtual Directory, select [Next]

  5. In the Alias editbox type in without quotes “sePlugins”, then select [Next]

    i.e Alias: sePlugins

  6. In the Directory editbox type in without qoutes and replacing with what was set in step 1,

    “:\websphere\appserver\bin”, then select [Next]

    i.e Directory: C:\websphere\appserver\bin

    (Assuming Websphere plugin is on C: drive)

  7. In Access Permissions allow the following

    Read

    Run scripts (such as ASP)

    Executables (such as ISAPI applications or CGI)

    Write

    Browse

    then select [Next]

    Special Note: if you receive a File Download when accessing db via IIS then you have not specified Executables

              you can adjust permission by
    
              a. R/C on sePlugins    (virtual directory of website) - Properties
    
              b. In tag, Virtual Directory, make sure that 
    
                   [ ] Read
    
                   [ ] Write
    
                   [ ] Directory Browsing
    
    
    
                   Executable Permission:    Scripts and Executables
    
  8. Select [Finish]

  9. R/C on ‘Internet Information Services’ - Properties

  10. On tag, ‘Internet Information Services’, Master Properties, select ‘WWW Service’ and [Edit]

  11. Select tag, ‘ISAPI Filters’ and [Add]

  12. Type for filter name withOUT quotes: “iisWASPlugin”

    i.e Filter Name: iisWASPlugin

  13. Type for Executable withOUT quotes: “:\WebSphere\AppServer\bin\iisWASPlugin_http.dll”

    i.e C:\WebSphere\AppServer\bin\iisWASPlugin_http.dll

    (Assuming Websphere plugin is on C: drive)

  14. Click OK until back at the mmc console ‘Internet Information Services’.

  15. Open registry edit (regedit) and navigator to ‘HKEY_LoCAL_MACINE \ SOFTWARE’

    Create Key withOUT quotes “IBM”, if not existing and enter

    i.e R/C on SOFTWARE - New - Key type, IBM

  16. Open, if existing, or create and open “WebSphere Application Server”

    i.e R/C IBM - New - Key, Type, Websphere Application Server

  17. Open, if existing, or create and open “4.0”

    i.e R/C Websphere Application Server - New - Key, Type, 4.0

  18. Select 4.0 and create new string value “Plugin Config”

    i.e R/C Websphere Application Server - New - String Value, Type, Plugin Config

  19. Double Click (D/C) on “Plugin Config” and set value to :\websphere\appserver\config\plugin-cfg.xml

    (Assuming Websphere plugin is on C: drive)

    i.e Plugin Config: C:\websphere\appserver\config\plugin-cfg.xml


Configure Websphere Plug-in


  1. Open file in Notepad, :\websphere\appserver\config\plugin-cfg.xml

    Note: change the Transport Hostname, Port and

–BEGIN–

<Server Name="default_server"> 

	<!-- The transport defines the hostname and port value that the web server 

	plugin will use to communicate with the application server. --> 

	<Transport Hostname="youdominoserver" Port="yourportnum" Protocol="http"/> 

</Server> 
<VirtualHost Name="*:*"/> 
<!-- searches for a match in the URL address -->

<!--  i.e "*.nsf*" would match any that contains .nsf in URL -->

    <!--     "*reports.nsf*" would only restrict to reports db -->

    <!--  if matched then pass to Transport Host

<Uri Name="*.nsf*"/>

<Uri Name="/icons/*"/> 

<Uri Name="/domjava/*"/> 

<!-- Uri Name="*.jsp"/ --> 

<!-- Uri Name="*.jsv"/ --> 

<!-- Uri Name="*.jsw"/ -->

<!-- Url Name="/servlet/*"/-->

<!-- Url Name="/download/*"/-->

<!-- Url Name="/mail/*"/-->

—END—

  1. Save and Close

Add to Domino Server


  1. Open in notes.ini in domino folder.

Add line below

HTTPEnabledConnectorHeaders=1

  1. Save and Close, restart domino server

    At console type without quotes “restart server”


Restart IIS and check to see plugin has loaded.


  1. On IIS server, Open ‘Internet Information Service’

    i.e Right Click (r/c) on ‘My computer’ - Manage

    Expand 'Services and Applications'
    
    Click on 'Internet Information Service'
    
  2. R/C on ‘Internet information Service’ - Restart IIS

  3. R/C on ‘Internet information Service’ - Properties

  4. R/C on ‘Internet Information Services’ - Properties

  5. On tag, ‘Internet Information Services’, Master Properties, select ‘WWW Service’ and [Edit]

  6. Check to see if all up arrows are green.

    If not all green then plugin dll has not loaded.

    Check the Log located in :/WebSphere/AppServer/logs/native.log

    change error detail (LogLevel) in the plugin configuration file

    :\websphere\appserver\config\plugin-cfg.xml

    Restart the IIS or wait one minute for the configuration file to be reloaded.


SPECIAL NOTES:

You cannot use Domino server and IIS with the same IP and port numbers will cause a conflict.

If you want to place on same server either specify transport host as 127.0.0.1 in plugin config file

or give another IP to the card or specify another empty port i.e 81

FAQ:

Q. Why would you want to use Websphere as a frontend and Domino webserver as the backend.

A. Senerio 1: Can use MS authenication to access both domino security and windows security,

           one logon only to windows.

Senerio 2: Can use websphere to restrict access to certain dbs behind a firewall without

           having to specify extra ACL entries for all your databases as what you have to 

           do when using domino webserver as front end.



i.e  in configuration file.  change <URI name="/*.nsf*"/> to  <URI name="/reports.nsf"/> 

reports.nsf is only passed to the transport webserver ("domino") when there is a match URL 

and all other references are passed only to IIS.

Senerio 3: Saves on buying extra domino servers for both intranet and internet webservers.

	IIS (free with OS) as front end

            domino as your lotus notes server with webserver enabled.

Subject: tnx!

Subject: Question to scenarios

Scenario 1How about active directory and single logon?

Scenario 2

Aren’t there some nice tools to manage all the ACL-Entries for notes databases?

Scenario 3

Would anybody who can buy a WebSphere care about one or even 10 additional Domino Servers?

(Just attended a workshop from IBM about websphere and Domino. A complete desaster for IBM because they weren’t able to show even the easiest feature of websphere. I did not work the whole day and they had to show print screens. I am still waiting for a convincing reason to buy a websphere)

Cti

Subject: Topic covered some time ago

Great article, but I covered this topic some time ago. You may want to have a look at the article I posted for some information / tips that haven’t been covered here.

http://www-10.lotus.com/ldd/nd6forum.nsf/0/33bd348aab606b5785256cfb002c0ffc?OpenDocument

Regards,

Alex