22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

448 Lotus Security Handbook<br />

but the function that the API is performing may need or deserve to be<br />

implemented in a different architectural way to exploit the advantages of the new<br />

Domino 6 embedded HTTP stack architecture.<br />

As an example of one change in the Domino 6 API that could be a reason to<br />

re-write an R5 DSAPI, in the R5 DSAPI your code gets called for 100% of the<br />

times the “step” of the HTTP stack is needed (that is, DSAPI intercepting<br />

authentication requests will be called 100% of the time). However, in Domino 6,<br />

DSAPIs can be declared for individual Internet sites, so they are not called 100%<br />

of the time, and therefore performance may be improved.<br />

.<br />

For more information about the use of DSAPI in a single sign-on configuration,<br />

see 7.4, “DSAPI” on page 296.<br />

11.2.2 HTTP server plug-ins<br />

New for<br />

Domino 6<br />

Restriction: DSAPIs coded for R5 may crash the HTTP server if they allocate<br />

dynamic DSAPI memory to be used as private context outside of the new<br />

Domino 6-specific guidelines. This means that you - or your DSAPI<br />

application provider - may need to make some modifications to the R5 DSAPI<br />

application source and recompile it with the new toolkit. This is the price to be<br />

paid for the better memory stability of the R6-specific HTTP stack<br />

requirements.<br />

Domino R6 leverages the WebSphere Web server plug-in model. This feature<br />

replaces the “Domino for IIS” architecture that was provided in Release 5. This<br />

new model allows a third-party Web server like IIS to be the one “facing” the<br />

browsers and serving up static content (which is their speciality), and have all<br />

NSF requests be forwarded to the Domino HTTP stack. The plug-ins use HTTP<br />

to communicate with the Domino server, so the third-party HTTP server can sit in<br />

the DMZ with its plug-ins communicating to a Domino HTTP server sitting inside<br />

the firewall. The plug-ins support basic Domino back end services (core Domino<br />

database functionality, Lotus iNotes Web Access, Lotus Domino Off-Line<br />

Services (DOLS), Lotus Dis<strong>cover</strong>y Server), while all other HTTP traffic is<br />

ignored by the plug-in and handled by the front end HTTP server.<br />

This new plug-in architecture applies to all supported operating system platforms<br />

on which Domino runs, because the “plug-in” is not actually installed on the<br />

Domino server itself. Rather, the “plug-in” is installed on the “front end” HTTP<br />

server. The front end servers that are supported with the 6.0 release of Domino 6<br />

are:<br />

► <strong>IBM</strong> HTTP Server (IHS) on AIX, Windows NT 4.0, and Windows 2000 Server<br />

► Microsoft IIS on Windows NT 4.0 and Windows 2000 Server

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!