IBM HTTP Server and WebSphere Application Server - Plugging in to one another

Note to self - if you see exceptions such as this: - 

[14/08/14 13:20:48:671 BST] 00000169 SystemOut     O PLGC0005I: Plug-in configuration file = /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PCCell1/nodes/AppSrv01Node/servers/webserver1/plugin-cfg.xml
[14/08/14 13:20:48:672 BST] 00000169 SystemOut     O PLGC0052I: Plug-in configuration file generation is complete for the Web server. PCCell1.AppSrv01Node.webserver1.
[14/08/14 13:20:56:029 BST] 0000014c SystemOut     O PLGC0062I: The plug-in configuration file is propagated from /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PCCell1/nodes/AppSrv01Node/servers/webserver1/plugin-cfg.xml to /opt/ibm/WebSphere/Plugins/config/webserver1/plugin-cfg.xml on the Web server computer.
[14/08/14 13:20:56:030 BST] 0000014c SystemOut     O PLGC0048I: The propagation of the plug-in configuration file is complete for the Web server. PCCell1.AppSrv01Node.webserver1.

[14/08/14 13:20:56:030 BST] 0000014c SystemOut     O PLGC0063E: The propagation of the plug-in configuration file from /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PCCell1/nodes/AppSrv01Node/servers/webserver1/plugin-cfg.xml to /opt/ibm/WebSphere/Plugins/config/webserver1/plugin-cfg.xml on the Web server computer failed.
[14/08/14 13:20:56:030 BST] 0000014c SystemOut     O PLGC0049E: The propagation of the plug-in configuration file failed for the Web server. PCCell1.AppSrv01Node.webserver1.

 [14/08/14 13:27:49:141 BST] 0000014d SystemOut     O PLGC0064I: The plug-in keyring file is propagated from /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PCCell1/nodes/AppSrv01Node/servers/webserver1/plugin-key.kdb to /opt/ibm/WebSphere/Plugins/config/webserver1/plugin-key.kdb on the Web server computer.
[14/08/14 13:27:49:141 BST] 0000014d SystemOut     O PLGC0069I: The propagation of the plug-in keyring is complete for the Web server. PCCell1.AppSrv01Node.webserver1.
[14/08/14 13:27:49:142 BST] 0000014d SystemOut     O PLGC0065E: The propagation of plug-in keyring file from /opt/ibm/WebSphereProfiles/Dmgr01/config/cells/PCCell1/nodes/AppSrv01Node/servers/webserver1/plugin-key.kdb to /opt/ibm/WebSphere/Plugins/config/webserver1/plugin-key.kdb on the Web server computer failed.
[14/08/14 13:27:49:142 BST] 0000014d SystemOut     O PLGC0070E: The propagation of the plug-in keyring has failed for the Web server. PCCell1.AppSrv01Node.webserver1.
[14/08/14 13:27:49:158 BST] 0000014d MBeanHelper   E   Could not invoke an operation on object: WebSphere:name=PluginCfgGenerator,process=dmgr,platform=common,node=dmgr,version=8.5.5.2,type=PluginCfgGenerator,mbeanIdentifier=PluginCfgGenerator,cell=PCCell1,spec=1.0 because of an mbean exception: com.ibm.websphere.plugincfg.exception.PluginConfigException: PLGC0070E: The propagation of the plug-in keyring has failed for the Web server. PCCell1.AppSrv01Node.webserver1.

check that the Node Agent is running.

In the WAS 8.5 world, the remote management of IHS is undertaken by the Node Agent, rather than the IHS Admin Server Instance ( adminctl etc. ).

This, of course, assumes that WAS and IHS are tightly coupled, which may go against the suggested WAS security hardening routines such as: -

Advanced security hardening in WebSphere Application Server V7, V8 and V8.5, Part 1: Overview and approach to security hardening

Advanced security hardening in WebSphere Application Server V7, V8 and V8.5, Part 2: Advanced security considerations

Bottom line, check your non-functional requirements, including security, when deciding whether IHS/Plugin should be tightly wired to the WAS cell / Deployment Manager.