To backup a SharePoint site there are a few methods, but what I found works the best for us is to use the stsadm.exe backup command. The stsadm.exe can found within the 12 hives directory within the bin folder.
- Run > cmd (depending on your configuration you might have to run the cmd prompt as a local admin)
- cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
- stsadm -o backup -url http://mysite.com -filename C:\temp\mysitefile -overwrite
- You are DONE!
To restore a site backup on another server:
- Login to Central Admin
- Create a new web application under the "Application Management" tab
- Once the site has been successfully created, there is no need to create a site collection because we are going to load it from the backup file
- Run > cmd > cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
- stsadm -o restore -url http://mynewsite.com -filename E:\temp\mysitefile -overwrite
- Once the restore has complete head back into the Central Admin > Application Management tab and choose "Policy for Web Application" and add a user account to login to the new restored website.
Here's one of those things I do just infrequently enough to forget a step. Now I just need to remember that I've put all the steps here.
- Provision a database. It does not need to be new, but it cannot already have the ASP.net membership provider tables in it. If it does, skip ahead to step 3.
- Use the aspnet_regsql.exe tool to create the necessary tables and stored procedures in the database. The tool can be found at <system drive letter>:\Windows\Microsoft.NET\Framework\v2.0.50727. The tool has a GUI wizard that will lead you through the steps.
- Create a web site. A local web site works fine.
-
Add the connection string to your database to the web.config file. Connection strings are placed just inside the configuration root:
<configuration>
<connectionStrings>
<add name="SqlMembershipConnection"
connectionString="Data Source=IPADDRESS;Initial Catalog=DBNAMEHERE;User
ID=DBUSERNAMEHERE;Password=PASSWORDHERE" />
</connectionStrings>
<configuration>
-
Add the SqlMembershipProvider to the web.config file under the system.web node:
<membership>
<providers>
<clear/>
<add name="AspNetSqlMembershipProvider"
type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="SqlMembershipConnection"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="false"
requiresUniqueEmail="true"
passwordFormat="Hashed"
maxInvalidPasswordAttempts="5"
minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="1"
passwordAttemptWindow="10"
passwordStrengthRegularExpression=""
applicationName="NAMEOFAPPHERE"/>
</providers>
</membership>
NOTE: The connectionStringName parameter of the membership provider must match the name you chose for the connection string above. The applicationName parameter allows you to use the same database for different web applications. Choose a suitable name and set the other parameters as needed.
- Add a CreateUserWizard control to the default.aspx page of your web site.
- Right click on the default.aspx page and choose "View In Browser" from the context menu.
- You know the rest...
Introduction
Windows SharePoint Services 3.0 (WSS) is Microsoft’s fastest and largest growing server application. As a development environment, WSS has been defined as an ecosystem that operates by enabling development partners the ability to build and design new methods of enhancing the features and establishing third party integrations all into one solid and secure environment.
By adopting the SharePoint environment, applications will continue to benefit from the technology enhancements and new features that are supported by Microsoft or any Microsoft partnered organization.
Setting up a WSS Application
- Central Administration
- This is the source for all high level administration for the set up and maintenance of WSS applications and other important functions including site backup and restore
- Application Management
- Operations
Create New Web Application
- Authentication Provider
- Kerberos
- The most secure server authentication support by Active Directory
- Require a lot more configuration and is much more complicated to setup
- NTLM (NT LAN Manager)
- Easy to set up, virtually no configuration required
- Secure, but not as secure as Kerberos
The difference is… When using Kerberos, any server component that the user invokes enjoys full network access
- Setup the content database
- WSS ships with a version of SQL Server Embedded Edition (SSEE). Therefore, no SQL Server license is required
- You can create the content database with an external data catalog, but you need to choose collation LATIN1_General_CI_AS_KS_WS
- Select a template
- Set a quota
- Create a site collection and reset iis
WSS Application Out-of-the-box
Depending on the type of site template being used, features will be available right away
- Announcements
- Calendar
- Document Library
- Workflows
- Content Versioning
- Many more… www.codeplex.com has a bunch of downloads and add-ons for templates as well
Site Actions
- Site Settings
- Zone for site collection configuration
- Main activities
- People and Groups
- Site Theme
- Web Parts
- Create
- Create new pages or add features to the current page
- Libraries, Communications, Tracking, Custom Lists, Web Pages
Customize Web Applications
- Customization Tools
- SharePoint Designer
- Customize pages and modify masterpages
- Visual Studio 2005, 2008
- Build customized Web Parts
- STSDEV
- Utility designed to quickly transform your ideas into real-world components that you can deploy into a staging or production Web. http://www.codeplex.com/stsdev
Preferred Development Environment
Unfortunately, to take advantage of the dev tools available such as STSDEV, it is required to run development on the WSS machine.
Debugging is available but configuration is necessary.
- Start Remote Debugging
- Attach to Process (ctrl + p)
So you have decided to entertain the concept of developing a published CMS (Content Management Systems) website built on the SharePoint technology, and perhaps you are unsure of any pros and cons with the technology or need a good solid place to begin research. If you are just starting with the SharePoint development you do have a long road to travel and the road can very rough at based on a direction that has been chosen. I have been primarily developing in SharePoint for 2 years now and have fought hard for the toolbox library of custom web parts that I have today, but with every step forward more opportunity and understanding of the true power of SharePoint framework, especially using the framework for customized or template CMS websites.
I was at the 2009 SharePoint Summit in Montreal and had the amazing opportunity to listing to Mike Fitzmaurice – Nintex, present a talk on "The Evolving Market around SharePoint Products and Technologies". Within first slide, he had made a statement that completely summed up the SharePoint framework for me and really started to make me think about using the product differently and to that effect, appropriately. The statement was very simple and stated that "SharePoint is an Ecosystem". This statement turned me around because instead of thinking "what is SharePoint going to do for me?" I started thinking "How can I start developing my own ecosystem on top of the SharePoint engine?" And that leaves me where I am today. I have now been building various websites within SharePoint and have a collection of valuable customized web parts that I can deploy and reuse and SharePoint site. Throughout the course of this development blog I will be releasing concepts that represent different tools in our web part library to help make any readers understand the approach and begin using these tools within their development.
Beginning a SharePoint site of any size takes a large amount of understand of the SharePoint hierarchy of sites, sub-sites, content types, folders and list items. Understanding to appropriate approach with this hierarchy and assigning the appropriate relations and metadata, your development cycle will benefit completely. Take the time to plan and understand the requirements in relation to the SharePoint core functionality.
There are a lot of really good articles and blog postings out and from time to time I intend to share links to related topics that helped improve our understanding when developing parts for SharePoint. Being as this is the initial blog post, I will quickly share our recent links to help any up and coming SharePoint developers get started. ENJOY!!
Kyle Pearn,
Akira Systems |
|
|
|