Geekflare is supported by our audience. We may earn affiliate commissions from buying links on this site.
In WebSphere Last updated: September 6, 2022
Share on:
Invicti Web Application Security Scanner – the only solution that delivers automatic verification of vulnerabilities with Proof-Based Scanning™.

Putting your WebSphere behind Web Server is essential for various reasons including performance, security, and scalability. If you are working as a WebSphere administrator or just started then one of the tasks you will be involved in is to connect IHS with WAS.

On high-level, you need to do following in order to implement managed web server.

  1. Download Web Server Plug-ins for WebSphere
  2. Install Plug-ins
  3. Add Web Server into WebSphere
  4. Configure Plugin into Web Server

Following abbreviations are used in this article.

  • IHS – IBM HTTP Server
  • WAS – WebSphere Application Server
  • ND – Network Deployment
  • IM – Installation Manager

This assumes you have IHS and WAS installed on Linux environment. The following demonstration is based on WebSphere ND 8.5.5 and IBM HTTP Server 8.5.5.

You may use IBM WAS with other web servers like Apache, Nginx or IIS as well. However, WebSphere is nicely integrated with IBM HTTP Server through Web Server Plug-in.

Download Web Server Plug-ins for WAS

In order to implement IHS in front of WebSphere, you need to have Web Server plugin installed. You can download the plugin from IBM website.

  • Visit the following link
  • Enter your information and confirm. You will be directed to a download page where you will have two tabs. Click on “Download using http” tab.
  • Look for plug-ins and download both files


  • Once downloaded, you should have following two files. You can transfer this to IHS server.
-rw-rw-r--. 1 chandan chandan 696338913 May 10 04:52
-rw-rw-r--. 1 chandan chandan 961156085 May 10 04:56
  • Let’s extract both files

Install Web Server Plug-in using IM

It’s time to install the downloaded plugin through Installation Manager.

  • Launch IBM IM, usually it will be under /opt/IBM/InstallationManager/eclipse/IBMIM
  • Click on File >> Preferences
  • Click on Add Repository
  • Click on Browser and select the repository.config file, which you got after extraction
  • Click ok and OK again


  • Click on Install on IM Wizard


  • Select the version and click Next


  • Accept the license and Next
  • Select the directory where you wish to install the plugin. By default, it will install under /opt/IBM/WebSphere/Plugins. If you are ok with it, click Next


  • Select the 64-bit runtime environment for Java and Next
  • Review the summary and click on Install to begin the installation


It may take some time and once done, you will get confirmation – The packages are installed. Click on Finish.


This concludes plug-in is installed successfully and time to configure them.

Add Web Server in WebSphere Console

  • Login into WebSphere Administrative Console
  • Click on Servers>>Server Types>>Web servers


  • Click on New


  • Select node – leave it to default if IHS is running on the same server as WebSphere else select the node of web server
  • Enter the Server name
  • Select Type as “IBM HTTP Server” and click next
  • Leave the default web server template, click next


  • Port – if HTTP Server is running on different port than 80 then change here
  • Web server installation location – verify IHS is installed here else change the location
  • Plug-in installation location – verify if plugin is installed here else change it
  • Click next


  • Review the web server definition and click Finish


  • You will get a confirmation about new server created successfully and option to review the changes. Click on review


  •  Select checkbox for “synchronize changes with Nodes” and click Save


  • It will take few seconds to synchronize the changes. Click OK


  • It will display the newly added web server in the list


It’s time to generate & propagate the plug-in now. Select the newly added web server and click on first

Generate Plug-in

And then click on

Propagate Plug-in


It will take few seconds and give you plug-in path.


This is the plugin you need to use in HTTP Server. Let’s configure this in httpd.conf of IHS.

Add Plug-in in IHS (httpd.conf)

There are two things you need to do in httpd.conf file to make IHS talk to WebSphere using a plugin.

  1. Add
  2. Add plugin-cfg.xml path
  • Go to the conf path of IHS. By default it will be under /opt/IBM/HTTPServer/conf
  • Take a backup of httpd.conf file
  • Add following two lines
LoadModule was_app22_module /opt/IBM/WebSphere/Plugins/bin/64bits/
WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/WebServer-1/plugin-cfg.xml

Tip: if you are not sure the file location of then you can use find command.

  • Restart HTTP server

This concludes you have successfully integrated IBM HTTP Server with IBM WebSphere Application Server.

Note: In order to have context root accessible through a web server, you must select Web Server as the target during deployment.

Whenever you add new application or changes in context root, you must generate and propagate plug-in.

So that was all for today. Hope you like this.

  • Chandan Kumar
    As the founder of Geekflare, I’ve helped millions to excel in the digital realm. Passionate about technology, I’m on a mission to explore the world and amplify growth for professionals and businesses alike.
Thanks to our Sponsors
More great readings on WebSphere
Power Your Business
Some of the tools and services to help your business grow.
  • Invicti uses the Proof-Based Scanning™ to automatically verify the identified vulnerabilities and generate actionable results within just hours.
    Try Invicti
  • Web scraping, residential proxy, proxy manager, web unlocker, search engine crawler, and all you need to collect web data.
    Try Brightdata
  • is an all-in-one work OS to help you manage projects, tasks, work, sales, CRM, operations, workflows, and more.
    Try Monday
  • Intruder is an online vulnerability scanner that finds cyber security weaknesses in your infrastructure, to avoid costly data breaches.
    Try Intruder