Best practices for deployment from Dev /Staging /Production in SharePoint ?

Hi All,
What is a best practices to deploy SharePoint Portal to dev / staging / Production.
I have custom solution deployed using WSP file. But I have done some changes using sharepoint designer.
Like as Designer workflow, master pages etc.
How can I deploy my document libraries and list to dev to prod using best practices?
Thanks
Balaji More

Hi,
According to your post, my understanding is that you wanted to know the best practices to deploy SharePoint Portal in different SharePoint environment.
If the site is not existing in the production server, we can save the site from the development server, and then import it to the production server.
But if the site is already existing in the production server, we should follow these steps to just add the taxonomy and content types to the production server:
Save the site from Dev as a template
Import the template as solution in Visual Studio
Remove unnecessary items from the solution(Please pay more attention on it. If a content type/list... in the solution is existing in the production site too, it will replace the
same object existing in the production after deployment)
Package the solution
Deploy the solution in the production
For more detailed, please see:
http://ahmedmadany.wordpress.com/2012/12/30/importing-sharepoint-solution-package-wsp-into-visual-studio-2010/
There is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/7dcf61a8-1af2-4f83-a04c-ff6c439e8268/best-practices-guide-for-deploying-sharepoint-2010-from-dev-to-test-to-production?forum=sharepointgeneralprevious
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Similar Messages

Change PowerPivot data source when deploying from Dev - Staging - Production

We have PowerPivot workbooks we store in SharePoint 2013 Libraries.
We have a powershell script which automates the deployment of sites and pages. Is there a way using PowerShell (or any scripting language really) to look into the workbook and change the PowerPivot data source when deployment from one environment to
another? (Dev -> Stage -> Prod) We need to update the workbooks to point to our SSAS cubes Dev -> Stage -> Prod respectively.
Thank you for any expert advice you may offer,
Sincerely,
-Craig

Basically, it's an excel file (XLSX) file and you can use excel OM for this.
A simple program (in C# or any language of your choice) can be written to do the following and achieve what you need.
using XLS = Microsoft.Office.Interop.Excel;
string info = null;
XLS.Application application = null;
try
application = new XLS.Application();
var book = application.Workbooks.Open(filepath);
foreach (XLS.WorkbookConnection wc in book.Connections)
  switch (wc.Type)
   case XLS.XlConnectionType.xlConnectionTypeOLEDB:
    info = wc.Name + " " + wc.OLEDBConnection.Connection.ToString() + "\r\n";
    break;
book.Close();
finally
if (application != null)
  application.Quit();
Hopefully, this was helpful.

Best practices for deploying EMGrid Control

Can i use one db for OEM & RMAN repository? Looking for Best practices for deploying EMGrid Control in our environment, I have experience working with EMGrid control it was very slow , how to make it fast ? Like i enjoy the speed of EMDBControl....

DBA2008 wrote:
Is this good idea to put RPM recovery catalog & OID schema in OEM Repository DB? I am thinking just to consolidate all these schema's in one db.Unless you are really starved for resources, I would not recommend storing the OID and OEM repositories in the same database. Both of these repositories support different products, and you risk creating unnecessary dependencies when patching or upgrading. As a completely fictitious example, what if your OID installation has a critical issue that requires a repository database upgrade to version 10.2.0.6, and the Grid Control repository database is only certified for version 10.2.0.5?
Regards,
John P.
http://only4left.jpiwowar.com

Best practice for exporting from iMovie '08 to iDVD

I am looking to find out what is the best practice for exporting from iMovie '08 to iDVD. I have read the other postings that give the basic howto (export to Media Browser then select the video in iDVD). However, my question is a little more technical. I have 1080i HD projects. I am interested in burning them to DVD in the best possible quality. What setting should I be using when I publish to Media Browser?
I am wondering about quality loss due to more than one conversion/compression. I suspect that when I export to the Media Browser then this is occurring. If I am not mistaken iMovie is using something like H.264 for this. Then, when I run iDVD I suspect it will it do another conversion/compression, I think to get to MPEG2. Not only could this result in a loss of quality but also it will take extra time. I am interested to know what others think about this.
Finally, I am looking to create DVDs for a lot of video. I am wondering if there are any USB or firewire hardware devices out there that could speed up the compression. I use the Elgato Turbo.264 when I want to encode to H.264 but I wonder if there is something similar for DVD creation.
Thanks in advance.

the standards for videoDVD are 720x480, and usually mpeg2 encoded..
so, your HiDef project HAS to be 'downsampled' somehow..
I would Export with Qucktime/apple intermediate => which is the 'format' your project is allready, and you avoid any useless 'inbetween encoding'..
iDVD will 'swallow' this huge export file - don't mind: iDVD cares for length, not size.
iDVD will then convert into DVD-standards..
you can 'raise' quality, by using projects <60min - this sets iDVD automatically to highest technical possible bitrate
hint: judge pic quality on a DVDplayer + TV.. not on your computer (DVDs are meant for TVdelivery)

What is best practice for deploying agent(10204) on RAC 9i

Hello,
What would be best practice for deploying agent(10204) on RAC 9i? Should the agent be deployed on each node or should the agent be deployed on the cluster file system? What are the advantages/disavantages deploy on individual nodes vs. on cluster file system? Please advice. Thank you in advance.

Please use agent push application to deploy agent on all the nodes at one shot
Please refer the obe
http://www.oracle.com/technology/obe/obe10gemgc_10203/agentpush/agentpush.htm

Best Practice for Deploying ADF application

I am tasked with developing a best or prefered practice of feploying a large ADF application. Background: we are in the process of redeveloping a UI for a large system. We have broken the system down into susbsytems. Each of these susbsystems UI will be a ADF aaplicaion(?). This is a move from a MS .Net front end. The backend (Batch processes etc) is being dveloped in Java. So my question is if I have several ADF projects for each subsystem and common components that they all will use - what is the best practice to compile package and deploy? The deployment will be to weblogic server or servers(Cluster).
We have a team of at least 40 -50 developers worldwide so we are looking for an automated build and deploy and would like to follow Oracle best practice. So far I have read Deploying ADF Applications (http://download.oracle.com/docs/cd/E15523_01/web.1111/e15470/deploy.htm#BGBJHGFH) and have followed the links. I have also look at the ADF evangalist blogs - lots of chatter about ojdeploy. My concern about ojdeploy is that dependent files are also being compiled at the same time. I expected that we want shared dependent files compiled only once (Is that a valid concern)?
So then when we build the source out of subversion (ojdeploy ? Ant? ) then what is best practice to deploy to a weblogic server (wslt admin console) - again we want it to be automated.
Thank you in advance for replies.
RK

Rule 1: Never use the "Automatically Expose UI Componentes in a New Managed Bean" option, create your bindings manually;
Rule 2: Rule 1 is always right;
Rule 3: In doubts, refer to rule 2.
You may also want to check out :
http://groups.google.com/group/adf-methodology
And :
http://www.oracle.com/technology/products/jdev/collateral/4gl/papers/Introduction_Best_Practices.pdf

Best practices for deploying forms in a 'cluster'?

Anyone know of any public docs that discuss typical best practices for
- forms deployment;
- forms apps management and version control; and/or
- deploying (and keeping) the .frm/frx in sync when using multiple forms servers in a HA or load balancing envrionment?

Hi adil,
Based on your description, you want to know the best practices for search service in a SharePoint farm.
Different farms have different search topologies, for the best search performance, I recommend that you follow the guidance for small, medium, and large farms.
The article is about the guidance for different farms.
Search service can run with other services in the same server, if condition permits and you want to have better performance for search service and other services including BI performance, you can deploy search service in dedicated server.
If condition permits, I recommend combining a query component with a front-end Web server to avoid putting crawl components and query components on the same serve.
In your SharePoint farm, you can deploy the query components in a WFE server and the crawl components in an application server.
The articles below describe the best practices for enterprise search.
https://technet.microsoft.com/en-us/library/cc850696(v=office.14).aspx
https://technet.microsoft.com/en-us/library/cc560988(v=office.14).aspx
Best regards
Sara Fan
TechNet Community Support

Best practice for deploying the license server

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Deployment from DEV to Production environment

Hi,
What are the best possible ways to deploy the visual web parts and Pages from development environment to Production environment.
As I am very much new to Sharepoint, I would like to have the safest methods to do the deployment into production. Please also suggest the prerequisites.
I have a solution with number of visual web parts in the development environment which is working fine. Need to move the Visual web parts to production (Existing site). So please suggest the safest methods.
Thanks and Regards,
Satish
Sathiish Reddy

Hi Satish,
From your description, my understanding is that you want to deploy your solution from development environment to production environment with a safest method.
These links below about moving content from environment to another environment could be helpful to you:
SharePoint 2013 Dev/Test/Production environment - Moving content
http://sharepoint.stackexchange.com/questions/78483/sharepoint-2013-dev-test-production-environment-moving-content
How to deploy webpart on production (not debugging) server?
http://sharepoint.stackexchange.com/questions/17779/how-to-deploy-webpart-on-production-not-debugging-server
you could also have a look at this link below about SharePoint Content Deployment Wizard:
How do you deploy your SharePoint solutions?
http://stackoverflow.com/questions/9543/how-do-you-deploy-your-sharepoint-solutions
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Need Best Practice for Migrating from Solaris to Linux

Hi Team,
We are migrating our Data Center from Solaris to Linux and our EBS 11i, database 10g (10.2.0.5) is 6TB. Please let us know the Best Practice to Migrate our EBS 11.5.10.2 from Solaris to Linux RHEL 5.
we require Database 10g (10.2.0.5) on Linux x86-64 RHEL 5 and Application EBS on Linux x86 RHEL 5. Please let us know for any details.
EBS version: 11.5.10.2
DB version: 10.2.0.5
We have checked the certifications in Oracle support.
Oracle EBS 11.5.10.2 is not certified with Linux x86-64 RHEL 5.
Oracle EBS 11.5.10.2 is certified on Linux x86 RHEL 5.
So we require Database 10g (10.2.0.5) on Linux x86-64 RHEL 5 and Application EBS on Linux x86 RHEL 5.
Thank You.

You can transportable tablespace for the database tier node.
https://blogs.oracle.com/stevenChan/entry/10gr2_xtts_ebs11i
https://blogs.oracle.com/stevenChan/entry/call_for_xtts_eap_participants
For the application tier node, please see:
https://blogs.oracle.com/stevenChan/entry/migrate_ebs_apptiers_linux
https://blogs.oracle.com/stevenChan/entry/migrating_oracle_applications_to_new_platforms
Thanks,
Hussein

Best practice for upgrading task definition in production system

If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

The best way for upgrade purposes is to use the rename function of the TaskDefinition from the lh command line utility.
Basically renames all current task instances with the TaskDefinition name. You can then alter the existing TaskDefinition and upload into identity manager.

Best practice for moving from a G5 to a new Mac with SL

I am receiving my new iMac today (27") and am very excited
However I want to move over using the best practices to assure that I remain excited and not frustrated
My initial thoughts are to boot it up and doe the initial set up - to move my iPhoto library over and to use migration assistance to move the rest of my data files
Then to install all of the extra software that I can find the packages for from the original installation disks
And then finally to use migration assistant again to move over any software that I can not find original disks for (I've moved from Mac to Mac to Mac over and over and some of the software goes back to OS 9 (and won't run anymore I guess)
Is this a good way
OR
will I mess up doing it this way
OR
am I spending far too much time worrying about moving old problems over and would be better off to just turn MA loose and let it do its thing form the beginning?
BTW - mail crashes a lot on my existing system - pretty much everything else seems ok - except iPhoto is slow - hoping that the new Intel dual core will help that
LN

Migration Assistant is not a general file moving tool. MA will migrate your Applications and Home folders transferring only your third-party applications. MA will transfer any application support folders required by your applications, your preferences, and network setup. You do not have a choice of what will be migrated other than the above. MA cannot determine whether anything transferred is compatible with Snow Leopard. I recommend you look at the following:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior 4.1, TechTool Pro 4.6.1, SuperDuper 2.5, and Drive Genius 2.0.2 work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode, copying the critical contents to CD and DVD, an external hard drive, or networking
will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.
If both computers support the use of Firewire then you can use the following instructions:
1. Repair the hard drive and permissions using Disk Utility.
2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.
3. Connect a Firewire cable between your old Mac and your new Intel Mac.
4. Startup your old Mac in Target Disk Mode.
5. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)
1. Set up a local home network: Creating a small Ethernet Network.
2. If you have a MacBook Air or Late 2008 MacBook see the following:
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- Migration Tips and Tricks;
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
MacBook Air- Migration Tips and Tricks;
MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.
Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/ (copy the whole folder)
/Home /Library/Calendars (copy the whole folder)
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to Macjack for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.
Revised 1/6/2009
In general you are better off reinstalling any third-party software that is PPC-only. Otherwise update your software so it's compatible with Snow Leopard.
Do not transfer any OS 9 software because it's unsupported. You can transfer documents you want to keep.
Buy an external hard drive to use for backup.

Best Practices for deployment of Oracle 10g database.

Hello ,
Is anyone aware of a whitepaper/ document that talks about best pratices in deploying a database on Oracle 10g and configuration of the database to utilize all the features available in 10g ( eg. ADDM , reports setup etc )
Thanking you in Advance.
Cheers..rCube

Appreciate the input Jaffer. Thanks.
However I was referring to a Best Practices whitepaper like the one existing for Data Guard & MAA available at the follwogng url : - http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm
Is there something available along the same lines ?
Cheers..rCube

Best practice for upgrading from ADS 9.1 to ADS 11

So we will need start upgrading installs from Advantage Database Server (ADS) version 9 to ADS version 11. Is there a set of best practices? Certain procedures? How do we gracefully fall back if it doesn't work? Does anyone have experience with the dual install setup of ADS 9 and ADS 11? Did anyone else run into any issues with this upgrade path?
Thanks in advance!
Rodney

Rodney,
My first recommendation is to read the "Effects of Upgrading" section of the help file. I put the links below.
Effects of Upgrading to Version 10
Effects of Upgrading to Version 11
Effects of Upgrading to Version 11.1
The server will always work with an older client so I would recommend upgrading the server and testing it with your current application. The next step would be to upgrade the client and re-compile your application. I wouldn't anticipate any issues other than those outlined in the effects of upgrading.
You can install multiple instances of Advantage, beginning with version 10, on the same machine. Keep in mind that only one instance, the first one installed, will be discoverable. To connect to other instances you will need to use <IP Address>:<Port> in the connection string. Details on installing additional instances of Advantage are here
Chris

Best Practice for deploying in Production Cluster

          I have the following.
          2 Physical machines each running 2 jvm's, thus I have 4 jvm's in my cluster.
          We access the jvm's via an IIS plug-in.
          When it comes time to do a new .war file migration, do you need to stop the jvm's
          first ?
          I have tried deploying with the jvm's live, it technically worked but we then
          noticed several 404 errors during the day on a servlet that was there. (Called
          successfully around the 404)
          Anyway, I'm just looking for recomendations on how others deploy to production.
          Tim


          Tim wrote:
          > I have the following.
          >
          > 2 Physical machines each running 2 jvm's, thus I have 4 jvm's in my cluster.
          >
          > We access the jvm's via an IIS plug-in.
          >
          > When it comes time to do a new .war file migration, do you need to stop the jvm's
          > first ?
          You should be able to redeploy a web application without any
          problems? When you get this 404 errors, do you see any stacktrace
          on the server window
          Kumar
          >
          >
          > I have tried deploying with the jvm's live, it technically worked but we then
          > noticed several 404 errors during the day on a servlet that was there. (Called
          > successfully around the 404)
          >
          > Anyway, I'm just looking for recomendations on how others deploy to production.
          >
          > Tim

Best practices for deployment from Dev /Staging /Production in SharePoint ?

Similar Messages

Maybe you are looking for