The SOLR Admin UI is an interesting tool for monitoring the created cores, reviewing their configuration, querying them, understandng the cache performances, collecting useful troubleshooting information and many other things.

Having this tool in the hands of a System Admin could be really worth it. The UI is the following one:


The WCS InfoCenter describes the steps to follow in order to integrate the admin UI files in the solr-search web app: Info Center, Search performance tuning, Performance monitoring

However, it seems to have a couple of inaccuracies. So, I decided to report my experience deploying the SOLR Admin UI on FEP7 toolkit.


System Administrators


  • WebSphere Commerce Developer v FEP7
  • WebSphere Application Server
  • DB2 9.7
  • SOLR 4.3.0 (local)

Steps followed

1) Download the SOLR version 4.3.0 from SOLR archive, distribution 4.3.0

2) Unzip the download file

3) Open WebSphere Commerce Developer

4) Copy the following directories and files from the unzip folder into the Search-Solr/WebContent project's directory

5) Open the Search-Solr\WebContent\WEB-INF\ibm-web-ext.xml file for editing.

6) Find the enable-file-serving flag and set it to true.

   <enable-file-serving value="true"/>

7) Save your changes and close the file.

8) Open the Search-Solr\WebContent\WEB-INF\web.xml file for editing.

9)  Change the URL pattern for the SolrSearchServlet servlet to /Search-Solr


10) Save your changes and close the files.

11) Publish the search EAR.


Now, you are ready to access the console using the following URL:



Problem faced

Once I re-published the Search EAR the module mappings of the Seach-Solr.war was wrong.

So, I had to update the Search/META-INF/application.xml file using the following value:

 <module id="Module_1404737500743">