Sunday, August 26, 2012

MIGRATING CONTENTS FROM DEV TO HIGHER ENVIRONMENTS


MIGRATING CONTENTS FROM DEV TO HIGHER ENVIRONMENTS

Basic Steps & Directions

Move content from one SharePoint 2010 site into a set of lists or document libraries located in another SharePoint 2010 site.
Before we start moving content, you need to complete a small checklist of tasks.
·         Make sure you have set up and configured a PerformancePoint Service Application that will be used by the destination Web application.
·         Recreate the current site and list structure in the destination Web application.
·         Think about a security structure and implement it.

First point-- Without a destination Web application that is connected to a PerformancePoint Service Application, migration won’t work.

Second point -- PerformancePoint Services 2010 content migration tool doesn’t recreate existing site structures. You need to recreate the exact same site structure in the destination Web application. Failing to do so results in broken PerformancePoint references.

Third & Final point -- You need to implement a security structure, because existing permissions from a SharePoint 2010 source will not be migrated to a SharePoint 2010 destination. Instead, the existing destination security structure will be used.
Step 1-- Use the PerformancePoint Dashboard Designer to migrate content from a SharePoint 2010 source to a SharePoint 2010 location. PerformancePoint Dashboard Designer is a ClickOnce application that needs to be downloaded and installed once from a Business Intelligence Center. This can be done by creating a new site collection using the Business Intelligence Center template.
Step 2-- After you have created the BI center, you need to click the Start Using PerformancePoint Services link and click the Run Dashboard Designer button, which starts the download and installation of the client (note that a client requires .NET Framework 3.5 SP1).
The following procedure explains how to migrate content from a SharePoint 2010 source to a SharePoint 2010 location.
1.      Launch the PerformancePoint Dashboard Designer by clicking Start, selecting All Programs, and then selecting SharePoint. Select PerformancePoint Dashboard Designer.
2.      Load an existing dashboard.
3.      Click the Office button and then select the Save Workspace As option to save the existing dashboard as a Dashboard Designer Workspace.
4.      Point the Dashboard Designer to the destination location. You can do this by choosing Designer Options, which can be opened by clicking the Office button, choosing the Server tab, and specifying a new location.
5.      Click Import Items, which is located at the upper right on the Ribbon.
6.      Browse to the previously created Dashboard Designer Workspace.
7.      Select the items you want to copy to the destination location.
This action will cause the Import Items To SharePoint Wizard to start copying PerformancePoint content to the new location. The final screen in the wizard displays a summary that allows you to open the migration log files if you want to see more details.
There are a couple of issues you need to be aware of when it comes to moving PerformancePoint 2010 content.
a)      When you select an object in Dashboard Designer, it loads all of the dependencies of that object. For example, opening a dashboard definition in SharePoint Designer will cause all of its dependencies to be loaded. This means that you should always choose objects that are high in the hierarchy when moving content (a top-down approach) to save time.
Dashboard Designer allows you to skip existing data sources during content migration. Typically, you will migrate them once, update data source references in the destination location (which is often needed in a new environment), and after that leave them as they are. This way, you will have to update those references only once.
Dashboard Designer ensures those references will also be updated, whereas SharePoint migration tooling just migrates the content and leaves those references as is. However, you can use the SharePoint backup and restore tools as long as you restore content to the same site structure. In that case, the references don’t need to be updated.

 

Step By Step details of Migrating Reports/Dashboard/Scorecard  from one Environment to Another


To migrate your content from one environment to another (for example:  development to test, test to production, etc), flowing approach is recommended.

First, you will need to pull the content from your PerformancePoint Monitoring Server  into a workspace file locally using the Dashboard Designer.  Only pull the content that you wish to migrate into a clean workspace file.  If you select a dashboard, all of the scorecards, KPIs, data sources, indicators and report views associated with that dashboard will be also included.  Similarly, if you select a scorecard, all of the KPIs, data sources and indicators associated will also be included.  Save this workspace file locally. 

From the dashboard designer connected to the new server, open the workspace (bswx) file that you saved.  Follow the below steps to modify the settings and publish to your new server.

Change the server name

1.       From the Options dialog box (File > Options), select the Server tab.
2.       Change the Server URL to the URL for your new Monitoring Server, such as http://<<NewServer:>><<Portno>>/WebService/Service.asmx.
3.       Change the Server name URL to the URL for your new Monitoring Server.
4.       Click Connect to verify the server is working properly.
5.       Click OK to close the dialog box.

Update the data source

1.       Select the first Data Source in your workspace file.
2.       Change the connection information to the new location of the data.  Note, if you built your content on your production data, these will not need to change.  If you built your content on a test or development copy of the source date, these will all need updated.
3.       Click Test Connection to ensure that your data source is properly configured.
4.       From the properties tab, update the Owner field and the User Permissions field with the proper credentials.  Note, if the users are the same in both of your environments, this step will not need to be completed.
5.       Repeat for each data source. 

Update the scorecards

1.       Select the scorecards you wish to update.
2.       From the properties tab, update the Owner field and the User Permissions field with your  proper credentials.  Again, only required if users are different between your two environments.

Update the reports

1.       Select the Reports folder from the Workspace Browser.
2.       Highlite all Reports in the Workspace (making sure that the Workspace tab is selected in the Workspace area).
3.       Select the Bulk Edit toolbar button on the Home tab.
4.       Update the Owner field with the proper credentials.  Only required if the users are different between your two environments. 
5.       Select Next then Finish.

Update the dashboard

1.       Select each of the dashboards.
2.       From the properties tab, update the Owner field and the User Permissions field with the proper credentials.  Only required if the users are different between environments.

Publish the dashboard and its views

1.       From the Home tab of Dashboard Designer, click Publish All.
2.       On the Export tab, click SharePoint.
3.       Select the dashboard to deploy.  Click Next.
4.       Type the SharePoint URL (such as http://MyServer/).
5.       Select the Document Library for your published dashboard and click Next.
6.       Click Finish to accept the default master page and publish the dashboard.



Some sample Screenshots of how the steps are performed.
In Performance Point Services 2010 we need to start out by opening up Dashboard Designer and connecting to the new environment.



Click on the Import Items button in the Home Ribbon of Dashboard Designer and select your workspace file (this will be the file from your other environment that contains the content that you want to migrate and move to the new server).


Now you will walk through a wizard to select the content that you want to import to the new server (environment).

In this case I am going to do both items and I only have one location for each on my new server that I am moving the content to.





The items will now be imported and saved to the specified locations and you will receive a results 
page.





You can then add the items to the workspace and start to make the necessary changes. 





Sunday, November 14, 2010

Why Upgrade to 2010 & Different Approaches for


[ Why Upgrade ?

&

Different Approaches]

This document contains Reasons to Upgrade to SharePoint 2010 from SharePoint 2007.




Why Upgrade & Different Approaches

Why Upgrade?

  • License getting expired : If License of MOSS2007 is getting or already has expired, than apart from going for getting it renewed, we can go for SharePoint 2010 which offer you a huge variety of New WebParts and Features
  • Connect and Empower people: SharePoint 2010 enables people to access resources from anywhere and at any time, which let them work efficiently and promptly. SharePoint 2010 integrates seamlessly with Microsoft Office enhancing user experience for accessing, editing and publishing SharePoint sites
  • Cut Costs with a unified Infrastructure: SharePoint 2010 optimizes IT resources by lowering the total cost of ownership. It does this by combining key business collaboration solutions with SharePoint 2010 and further leveraging the common platform to execute solutions for intranet, extranet, and internet presence.
  • Rapidly Respond to Business Needs: SharePoint 2010 makes it possible to shorten the time between understanding a business need and delivering business productivity solutions for it.
  • Reduce Cost as dependency on MSOffice on Client Side Office is removed: Microsoft Office Web Applications allows users to work on Microsoft Word, PowerPoint, Excel and OneNote in the browser with the ability to do co-authoring on the Web and the Client Microsoft Office 2010.
  • SharePoint 2010 UI: SharePoint 2010 UI is much more powerful with inclusion of Ribbon and support for Silverlight and AJAX which allows users to reduce learning curve. SharePoint is more clicks and page post backs. You will find consistent user interface across all levels.
  • Advanced Searching: Search is powerful that ever with FAST Search which allows them to find information and saw preview of search results without even opening the documents. Search results provide easier and most flexible filtration and having the ability to include federated search from Google or Bing makes search results efficient.
  • Fast Search – If you are a sales executive looking for a particular type of presentation or company resource. Just type in a keyword. Fast Search will search not just titles, keywords or description, but the actual documents themselves. And it knows, based on your role, what you might be interested in (Sales).
  • List Joins - We will finally be able to query lists and join them.
  • Significantly improved user experience - The Microsoft Office ribbon, Silverlight and client object model, better CSS, etc...
  • Visio diagram --> SharePoint Designer Workflow --> SharePoint Workflow - completely seaming-less and not an ounce of C#
  • Built in support for database mirroring
  • PowerShell
  • Corporate Taxonomy: It is huge! And if you don't know what it is, read about it. In today's world, organizations are literally flooded with information. Forget storing your documents on a file share somewhere. SharePoint 2010 allows you to categorize, contextually search, and easily find whatever you are looking for.
  • Logging database with windows event logging and health reporting
  • Reusable Workflow Templates: Single Workflow can be used multiple times by associating it with multiple lists & libraries.
  • Wild Card Search: Enhancements to search allow employees to perform complex queries from SharePoint or the Windows 7 desktop. The queries can now include wildcards, Booleans, and free-text, as well as pre- and post-query suggestions
  • Graphical Output in form of Charts without using 3rd party tools: The SharePoint 2010 charts can be customized in various different ways and because of that can be a really powerful way to visualize data for your business. Whatever you would like to visualize, SharePoint 2010 Chart Web Part can help you – moreover, its configuration and customization is very easy
  • Support for Mozilla FireFox: SharePoint 2010 supports both internet explorer as well as the 3.x versions of Mozilla firefox.
  • Better Security Model: SharePoint Server 2010 incorporates a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory services, LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID
  • Maintenance: As far as the maintenance is concerned. There are many improvements. The administration is simple and one way which means you don’t have to go to many places to do it. Backup and restore has been improved which allows us to take backup at any level of SharePoint Implementation. Configuration, Site, List etc. The restoration form these backups is also lot easier than before. Administrator can take backup of SharePoint databases on the fly using the SQL Snapshot and restore it to same SharePoint farm to restore any part of it at any time.

Upgrade Approaches

There are two ways of moving from MOSS2007 to SharePoint 2010.

    1. Perform a database attach upgrade

Your browser may not support display of this image.

    1. Perform an in-place upgrade

Your browser may not support display of this image.

Note -- We have successfully implemented a Migration project using Perform a database attach upgrade

Other Technical benefits of SharePoint 2010

  • Web Analytics: SharePoint 2010 includes a Web Analytics service so that enterprises can monitor site usage and search terms. For companies drowning in unused sites (e.g., a project site goes live, is used intensively for two months, and then never used again), this capability will be invaluable in helping them clear out the deadwood. In addition, it will help companies understand how their employees are using SharePoint—the first step in optimizing site design, terms, and so on
  • Visio Integration: Business users can use familiar tools to create the outline of a workflow and then export that workflow to a SharePoint Designer workflow for configuration.
  • Enterprise Content Management (ECM):
  • Social Networking sites like My Sites with Tagging functionality: One of the top features is the Social Features of SharePoint 2010. Now all users can get together easily and share information and knowledge using the Face book like functionality available at MySite
  • Enhancing SharePoint 2010 with Silverlight: SharePoint 2010 has evolved incredibly over previous versions and now offers native support for Silverlight. In turn, Silverlight can create a very powerful experience for your end user, creating vastly dynamic and compelling business applications or media-rich Internet solutions. The convergence of SharePoint and Silverlight is growing and is extremely powerful.
  • Improved WIKI: SharePoint 2010 is completely a WIKI application which allows people to share information and produce knowledge lot easier than before. Creating WIKI pages on the fly and allowing other people to comment results in fast collaboration and knowledge development.
  • Improved Blogs: Blogs have been improved to provide blogging from Office word or Live Writer allows users to publish personal or enterprise blogs very easily.
  • Integration with Performance Point Server: Microsoft SharePoint Server 2010 BI Stack extends the capability to develop BI Dashboards and KPI. Using Performance Point Services users can easily create dashboards, KPIs, Scorecards, Graphs and many more types of reporting. Microsoft Power Pivot for Excel enables end users to build rich Pivot tables that can get data from any data source in the company.
  • Inbuilt DAM (Digital Asset management ) Support : SharePoint 2010 Supports Digital Asset Management of Videos, Images etc. and users can simply drag and drop images and videos on the pages and play for others.

For detailed list kindly click here…. Your browser may not support display of this image.

Small Comparison Chart of MOSS 2007 and SharePoint 2010:

MOSS 2007

SharePoint 2010

Does not support SilverLight

SharePoint 2010 supports SilverLight without needing any additional configuration, along with SilverLight web part.

Business Data Catalogue (BDC) in MOSS 2007 gets data from external source (LOB Data) but data is read only.

In SharePoint Server 2010, BDC is known as BCS (Business Connectivity Services). It allows read from and write to data, from external source (LOB Data).

Unable to integrate with Sandboxed Solutions.

Site administrators can safely custom user code by using Sandboxed Solutions through SharePoint Server 2010.

Does not display Ribbon interface like MS Office 2007.

SharePoint Server 2010 displays Ribbon interface allowing users to manage various options for applications upfront.

MOSS 2007 supports only internet explorer and not Firefox

SharePoint 2010 supports both internet explorer as well as the 3.x versions of Firefox .

Some functionality including Multi-Select Document checkout /check –in, delete are present in the content and structure pages.

The functionality such as Multi-Select Document checkout /check –in, delete Multi-Select Document checkout /check –in, delete in the available in Document Libraries.

Users cannot use PowerPoint themes to tweak the sites’ visual appeal

In SharePoint 2010, users can change the site’s visual appeal with the help of PowerPoint themes.

Activity feed, profile picture and social feedback aren’t available on My Site

Activity feed, profile picture and social feedback are available on My Site.

Users cannot use benefit from out of box Vision Web parts to deliver vision diagrams within browser.

SharePoint 2010 users can deploy the out of the box Visio web parts to deliver Visio diagrams.

Folders cannot be used in 2007

SharePoint 2010 helps users organize metadata at folder level



Only reasons to Stay back on 2007

5 Reasons You Might Consider Waiting While it ultimately may come down to your timelines,

  • Timeline
  • Requirements addressed with 2007
  • Data Center or Hardware Standards Requirements Your companies ability to support 64 bit Windows Server 2008 or SQL 2008 (or SQL 2005 SP2)
  • Company adoption standards of products or even specifically Microsoft products
  • Lack of knowledge on licensing & release date for planning