Free Server Name WebPart Which WFE Is Servicing a SharePoint Request
This is probably the most nominal WebPart I have ever seen / written but I really needed it this morning. As you can guess it just uses a ServerVariables object (off the current context request) to expose the relevant environment variables, in this case just the server name.
The reason this came about was in large SharePoint farms it is notably important when doing certain types of architecture troubleshooting to know which WFE you are hitting. And….well…that’s really it. At least you don’t have to put the WSP together I guess.
So this is what that WebPart does. Just install the WSP and deploy it in Central Admin (as noted in previous posts, I never automate the deployment step).
The WebPart is Feature activated. In the site collection features, locate the Server Name WebPart feature and activate it.
Once activated, you will find the WebPart under the ARB Security Solutions header in the WebPart gallery.
Add it to the page, and it will display the server name in the SharePoint farm responding.
EDIT:
Well I guess I should actually give a download link :)
DOWNLOAD THE SERVER NAME WEBPART INSTALL PACKAGE
6 Comments
Trackbacks/Pingbacks
- Links (10/15/2009) « Steve Pietrek – Everything SharePoint - [...] Free Server Name WebPart – Which WFE Is Servicing a SharePoint Request [...]
- Czech Information Worker Community » Free Server Name WebPart - [...] more info & download: Free Server Name WebPart – Which WFE Is Servicing a SharePoint Request [...]
Leave a Reply
Articles & Research
-
SharePoint Security -
SharePoint Development -
SharePoint Architecture -
Claims Authentication -
Forefront For SharePoint -
AIS / Dynamics GP -
Team Foundation Server -
Pex And Moles -
ISA/TMG/IAG/UAG -
DPM -
Cardspace -
Research Methodology -
Rural ICT Development -
Numerical Analysis -
Multi-Level Research -
Knowledge Management -
Personal/Off-Topic
Latests SharePoint Development Posts
- SharePoint 2013 High Availability And Business Continuity
- Designing Global (WAN) SharePoint 2013 Environments Part 2
- Designing Global (WAN) SharePoint 2013 Environments Part 1
- Using Information Policies In SharePoint 2013
- Information Policy Management In SharePoint 2013
- Co-authoring In SharePoint 2013
Latests SharePoint Security Posts
- Security In Business Connectivity Services In SharePoint 2013
- Planning Security When Migrating To SharePoint
- User Profile Database Architecture In SharePoint 2013
- Why Use User Profiles In SharePoint 2013
- SharePoint 2013 Planning User Profile Synchronization With Directory Services (AD DS,Novell, SJSDS)
- SharePoint 2013 User Profile Property Mapping And Synchronizing Groups
Hi,
I think you should be able to realize this without any dev using a DataViewWebPart to display the SERVER_NAME IIS variable (see http://blogs.msdn.com/joshuag/archive/2008/06/03/getting-the-current-user-name-or-id-in-sharepoint-using-sharepoint-designer-no-code.aspx and http://msdn.microsoft.com/en-us/library/ms524602.aspx).
True, it wouldn’t be as portable.
Joe
Portability being important, however a DVWP approach will unghost the page as well, arguably more important.
Well you can easily create a DVWP without unghosting the specific page it will sit on.
Juste create a “test/dev” page, thn create your DVWP on this page. Then Export/Import the web part on another page. And, bing, you have got it, a DVWP on a ghosted page.
Don’t you find that much more cumbersome than deploying a Feature controlled WebPart with no gallery hooks?
It is not giving the WFE Name but the HostHeader, so this is useless.
another no code simple solution is to add an image to layouts/images directory in each front end. Then change the image in each wfe to reflect name do WFE say WFE1 and WFE2
Now in any pages, insert a link to _layouts/images/
One issue, you need to refresh the page to get the latest image from server not from cash.