22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

660 Lotus Security Handbook<br />

You need to ensure that your firewall and network environment limits traffic<br />

between the front-end and back-end servers, and that Domino only accepts<br />

traffic from the IP address of the Web server plug-in via the new IP filtering<br />

capabilities of Domino 6.<br />

Installing the plug-in on an IIS server<br />

Important: Some early documentation on these plug-in capabilities had an<br />

extra dash in the word PlugIn (it said Plug-In) in the name of the new string to<br />

create (“Plugin Config”) in the registry editor step. This is where you tell the<br />

plug-in the name of the configuration file, which in turn contains the name of<br />

the log file to create. Please pay particular attention because if you have typos<br />

in this string NAME the plug-in will not load and your only clue – the message<br />

in EventViewer – is quite obscure.<br />

This section provides some instructions for successfully installing the<br />

WebSphere Application Server plug-in on a Microsoft IIS server.<br />

1. Create the following directory structure on the IIS machine (you may use any<br />

drive), and copy the sample minimal configuration file from the Domino server<br />

to the IIS server:<br />

Copy data/domino/plug-ins/plugin-cfg.xml to<br />

c:\WebSphere\AppServer\config.<br />

Figure C-1 Directory structure that you must create in your C drive of IIS server<br />

2. Launch RegEdit.exe (open the Windows registry file) and create the following<br />

key path: HKEY_LOCAL_MACHINE - SOFTWARE - <strong>IBM</strong> - WebSphere<br />

Application Server - 4.0.

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

Saved successfully!

Ooh no, something went wrong!