FreeKB - Generate the web server plugin in WebSphere
Generate the web server plugin in WebSphere

Home > Search

Generating the web server plugin creates the plugin XML file (plugin-cfg.xml). 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 installed IHS web server, that you have installed the web server plugin, and that you have created a new web server in the dmgr.

Before you generate the web server plugin, you will want to map your WebSphere applications to a JVM or cluster and to your IHS web server. Let's consider an example where an app with a context root of /beta is mapped to both a JVM (server01) and web server (IHS).


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 plugin-cfg.xml file should automatically be updated to contain the apps.


If "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 newly created 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 SystemOut.log.

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


You can view the plugin by navigating to Servers > Server types > Web servers > your web server > Plug-in properties > View. The plugin-cfg.xml file should now have the context root of the app being requested, which is /beta in this example. There should only be one listing for each unique context root. If there is more than one listing, the plugin-cfg.xml file is misconfigured.

<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 propogate 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 in the box below so that we can be sure you are a human.