April 24th 2008 meeting

http://www.azsharepointpros.comhttp://www.azsharepointpros.com

Arizona SharePoint Professionals Group


Community News 5 for 5 Tips and Tricks SharePoint Taxonomy Planning and

Governance (Presented by Mark Schneider Vice President, Barricuda Tools)

Speed Demoing – MOSS and Silverlight (Presented by Doug Perkes of Microsoft)

Raffle


Mindsharp will be drawing off a $2995 voucher good Mindsharp will be drawing off a $2995 voucher good for any public Mindsharp training event (including for any public Mindsharp training event (including the June training events) – Complete your surveys the June training events) – Complete your surveys to be entered!!!to be entered!!!

Mindsharp will be providing free Demo DVD’s Mindsharp will be providing free Demo DVD’s containing our End User Computer Based Training containing our End User Computer Based Training solution for WSS 3.0 and MOSS 2007. solution for WSS 3.0 and MOSS 2007.


Joel’s 10 Steps to Governance Deck External Collaboration Toolkit for SharePoint Hotfix for Lotus Notes Protocol Handler

(KB950280) Mindsharp is holding a public SharePoint

training event in Phoenix on June 16th – 20th offering the following classes: 5-day 2007 SharePoint Designer 5-day WSS 3.0 Developer 3-day 2007 SharePoint Power User

TechEd (6-10-08) Next AZSPG - 5-29-08


Search, Search, Search, Search, SearchSearch Federating search with other engines

What is a search connector and what do I do with it!

Using Facets and Why Addressing Governance and the

Manageability of Search


SymptomSymptom You write custom code that eventually causes your You write custom code that eventually causes your

environment to become unstable or unresponsive.environment to become unstable or unresponsive. Potential FixPotential Fix: Validate Your Object Dispose : Validate Your Object Dispose

UsageUsage Review Roger Lamb’s Developer Blog and and

Jeremy Jameson’s Musings Long term: Look for new code analysis tools Long term: Look for new code analysis tools

coming in the future to identify these issues.coming in the future to identify these issues.


Situation: The search crawl Situation: The search crawl has failed for some reason has failed for some reason and the ULS logs do not and the ULS logs do not contain much information contain much information regarding the crawl. All the regarding the crawl. All the search categories in search categories in diagnostic logging are diagnostic logging are turned up to verbose yet turned up to verbose yet crawl information is crawl information is limited. What can you do?limited. What can you do?

Fix: Turn up the Fix: Turn up the hidden hidden diagnostics categories diagnostics categories related to the gatherer. related to the gatherer. This can be done using This can be done using STSADMSTSADM

stsadm -o setlogginglevel -category GatherBackup -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherDestruction -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherDirMon -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherDirMonQ -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GathererLink -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GathererSql -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherHistoryHash -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherPI -tracelevel verbose -windowslogginglevel information stsadm -o setlogginglevel -category GatherPITrx -tracelevel verbose -windowslogginglevel information


Alert templates are defined in 12\Template\xml\Alert templates are defined in 12\Template\xml\alerttemplates.xml. They are stored in the config DB alerttemplates.xml. They are stored in the config DB and are available at the web application level. Any and are available at the web application level. Any changes to AlertTemplates.xml must be followed by the changes to AlertTemplates.xml must be followed by the following stsadm command for the changes to take following stsadm command for the changes to take effect -effect -

stsadm -o updatealerttemplates -filename <templates stsadm -o updatealerttemplates -filename <templates file name> -url <site> file name> -url <site>

With the alert template you can - With the alert template you can - Customize the alert emailCustomize the alert email w/ CAML w/ CAML Customize the New Alert pageCustomize the New Alert page Specify custom Specify custom Alert handlerAlert handler

An alert template is what connects a subscription to An alert template is what connects a subscription to the formatting of the email, notification/update the formatting of the email, notification/update handlers if any, filters, etc. Each alert has an alert handlers if any, filters, etc. Each alert has an alert template specified in the AlertTemplateName property template specified in the AlertTemplateName property (AlertTemplate property for full xml) of the SPAlert (AlertTemplate property for full xml) of the SPAlert object. The OOB alert templates are in \Template\XML\object. The OOB alert templates are in \Template\XML\AlertTemplates.xmlAlertTemplates.xml

NOTE: Do not modify the OOB alert templates NOTE: Do not modify the OOB alert templates

file. You can copy the contents to another file file. You can copy the contents to another file and use the update alert templates command. and use the update alert templates command.

Following OOB alert templates are provided: SPAlertTemplateType.GenericList : Template for alerts on Generic lists SPAlertTemplateType.DocumentLibrary : for Document librariesSPAlertTemplateType.Survey SPAlertTemplateType.LinksSPAlertTemplateType.AnnouncementsSPAlertTemplateType.ContactsSPAlertTemplateType.EventsSPAlertTemplateType.TasksSPAlertTemplateType.DiscussionBoardSPAlertTemplateType.PictureLibrarySPAlertTemplateType.XMLFormSPAlertTemplateType.DataConnectionLibrarySPAlertTemplateType.AssignedtoNotification : Assigned to Task/Issuelist notifications


The <Formal> </Format> section of an The <Formal> </Format> section of an <AlertTemplate> in <AlertTemplate> in Alert TemplatesAlert Templates can can be used to modify the look of the email be used to modify the look of the email - -

In addition to these, CAML is supported. In addition to these, CAML is supported. For. e.g you can specify <GetVar For. e.g you can specify <GetVar Name="NewValue#{Field}"> inside the Name="NewValue#{Field}"> inside the <Fields> section. More examples can <Fields> section. More examples can be seen in AlertTemplates.xml.be seen in AlertTemplates.xml.

To exclude some fields from being To exclude some fields from being rendered in the email, you should rendered in the email, you should include them in the include them in the <DigestNotificationExcludedFields> and <DigestNotificationExcludedFields> and <ImmediateNotificationExcludedFields><ImmediateNotificationExcludedFields> section. section.

Xml tags - <Digest> - look of the digest email<Header><HeaderFieldsHeader><HeaderFields><HeaderFieldsFooter><RowHeader><RowFields><RowFooter><Footer> <Immediate> - look of immediate subscription<Subject><Header><Fields><Footer>


Explore the TEMPLATE folder Explore the TEMPLATE folder in the SharePoint 12 Hive. in the SharePoint 12 Hive. Pay particular attention to the Pay particular attention to the files in CONTROLTEMPLATES, files in CONTROLTEMPLATES, LAYOUTS, and XML LAYOUTS, and XML directories.directories.

Use Lutz Roeder’s reflector Use Lutz Roeder’s reflector ((http://www.aisto.com/roeder/http://www.aisto.com/roeder/dotnet/dotnet/). You can get a wealth ). You can get a wealth of information be examining of information be examining the source code of the the source code of the SharePoint assemblies. SharePoint assemblies. Example:Example:

If you ever want to find out “How did they do that?” when If you ever want to find out “How did they do that?” when looking at an out-of-the-box SharePoint control or field use looking at an out-of-the-box SharePoint control or field use these tips to find out how the Microsoft team did itthese tips to find out how the Microsoft team did it


Learn why your organization’s taxonomy will make or break your Learn why your organization’s taxonomy will make or break your SharePoint deployment, how to tell a good taxonomy from a bad one, SharePoint deployment, how to tell a good taxonomy from a bad one, and why SharePoint requires collaborative governance in order to be and why SharePoint requires collaborative governance in order to be successful.successful.

Mark is a contributing author an upcoming Microsoft Press book on Mark is a contributing author an upcoming Microsoft Press book on SharePoint Governance and Best Practices. Mark provided technology SharePoint Governance and Best Practices. Mark provided technology leadership and planning for over 25 years to organizations big and leadership and planning for over 25 years to organizations big and small. He focuses on bridging the strategic planning gap between small. He focuses on bridging the strategic planning gap between business and technology stakeholders. His passion is in developing the business and technology stakeholders. His passion is in developing the skills and capabilities of others, and toward that end he teaches skills and capabilities of others, and toward that end he teaches workshops on strategic technology planning, taxonomy planning, workshops on strategic technology planning, taxonomy planning, technology governance, and project management. He is currently technology governance, and project management. He is currently serving as Vice President of Barracuda Tools, a developer and publisher serving as Vice President of Barracuda Tools, a developer and publisher of enterprise software tools. Mark can be reached at of enterprise software tools. Mark can be reached at [email protected]@vitalskill.com, and his blog site , and his blog site www.sharepointplan.comwww.sharepointplan.com..

April 24th 2008 meeting

Documents

Transcript of April 24th 2008 meeting