How to avoid having to restart Yellowfin after backend modifications to the Yellowfin database.

Hello to all our readers, 

as many of you will know, officially we do not support making backend modifications to the Yellowfin configuration database.

However, in spite of this warning, many people from different walks of life, from all over the world still perform this unsupported act!

If you are one of those people and have been looking for a way to avoid having to restart Yellowfin after having performed a backend manipulation of your repository then there is a way...in fact there are a few different ways.

Firstly, there are 3 web services that you should know about. They are documented in this Wiki article on Cache Management:

1) If you have modified values in the Configuration table then you will need the RELOADCODES service

2) If you have modified values in the View cache then you will need the service called REMOVEVIEW

3) If you have modified values that are stored in the Report cache then you will need the service called FLUSHREPORT

As well as that, if you don't want to use any web services then you can run the attached JSP called info_cache_enhanced.jsp (just place it in your ROOT folder) and click the Clear button under the particular cache you want to clear.

The OrgCache does not feature in the selection of caches in the afore-mentioned info_cache_enhanced.jsp, and that is the cache that needs to be refreshed if you have modified your Configuration table, so there is another jsp attached here called "Refresh_Caches.jsp" which will do precisely that job for you.

I hope some of you will find this information useful, and please remember....we do not support backend modifications to the repository!

regards,

The Support Team

Is article helpful?