To install the WebSphere plug-in on an IIS server
Do the following to install the IBM® WebSphere® plug-in on the IIS server and enable it for a Web site. Before beginning this procedure, you should be familiar with the Internet Information Services (IIS) Manager configuration tool. On Microsoft® Windows® 2000/2003, this tool is accessed through the Microsoft Management Console.
1. Create the following directory structure on the IIS machine (you may use any drive);
2. Download the Web server plug-in files for WAS from IBM software downloads – Trials and demos Web site.
Follow the instructions, according to platform, that display on the Web site.
3. Copy the plug-in files to the IIS server.
1. Copy data/domino/plugins/plugin-cfg.xml to c:\WebSphere\AppServer\config.
2. Copy data/domino/plugins/<WAS version>/w32/iisWASPlugin_http.dll to c:\WebSphere\AppServer\bin.
4. Start the Internet Information Services Manager application.
5. Create a new Virtual Directory for the Web site instance you want to work with WebSphere. To do this with a default installation, expand the tree on the left until you see “Default Web Site.” Right click on “Default Web Site” and select New – Virtual Directory. This opens the wizard for adding a Virtual Directory.
6. In the Alias field, enter “sePlugins.”
7. In the Directory field, browse to the WebSphere bin directory (C:\WebSphere\AppServer\bin).
8. For access permissions, check “Execute” and uncheck all other permissions.
9. Click Finish. A virtual directory titled “sePlugins” is added to your default Web site.
10. In this step, follow the appropriate procedure for your version of Windows.
On Windows 2000:
1. Right-click the machine name in the tree on the left and select Properties.
2. On the “Internet Information Services” tab, select “WWW Service” in the “Master Properties” drop down box and click Edit.
3. In the “WWW Service Master Properties” window, click the “ISAPI Filters” tab.
On Windows 2003:
4. Right-click the individual web site to enable for the plugin.
5. Click “ISAPI Filters.”
11. Click Add. This opens the “Filter Properties” dialog.
12. In the “Filter Name:” field, type “iisWASPlugin.”
13. In the “Executable:” field, click Browse. Open the WebSphere bin directory and select “iisWASPlugin_http.dll.”
14. Close all open windows by clicking OK.
15. In this step, follow the appropriate procedure for your version of WebSphere.
o For WebSphere 4.0/5.0 plugins:
Open the Windows registry file and create the following key path: HKEY_LOCAL_MACHINE – SOFTWARE – IBM – WebSphere Application Server – <WAS version>. Select this last key and create a new string value “Plugin Config”. Set the value for this variable to the location of the plugin-cfg.xml file (C:\WebSphere\AppServer\config\plugin-cfg.xml)
o For WebSphere 6.0 plugins:
Create a text file that contains the full path to the plugin-cfg.xml file (including the file name) and save the text file in the C:\WebSphere\AppServer\bin directory as “plugin-cfg.loc.” For example:
16. To enable the plug-in for additional Web sites, repeat Steps 4 through 8.
For more information, see Configuring Microsoft Internet Information Services (IIS) in the WebSphere Application Server Information center.
Configuring IIS with WebSphere
The Default Web Site of the IIS server is used as examples in this section. You can choose another existing Web site, or create a new Web site.
Installing Appeon Server Web Component to the IIS Web root
Run the Appeon setup program and install Appeon Server Web Component to the Web root of the IIS Web site, for example, the Web root for the Default Web site is C:\Inetpub\wwwroot.
If you have installed Appeon Server Web Component to another location, then you should copy the entire “appeon” folder from the installation directory of Appeon Server Web Component to the IIS Web root.
IIS 6: Installing the redirector plug-in
Since IIS works on the Windows platform only, you must get redirector plug-ins from WebSphere running on Windows (not UNIX or Linux). For example, if you plan to use IIS as the Web server while Appeon Server is installed to WebSphere on Sun Solaris, you must copy the redirector plug-in from WebSphere on Windows to the IIS Web server.
1. Copy the iisWASPlugin_http.dll file from the %WAS_HOME%\bin\ folder to any location of the IIS Web server, for example, C:\Inetpub\wwwroot\AppeonWeb. If IIS and WebSphere reside on the same machine, you do not need to copy the file.
2. Open Control Panel | Administrative Tools | Internet Service Manager.
3. Right click the Default Web Site and select New | Virtual Directory from the popup menu.
4. Create a virtual directory using the name “sePlugins” and set the virtual directory to the folder where the iisWASPlugin_http.dll file is located.
5. Enable Read, Run script, and Execute permissions on the virtual directory.
6. Right click Default Web Site and select Properties from the popup menu.
7. On the ISAPI Filters tab, click Add, and install iisWASPlugin_http.dll as an ISAPI filter. Filters are invoked in the listed order. Appeon recommends that you install iisWASPlugin_http.dll first in the list. Click OK.
Filter Name: appeon_filter
8. Restart IIS for the new configuration to take effect. Go to the ISAPI Filters tab and verify that iisWASPlugin_http.dll has been loaded successfully (indicated by a green arrow pointing upward while a red arrow pointing downward indicates that the DLL file was not successfully loaded).
Adding virtual host in WebSphere console
1. Click Environment > Virtual Host in the navigation tree of the WebSphere Administrative Console.
2. Click the New button in the page that displays.
3. Input the IP address of the Web server in the Host Name field and port number in the Port field.
4. Click Environment > Update Web Server Plug-in in the console navigation tree.
5. Click OK to update the Web server plug-in.
6. Save the new configuration and restart the WebSphere server.
IIS 6: Configuring the plugin-cfg.xml file
Copy the plugin-cfg.xml file from the %WAS_HOME%\config\cells\ folder to the virtual directory and modify the following directives according to the Appeon Server\WebSphere environment:
Configure the log file location. For example:
<Log LogLevel=”Error” Name=”C:/Inetpub/wwwroot/_vti_log/http_plugin.log”/>
Configure the IP address and port number of the Appeon Server\WebSphere. For example:
<Transport Hostname=”22.214.171.124″ Port=”9080″ Protocol=”http”/>
<Transport Hostname=”126.96.36.199″ Port=”9443″ Protocol=”https”>
<Property name=”keyring” value=”C:/Websphere/AppServer/etc/plugin-key.kdb”/>
<Property name=”stashfile” value=”C:/Websphere/AppServer/etc/plugin-key.sth”/>
Configure the context path. For example:
IIS 6: Creating the registry key
In the registry of the IIS Web server, locate the “HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server\188.8.131.52” key (if any of these are missing, create them), add the “Plugin Config” string and set the value to the directory of the plugin-cfg.xml file.
Additional configuration for IIS 6
1. Activate ISAPI:
Open the IIS manager.
Click Web Service Extensions on the left side of IIS manager.
Select All Unknown ISAPI extensions on the right of the window and click the Allow button on the left.