Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Migration from dev to QA to Prod

  Date: Sep 03    Category: MOSS    Views: 1915

I am currently working on making changes to a intranet website in MOSS 2007
using sharepoint designer. The development work is nearly done including new
webparts, columns and workflows.My question is how do I transfer this website
including the new webparts, workflows etc.to the qa and prod environment ( a qa
and prod site already exists) keeping the workflows and webparts intact. Being
new to sharepoint I have never done this before. From what I have read a .wsp
solution package needs to be created to transfer to different environments. How
do I go about creating this solution package and what are the things to keep in
mind especially in regard to workflow's and web-parts.(if there are any links or
articles that can help, would appreciate it).if the question is too general and
certain specifics of the environment are required would be happy to post them.

Share: 

 

6 Answers Found

 
Answer #1    Answered On: Sep 03    

Things created using SharePoint designer are stored in the content database
and so other than a very specific case of a Read Only publishing site they
just aren't built to be transferred from Dev to Test to Production.
SharePoint Designer was created to be a tool used by business users in a
production environment to manage and customize a SharePoint site.
Developers sometimes use it to to create things like master pages,
publishing layout pages, and other things that can be exported from a
content database and re-packaged using Visual Studio for import into a
production system. But most of the items you are talking about can't be
handled that way.

Yes, there are workarounds and hacks that make some of what you want to do
possible, but its just not the way SharePoint is designed to work. You
would have been much better off to research and plan the deployment before
jumping into making changes. A lot of the work you've done is not going to
be transportable.

 
Answer #2    Answered On: Sep 03    

If this is an ongoing need, then you may want to look into some third party
tools - AvePoint, Metalogix, Metavis, Quest, and a number of others. They range
in price, with many charging based on how much data needs to be migrated. Others
charge based on server licenses. Several of the tools can move structural things
like web parts and workflows, lists, etc., while not moving the actual content.

 
Answer #3    Answered On: Sep 03    

Would a Backup and Restore between FARMS do what you want? Also, there are third
party tools that handle deployment of solutions etc such as DocAve from
AvePoint. We are currently using their tools for this very purpose. I imagine
there are others as well.

 
Answer #4    Answered On: Sep 03    

This is not out-of-the-box behavior, as pointed out. However, you can move your
dev work to other systems if you use a 3rd party tool, such as those that
AvePoint, Metalogix and others offer. Migration products allow you to select
lists or whole sites etc. to move to another server.
You need to check the feature sets as not all migration products allow you to
move workflows.

 
Answer #5    Answered On: Sep 03    

You wouldn't be able to just move structure without third-party tools but if all
you want to do is wrap up your site and move it with the content and all then
couldn't you just save the site as a template and build new sites from it?

Also, we built an application that saves a template site with SPD workflows
attached and creates new subsites from that template in code. It's not pretty
but all workflows work correctly:

public void UpdateTemplate(string strURL, string caseTitle)
{
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite mySite = new SPSite(strURL))
{
using (SPWeb myWeb = mySite.OpenWeb())
{
// Delete site template with name STR_ CASESITETEMPLATE
if it exists
SPDocumentLibrary webTemplates;
try
{
webTemplates =
mySite.GetCatalog(SPListTemplateType.WebTemplateCatalog) as SPDocumentLibrary;

SPFolder folder = myWeb.Folders["_catalogs"];
SPFolder subfolder = folder.SubFolders["wt"];
subfolder.Files.Delete(STR_ CASESITETEMPLATE);
subfolder.Update(); //not sure if all of these
folder.Update(); //Update() method calls are needed
webTemplates.Update(); //but this works (O;
}
catch (Exception ex)
{
Exception_Handler.LogEHException(ex,
properties);
}

SPWeb mytemplateWeb = mySite.OpenWeb("template");
mytemplateWeb.SaveAsTemplate(STR_CASESITETEMPLATE,
"Case Site Template",
"Saved via code on " +
DateTime.Now.ToShortDateString() + ".", true);

SPWebCollection webCollection = myWeb.Webs;
myWeb.AllowUnsafeUpdates = true;
SPWeb newWeb = webCollection.Add(caseTitle, caseTitle,
string.Empty,
1033, STR_ CASESITETEMPLATE, false, false);
}
}
});
}

 
Answer #6    Answered On: Sep 03    

We are looks at Xavior and the biggest one Davinci by Axcelar who makes
ControlPoint and other SP tools.

 
Didn't find what you were looking for? Find more on Migration from dev to QA to Prod Or get search suggestion and latest updates.




Tagged: