Learning Experience MOSS 2007 step by step-Part8

No.of Views790
Bookmarked0 times
Downloads 
Votes0
By  hussain.attiya   On  01 Apr 2010 11:04:07
Tag : SharePoint , Setup, Upgrade, Administration and Operation
Learning Experience MOSS 2007 step by step-Part8
emailbookmarkadd commentsprint

Images in this article missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at info@codegain.com

 

Introduction


In this stage, we have completed the entire project. This article - Part 8 - i going to explain in how to copy the SharePoint Website from the Development Server to the Production server.

You can still refer to the previous parts here:

Understand the default sharepoint website templates and choosing the suitable one for our case which is CMS - My Learning Experience in MOSS2007 - Part 1
Step-By-Step to Create a SharePoint Publishing Website - My Learning Experience in MOSS2007 - Part 2
Using SharePoint Variation Feature to create multiple languages website - My Learning Experience in MOSS2007 - Part 3
Branding/Customizing A SharePoint 2007 Website - My Learning Experience in MOSS2007 - Part 4
Creating Layout Pages for your SharePoint 2007 website - My Learning Experience in MOSS2007 - Part 5
Using Query Web Part in your website and customizing it - My Learning Experience in MOSS2007 - Part 6
Step-by-Step to Import SharePoint Website 2007 from Staging Server to Production Server - My Learning Experience in MOSS2007 - Part 7


Getting Started
 

Just documenting my experience of copying a SharePoint 2007 website from our development server to the production server. I know there are so many ways to do that. At least we can use the MOSS 2007 Backup/Restore facilities. But here i have used the "STSADM" command because i felt it is easy and straitforward.

  • In the development server I used the “stsadm” command line to export the entire website including the database. The command line is like that:
STSADM.EXE -o export -url http://dev-server:81 -filename "c:\my_website.cmp"

Note: The stsadm is available in this directory “c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\”. So, first change directory (CD) to the above directory.

  • After that I uploaded the “my_website.cmp” file to the production server. where from there i can then import
  • Before I started to import the file I have first done the following in the production server:
    • I have created a website using the central administration website
    • Then I create the site collection (publishing website)
    • I have used the exact database name which is available in the development server.
  • When I finished, I use the command line to import the website:
STSADM.EXE -o import -url http://production_server -filename "c:\my_website.cmp"

When I run the command above I faced the following error:

FatalError: Could not find Feature IPFSSiteFeatures
  • After searching about the problem. I found that I should install that feature by using the following command:
stsadm -o installfeature -name IPFSSiteFeatures

It keeps asking me about the features not found. And I installed whatever asked using the above command. At last the import works fine. It is taking long time.

 

Manual File Copy


The import will not import all the files in the _layout folder. these file you have to copy manual.

I copied the my website images folder "fh_images" to the “c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES\” location.
I copied my .Net Application which is located in the _layouts folder to the “c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\”
I backed up the "web.config" located here : "c:\Inetpub\wwwroot\wss\VirtualDirectories\80\" (Production Server) and copy the one from the development server.
I backed up the "wss_minimaltrust.config" and "wss_mediumtrust.config" in the following location "c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\" (Production Server) and copy the ones from the development server.
Copy the dll files containing my .Net Application Class Library to "c:\Inetpub\wwwroot\wss\VirtualDirectories\80\bin"

 
Sign Up to vote for this article
 
About Author
 
hussain.attiya
Occupation-
Company-
Member Type-Junior
Location-Bahrain
Joined date-29 Oct 2009
Home Page-
Blog Page-
 
 
Other popularSectionarticles
Comments
There is no comments for this articles.
Leave a Reply
Title:
Display Name:
Email:
(not display in page for the security purphase)
Website:
Message:
Please refresh your screen using Ctrl+F5
If you can't read this number refresh your screen
Please input the anti-spam code that you can read in the image.
^ Scroll to Top