Friday 18 December 2009

MOSS 2007: Jaspers Best Practices

This is a recurring post where I will try to mind-map my ideas about best practices for MOSS 2007. I will update this post every time I think about 'rules' that I find best practice. (Can call that frequently, right? ;-)

Installation

  • Install your Web applications to the WWWRoot. This helps everyone who's searching your Web application root folder.
  • When creating a Web application and requirements don't specify a port number to use, use port number 80 and up for custom Web applications. This helps you to remember the port number and recognizing which Web application your working with according to the URL.
  • When creating a Web application and requirements don't specify a port number to use, use port number 8080 and up for the Central Administration (CA) , the Shared Service Provider (SSP), My Site sitecollection and other MOSS dependent Web applications. This helps you to remember the port number and recognizing which Web application your working with according to the URL.
  • Name your application(pool, etc) after the function or projectname of your Web Application. For example: SharePoint - CA - 8080 instead of SharePoint - 8080. This helps you to recognize the application(pool) in ISS, CA, etc.
  • Name your database (DB) after the function or projectname of your Web Application. For example: WSS_Content_Library instead of WSS_Content_xxxxxxxxxxxxxxxxxxxxxxxxx9f7e04a. This helps you and DB managers to recognize the DB.

Server installation

  • Install 7-zip. It supports more file types and it's free, so no anoying pop-ups!

Development (tools)

  • Use the VSE WSS to easily create SharePoint Projects etc.
  • Use custom Definitions if possible, this makes it easier to reproduce your Sites/Pages/Lists/Contenttypes/etc.
  • Use SPM2007 to easily retrieve contenttype (etc.) GUIDs and brutaly change the Moss structures.
  • Use StsadmWin 2007 to create stsadm commands in a GUI-friendly-matter.
  • Use WSPBuilder to build your wsp's.
  • Use SharePoint Solution Installer to send to customers. It guides them installing your wsp's.

Content Deployment

  • Read 'Content Deployment – The complete' from Stefan Goßner, because it covers a lot of topics about the Content Deployment abilities of SharePoint like configuration, common misunderstandings and issues.

Users
... planned