Domino 7 and Websphere 6 on Windows

Encouraged by the ease you can make Domino 6.5 and Websphere 6 to work together in all areas (HTTP, LDAP, Single SignOn) I tried my luck with Websphere 6 and Domino 7. Unfortunatly the Websphere plug-in installer doesn't offer Domino 7 as an option (nota bene: in R7 the location of a lot of Java stuff has moved like where to find Notes.jar). So I gave the 6.5 selection a shot. The LDAP integration worked smooth like silk, however the HTTP integration did not happen. The DSAPI filter entry wasn't created. So I peeped on the R6 installation and added the DSAPI filter name:
domino5_http.dll. When I restarted the HTTP task I was greeted with an error message:

ERROR: WebSpherePluginCfg variable not defined in notes.ini
      Define variable WebSpherePluginCfg=Location_Of_plugin-cfg.xml
      in notes.ini and restart the server

ERROR: WebSphere HTTP DSAPI filter initialization failed.  Return code = 3

Hhm. A quick check on plugin-cfg.xml files showed, that there is only on in the Plugins/config/templates directory. That for sure doesn't fit into an active configuration. Luckily there is a Plugins/bin/configurewebserver1.batcommand file which should do the trick. Unfortunatly it terminates with an error too. Well I won't let them quit to easy on me, so I had a look into the batch file. Websphere uses an amazing mix of batch files calling each other The parameters in the file look like this:

"C:\Java\WebSphere60\AppServer\profiles\default/bin/wsadmin.bat" -conntype NONE -f "C:\Java\WebSphere60\AppServer\bin\configureWebserverDefinition.jacl" webserver1 DOMINO "N:\\" "N:\\Domino7\\names.nsf" 80 MAP_ALL "C:\\Java\\WebSphere60\\Plugins" unmanaged rohandaNode01 rohanda windows

The error stated the input parameters like:
Input parameters:

  Web server name             - webserver1
  Web server type             - DOMINO
  Web server install location - N: N:\ Domino7\names.nsf
  Web server config location  - 80
  Web server port             - MAP_ALL
  Map Applications            - C:\Java\WebSphere60\Plugins
  Plugin install location     - unmanaged
  Web server node type        - unmanaged
  Web server node name        - webserver1_node
  Web server host name        - windows
  Web server operating system - ...nothing here ...

So it looked like the "N:\\" wasn't such a good parameter. I replaced it with a wild guess:   "c:\\Program Files\\Lotus\\Domino" and the installation batch file stated the right parameters and got very busy configuring the server. At this point I'm not sure if that wrong parameter is caused because of Domino7 or because the Domino server binaries are located on a different drive that the Domino data. Restarting the Domino still complained about the missing Websphereplugincfg. So back to square one and some peeping how it runs on the Domino6. There should be a plugin-cfg.xml in the C:\Java\WebSphere60\AppServer\profiles\default\config\cells\rohandaNode01Cell\nodes\rohandaNode01\servers\webserver1which isn't there.
So another try.... stay tuned