If you are lost while finding all the REST requests made from a store page ( like product page, category page or home page ) and looking for a simple tool to debug the performance issues on WCS Store front, then this post is for you.
In just 3 steps, you will be able to identify all the REST requests made from a store page right in the store itself by looking at the store page. No more enabling trace / debugging through trace files / going through JSP code. The store page while displaying the details, will also display all the REST API calls, along with parameters passed to those REST calls and the time taken by each REST request and the JSP from where this REST request is made.
Download the patch that matches your WCS version and follow the steps outlined in Instructions.txt
Once you have deployed the code, you should be able to see the results on the store front in Footer like below:
JSP == /AuroraStorefrontAssetStore/Widgets/Header/Header.jsp variableName = categoryHierarchy URL = http://localhost:80/search/resources/store/10201/categoryview/@top Total Time elapsed = 16 millSeconds
Paramters {catalogId=[10052], responseFormat=[json], langId=[-1], contractId=[10005], depthAndLimit=[11,11]}
JSP == /AuroraStorefrontAssetStore/Widgets/Header/Header.jsp variableName = categoryHierarchy URL = http://localhost:80/search/resources/store/10201/categoryview/@top Total Time elapsed = 16 millSeconds
Paramters {catalogId=[10052], responseFormat=[json], langId=[-1], contractId=[10005], depthAndLimit=[11,11]}
JSP == /Widgets_701/com.ibm.commerce.store.widgets.ContentRecommendation/ContentRecommendation.jsp variableName = queryRemoteWidgetsConfigResult URL = store/{storeId}/configuration/{uniqueId} Total Time elapsed = 1 millSeconds
Paramters {}
JSP == /Widgets_701/com.ibm.commerce.store.widgets.ContentRecommendation/ContentRecommendation.jsp variableName = queryRemoteWidgetsConfigResult URL = store/{storeId}/configuration/{uniqueId} Total Time elapsed = 1 millSeconds
Paramters {}
Special Thanks to Siddharth for helping with this idea.
In just 3 steps, you will be able to identify all the REST requests made from a store page right in the store itself by looking at the store page. No more enabling trace / debugging through trace files / going through JSP code. The store page while displaying the details, will also display all the REST API calls, along with parameters passed to those REST calls and the time taken by each REST request and the JSP from where this REST request is made.
Download the patch that matches your WCS version and follow the steps outlined in Instructions.txt
Once you have deployed the code, you should be able to see the results on the store front in Footer like below:
JSP == /AuroraStorefrontAssetStore/Widgets/Header/Header.jsp variableName = categoryHierarchy URL = http://localhost:80/search/resources/store/10201/categoryview/@top Total Time elapsed = 16 millSeconds
Paramters {catalogId=[10052], responseFormat=[json], langId=[-1], contractId=[10005], depthAndLimit=[11,11]}
JSP == /AuroraStorefrontAssetStore/Widgets/Header/Header.jsp variableName = categoryHierarchy URL = http://localhost:80/search/resources/store/10201/categoryview/@top Total Time elapsed = 16 millSeconds
Paramters {catalogId=[10052], responseFormat=[json], langId=[-1], contractId=[10005], depthAndLimit=[11,11]}
JSP == /Widgets_701/com.ibm.commerce.store.widgets.ContentRecommendation/ContentRecommendation.jsp variableName = queryRemoteWidgetsConfigResult URL = store/{storeId}/configuration/{uniqueId} Total Time elapsed = 1 millSeconds
Paramters {}
JSP == /Widgets_701/com.ibm.commerce.store.widgets.ContentRecommendation/ContentRecommendation.jsp variableName = queryRemoteWidgetsConfigResult URL = store/{storeId}/configuration/{uniqueId} Total Time elapsed = 1 millSeconds
Paramters {}
Special Thanks to Siddharth for helping with this idea.