Forum Discussion
Dev_56330
Cirrus
CirrusSharePoint and WebAcceleration
I have recently configured a SharePoint application service using the latest SharePoint iApp (running Big-IP 11.4 HF 3). The default configuration for Web Acceleration creates a profile using optimi...
The WAM application stats are really the only thing to look at other than the header. It looks like some of the responses are being cached.
The X-WA-Info header should show you where the content was served from and what node of the acceleration policy it matched. There are explananations on page 77 of this guide:
https://support.f5.com/content/kb/en-us/products/wa/manuals/product/wa_implementations_11_0_0/_jcr_content/pdfAttach/download/file.res/wa_implementations_11_%20%20%20%20%20%20%20%20%20%20%200_0.pdf
If you open the acceleration policy in BIG-IP GUI, and hover over the individual leaf names in the policy tree, it will display a 5 digit number. That number corresponds to the node ID in the X-WA-Info header.
Hi Lyonsson, first off, which version of the iApp template are you using? The most recent is f5.microsoft_sharepoint_2010_2013.v1.0.0.tmpl.
Next, when you say you are selecting the webacceleration-wam-enabled profile, you mean you are selecting "Yes, use BIG-IP AAM" in response to the "Use the BIG-IP Application Acceleration Manager?" question, then choosing that acceleration profile in response to the "Which Web Acceleration profile do you want to use for caching?" question, correct?
Dev_56330I am using f5.microsoft_sharepoint_2013.v1.1.Orc1. And yes you are correct, I select "Yes, use BIG-IP-AAM (recommended)" and then selecting webacceleration-wam-enabled for the question "Which Web Acceleration profile do you want to use for caching?".- Did you previously create an AAM web application and associate the webacceleration-wam-enabled profile with it before running the iApp? In this case we recommend selecting the "Create a profile based on optimized-acceleration" option, as it will create all the necessary configuration for proper web acceleration.
- Dev_56330Mike, I have reverted to the "Recommended" settings and still see more errors than anything in the web acceleration dashboard. I see some entries in the web cache effectiveness and less entries in the web optimized transactions while nothing in optimized web throughput or web image optimization. How can I troubleshoot the OWS and WAM errors?
- In the iApp, can you select "Insert the debug header" from the "Do you want to insert the X-WA-Info header?" question? If you then inspect the client traffic using Fiddler, HTTPWatch, or IE Developer Tools, you should see a header in the response named X-WA-Info. I recommend visiting a page or pages several times to prime the cache, clearing the browser cache after each page refresh. When you look at the value of the X-WA-Info header, it should tell you which node of the acceleration policy applied to the response and whether or not it was cached. See "Viewing X-WA-Info response headers" here: https://support.f5.com/kb/en-us/products/wa/manuals/product/wa_concepts_11_0_0/wa_httpdata.html1029973
- Dev_56330Thanks for your continued comments. Will the X-WA-Info header provide details on the OWS and WAM errors that show up in the dashboard?
- I'm not sure about the dashboard, but the header will tell you exactly where the content was served from, and why.
- Dev_56330I have modified the iApp to include X-WA-Info though the codes are not straight forward. I have read the article you provided regarding the X-WA-Info headers though they do not go into detail about what the header codes actually mean. Any references that you know of?
- Dev_56330In all honesty, I do not think WA is functioning at all. When looking at the traffic reports, by reports and response reports there is no data. Other than debug headers is there a helpful WA log?
- Dev_56330While going through TMSH below are some of the results I see. Requests 766 Proxied 26.9M From Cache 448.9K OWS Responses Successful 267 Redirection 36 Client-Errors 367 Server-Errors 0 Rejected 5 WAM Responses Successful 273 Redirection 58 Client-Errors 367