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.

 Working with the Aurora starter store- provided with the FEP7- could bring some misconfiguration, in particular on the Developer version, lead to "break" the front-end, like in this case:

The above screenshot reports just the top part of the front page were is visible an issue rendering the menu. Looking at the log, an exception gets a glimpse on the possible reason:

 
[5/7/14 16:47:12:451 CEST] 00000148 LoggingHelper E /GenericJSPPageError.jsp - java.io.FileNotFoundException: http://myserverhostname:80/search/resources/store/11451/categoryview/@top?catalogId=10401&depthAndLimit=11%2C11&responseFormat=json&responseFormat=json&langId=-1
                                 java.lang.RuntimeException: java.io.FileNotFoundException: http://myserverhostname:80/search/resources/store/11451/categoryview/@top?catalogId=10401&depthAndLimit=11%2C11&responseFormat=json&responseFormat=json&langId=-1
	at com.ibm.commerce.foundation.internal.client.util.RESTHandler.execute(RESTHandler.java:122)
	...
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1656)
Caused by: java.io.FileNotFoundException: http://myserverhostname:80/search/resources/store/11451/categoryview/@top?catalogId=10401&depthAndLimit=11%2C11&responseFormat=json&responseFormat=json&langId=-1
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	...com.ibm.commerce.foundation.internal.client.util.RESTUtil.getWithMultiValuedParams(RESTUtil.java:172)
	at com.ibm.commerce.foundation.internal.client.util.RESTHandler.execute(RESTHandler.java:116)
	... 103 more
Caused by: java.io.FileNotFoundException: http://myserverhostname:80/search/resources/store/11451/categoryview/@top?catalogId=10401&depthAndLimit=11%2C11&responseFormat=json&responseFormat=json&langId=-1
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1457)
	at com.ibm.commerce.foundation.internal.client.util.RESTUtil.getWithMultiValuedParams(RESTUtil.java:136)
	... 104 more

Once the FEP7 installation is done and the starter store is published with some example data, the next step is the SOLR index configuration (setupSearchIndex), pre-process (di-preprocess) and build (di-buildindex).

However, during the pre-process step I faced an interesting exception. In fact, running the following command

di-preprocess.bat <WC_installfolder>\search\pre-processConfig\MC_<catalogId>\DB2

the process ended with the exception:

SEVERE: Exception message: CWFDIH0001: Data Import encountered a generic error. The error is null. , stack trace: com.ibm.commerce.foundation.dataimport.exception.DataImportSystemException: CWFDIH0001: Data Import encountered a generic error. The error is null. 
	at com.ibm.commerce.foundation.dataimport.preprocess.DataImportPreProcessorMain.processDataConfig(DataImportPreProcessorMain.java:957)
	at com.ibm.commerce.foundation.dataimport.preprocess.DataImportPreProcessorMain.execute(DataImportPreProcessorMain.java:802)
	at com.ibm.commerce.foundation.dataimport.preprocess.DataImportPreProcessorMain.main(DataImportPreProcessorMain.java:289)
Caused by: java.lang.NullPointerException
	at com.ibm.commerce.foundation.dataimport.preprocess.StaticAttributeDataPreProcessor.process(StaticAttributeDataPreProcessor.java:299)
	at com.ibm.commerce.foundation.dataimport.preprocess.DataImportPreProcessorMain.processDataConfig(DataImportPreProcessorMain.java:919)
	... 2 more

Once the FEP7 is installed and new new Aurora is published you could face validation errors in the JSP of the store.

I collected few examples and reported a possible way to fix them.