Fraska Portal

Exploring the WebSphere Commerce world

WebSphere Commerce, FEP7, Toolkit, Deploy SOLR Admin UI

Posted by on in Administration
  • Font size: Larger Smaller
  • Hits: 5314
  • 44 Comments
  • Subscribe to this entry
  • Print

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:

WCS_SOLR_UI.png

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.


Target:

System Administrators

Environment:

  • WebSphere Commerce Developer v 7.0.0.8 FEP7
  • WebSphere Application Server 7.0.0.29
  • 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 solr-4.3.0.zip

3) Open WebSphere Commerce Developer

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

  • css
  • img
  • js
  • tpl
  • admin.html
  • favicon.ico

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.

 <web-ext
   xmlns="http://websphere.ibm.com/xml/ns/javaee"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://websphere.ibm.com/xml/ns/javaee http://websphere.ibm.com/xml/ns/javaee/ibm-web-ext_1_0.xsd"
   version="1.0">
   ...
   <enable-file-serving value="true"/>
   ...
</web-ext> 

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

<servlet-mapping>
     <servlet-name>SolrSearchServlet</servlet-name>
      <url-pattern>/Search-Solr</url-pattern>
</servlet-mapping>

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:

http://localhost/solr

 

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">
 	<web>
		<web-uri>Search-Solr.war</web-uri>
		<context-root>/solr</context-root>
	</web>
 </module> 

 

Rate this blog entry:
0

Comments

Leave your comment

Guest
Guest Wednesday, 17 October 2018

Most Popular Post

WebSphere Commerce, the SOLR extension index
Administration
Rate this blog entry:
4
WebSphere Commerce, Data Load and SOLR Delta Index
Data Load
Rate this blog entry:
0
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5

Latest Blogs

WebSphere Commerce, CommandLevelAuthorizationCache
Cache
Rate this blog entry:
0
WebSphere Commerce v8, toolkit exception, ClassNotFound db2
Administration
Rate this blog entry:
1
WebSphere Commerce, ATP migration
Store
Rate this blog entry:
0
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5
WebSphere Commerce, Performance analysis of few European stores
Performance
Rate this blog entry:
0