CONFIGURING
About this task
In order for the plug-in to relay requests to the target IBM® Domino® server, you must add directives to plugin-cfg.xml to define a transport route to the server, and pattern rules for the URL namespaces that identify requests which are to be relayed to Domino. The plug-in will only relay requests that match a namespace rule. All other requests will be handled by the front-end Web server.
Procedure
1. Open plugin-cfg.xml in Notepad.
2. Modify the <Transport> element to target the appropriate Domino server. To do this, change the Hostname and Port parameters to the proper values required for the plug-in to reach your back-end server's HTTP task. For example:
<ServerGroup Name="default_group">
<Server Name="default_server">
<!-- The transport defines the hostname and port value that the web server
plug-in will use to communicate with the application server. -->
<Transport Hostname="mydomino.server.com" Port="81" Protocol="http"/>
</Server>
</ServerGroup>
<Uri Name="/*.nsf"/><Uri Name="/icons/*"/><Uri Name="/domjava/*"/><Uri Name="/execcgi/*"/><Uri Name="/cgi-bin/*"/><Uri Name="/servlet/*"/><Uri Name="/download/*"/><Uri Name="/mail/*" />
If your Domino application requires additional namespaces, you can create <Uri> directives for those patterns also.
Note: All the WAS plug-ins automatically reread the configuration file once a minute to pick up changes. If you don't want to wait that long, you must stop and restart the front-end Web server. In the case of the IIS plug-in, you must stop the World Wide Web Publishing Service from the Windows services control panel, then restart the Web site from the Internet Services Manager. Just stopping and restarting the Web site by itself won't work because the plug-in DLL won't be reloaded.
Related information "plugin-cfg.xml file" in WebSphere Application Server Version 6.1 Information center