FreeKB - IBM WebSphere Web server plugin (plugin-cfg.xml) - Generate using the dmgr
IBM WebSphere - Web server plugin (plugin-cfg.xml) - Generate using the dmgr

The web server plugin is used to create a communication channel between IBMs IHS web server and a WebSphere application server.


This assumes you have already done the following:

Generating the web server plugin creates/updates the plugin XML file (plugin-cfg.xml).


global vs. unique plugin-cfg.xml files

By default, the dmgr has a global web server plugin at Environment > Update global web server plug-in configuration. However, a significant limitation with the global web server plugin is that there is not an option to automatically generate / re-generate or propagate the plugin-cfg.xml file from the dmgr to your IHS web server. The generation / regeneration / propagation would have to be done manually. For this reason, a unique plugin-cfg.xml is almost always used. The global web server plugin is located at:



You'll want to generate / re-generate a unique plugin-cfg.xml file. The unique plugin-cfg.xml file will be located at located at:



Automatically generate the plugin-cfg.xml file

In the left panel of the dmgr, expand Servers > Server types > Web servers > your web server > Plug-in properties. If Automatically generate the plug-in configuration file is checked, then the ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/servers/your_server/plugin-cfg.xml file will be updated when a change is made to the master configuration file.


Manually generate the plugin-cfg.xml file

If you are using the global web server plugin, select Environment > Update global web server plug-in configuration > Overwrite to manually regenerate the plugin-cfg.xml file. 


If you are using unique plugin-cfg.xml files and "Automatically generate the plug-in configuration file" is not checked, at Servers > Server types > Web servers, check mark the web server and select Generate Plug-In. In this example, after generating the plugin, the location of the updated plugin-cfg.xml file is displayed.



To verify that the plugin-cfg.xml file was successfully generated, you can check for event PLGC0052I in the dmgr HPEL or SystemOut.log.

PLGC0052I: Plug-in configuration file generation is complete for the Web server. yourCell01.yourNode.yourWebServer


You can view the plugin in the dmgr. The plugin-cfg.xml file should now have the context root of the app being requested, which is /beta in this example.

<UriGroup Name="default_host_yourCluster_URIs">
  <Uri Name="/beta/*"/>


In this example, URI /beta maps to the UriGroup named default_host_yourCluster_URIs. There should be a routing tag that contains the UriGroup, and this will list the cluster that the app is in, as well as the virtual host being used. You will want to ensure that the application resides in the cluster. Typically, virtual host "default_host" is used.

<Route ServerCluster="yourCluster" UriGroup="default_host_yourCluster_URIs" VirtualHostGroup="default_host"/>


You can also ensure that the ports listed for the default_host are the ports that the web server and WebSphere application server are using for the app.

<VirtualHostGroup Name="default_host">
  <VirtualHost Name="*:80"/>
  <VirtualHost Name="*:443"/>
  <VirtualHost Name="*:9080"/>
  <VirtualHost Name="*:9081"/>
  <VirtualHost Name="*:9443"/>
  <VirtualHost Name="*:9444"/>


Next, you will propagate the plugin from your WebSphere application server to your IHS web server.

Add a Comment

We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.

Please enter 2a4e2 in the box below so that we can be sure you are a human.


Web design by yours truely - me, myself, and I   |   |