- Publishing, Viewing Dashboards, Management and delivery of reports through Sharepoint user interface.
- Leverage Sharepoint Collaboration and work flow capabilities with rich reporting experience.
- Shared security principles across SSRS and Sharepoint.
- Minimize the resource usage by eliminating separate reporting server.
Thursday, July 14, 2011
Sharepoint 2010 Integration with SSRS 2008R2
Thursday, February 24, 2011
Top 10 FAQs for Admins about BCS
Wednesday, February 2, 2011
Tags and Notes in Sharepoint MySites
Tags and Notes in MySites
Tags and notes is one of the key featuring in Sharepoint 2010 my sites. This shows the likes and tags of the users which let other users know more about them.
How it works?
When the user clicked on "I like it" or "Tags and Notes" links at the top right of the each page it will ask the name and notes about that tag.
This will be stored as tag to that page and displayed on the users MySite under "Tags and Content"
Removing the inappropriate tags
If the users post something which is inappropriate, Farm administrator has ability of managing those tags by navigating the following link.
SP Central Administration à Application Management à Manage service applications à Click on User Profile Service Application à Manage Social Tags and Notes
This provides a Search page as follows which shows the tags belong to particular page or users. Farm Admin can remove these tags if they are inappropriate.
Please find the following TechNet article to know more about Privacy and security implications of social tagging.
http://technet.microsoft.com/en-us/library/ff608006.aspx#sectionHidden
Wednesday, November 10, 2010
Project Server 2010 Architecture
Microsoft Project Server 2010 is a true multi-tiered system that extends the architecture introduced in Microsoft Office Project Server 2007. The Project Server architecture includes Microsoft Project Professional 2010 and Project Web App clients in the front-end tier. The front-end applications communicate with the middle tier only through the Project Server Interface (PSI) Web services, which in turn communicate with the business object layer. Business objects use the databases through the data access layer (DAL). Client applications do not directly access the primary databases; Project Server hides business objects and the DAL from clients.
The major differences between Project Server 2010 and Office Project Server 2007 are the following:
- Project Server 2010 requires Microsoft SharePoint Server 2010 to be installed on the computer running Project Server and on all Project Web App servers within a SharePoint farm.
- The PSI includes both the Windows Communication Foundation (WCF) interface and the ASMX interface for Web services.
- The Project Server workflow platform is integrated in the PSI, business object layer, and DAL, and built on Windows Workflow Foundation (WF) in the SharePoint platform.
- In Project Server 2010, you can use the WCF or the ASMX interface of the PSI. The Project Web App and Project Professional 2010 clients both use the WCF interface.
- The PSI Forwarder in the following diagram consists of two components, a WCF Forwarder and a Web Service Forwarder. Clients that use the ASMX interface call the PSI through the Web Service Forwarder. Clients that use the WCF interface call the PSI through the WCF Forwarder.
- The SharePoint Web Services site is part of SharePoint Server 2010 and is not shown in the following diagram. The SharePoint Web Services site includes the Project Service Application with the PSI virtual directory for the ASMX and WCF services. The Project Service Application in Project Server 2010 replaces the Shared Services Application in Project Server 2007.

Architecture of Project Server 2010 |
- The front-end tier includes third-party applications, Project Professional, and Project Web App. Project Web App uses Internet Explorer to display Microsoft ASP.NET 3.5 pages. The Project Web App pages use Project Server Web Parts that communicate with the PSI and also use standard SharePoint Server 2010 Web Parts.
- Client applications on separate computers call the PSI through service proxies. External clients that use the WCF interface access the PSI through http://ServerName/ProjectServerName/_vti_bin/psi/ProjectServer.svc. Clients that use the ASMX Web service interface use one of the Project Web App URLs, such as http://server1/pwa/_vti_bin/psi/project.asmx. If applications do not have intranet access to Project Server, they can use a Project Web App server in a perimeter network.
- If they can directly access the Project Server computer, client applications and back-end components of line-of-business (LOB) Web applications can use PSI proxies that use the Project Server service application URL for the PSI Web services, such as http://server1:32843/ProjectServiceApplication/project.asmx. Port 32843 is the default port for the SharePoint Web Services application in SharePoint Server 2010. Direct access to the Project Service Application virtual directory should be used only when an application needs to use impersonation or run with elevated permissions.
- The middle tier includes the PSI and the business logic layer, which consists of logical business objects that represent Project Server business entities. Business objects include Project, Task, Resource, Assignment, and so forth. The PSI and the business logic tier are tightly coupled and are located on the same server. A client application calls the PSI Web services, and the PSI invokes business objects in the business logic tier.
- The DAL provides communication between the middle tier and the database. All Project Server data is stored in Microsoft SQL Server databases. The Project Server databases are factored into the following stores: Draft, Published, Archive, and Reporting. Client applications can read the Reporting database for project data. Clients should use only the PSI to access the Draft, Published, or Archive databases. The Reporting Data Service (RDS, which is not shown in Figure 1) updates the Reporting database from published data in nearly real time. In Project Server 2010, all of the Project Server databases can be located on separate servers.
- The Project Web App components of Project Server also use the SharePoint Foundation 2010 configuration database for project site setup and the content database for project site content such as custom pages, workflows, management settings, documents, and lists of issues, risks, and commitments. The SharePoint configuration and content databases support additional features for project management, such as project templates and workspaces, custom lists for team collaboration, and reports.
Data Access Layer and Databases
The DAL is internal to Project Server and is not exposed to external applications. The DAL translates between the logical business entity representation of the data and the physical database tables. Each logical entity is stored in a number of different tables. The DAL encapsulates the work required to manage connections, execute queries, and begin/commit/roll back transactions.
Project Server data is partitioned into four databases in SQL Server.
- The Draft database contains tables for saving unpublished projects from Project Professional and other applications. Project Web App does not show project data in the Draft database.
- The Published database contains all of the published projects and enterprise resources, the enterprise global template, and other project templates. Published projects are visible in Project Web App. The Published database also contains tables that are specific to Project Web App (timesheets, models, views, and so on), and global data tables (custom fields, lookup tables, security, and metadata).
- The Archive database saves backup versions of projects and other data.
- The Reporting database (RDB) is the staging area for generating reports and OLAP cubes. Data in the Reporting database is comprehensive and is updated nearly in real time. The tables and views are optimized for read-only report generation; for example, the RDB tables are denormalized to provide redundant data and reduce the number of relational tables.
Monday, October 18, 2010
EPM --> MS Project --> MS Project Server
EPM:
- Enterprise Project Management (EPM), is the field of organizational development that supports organizations in managing Projects, Resources and the Cost of the projects.
- EPM provides the proper governance for the projects which are running under the organizations in terms of Schedules, Cost and Resources.
- Schedules meant for creating tasks related to the project to be completed in a particular timeframe. Cost includes the money and the time spent to the project and Resources stands for the people and resources needed for completing the project.
- EPM is very useful to make life easier for the managers to manage, monitor, and assess the status of all projects under them.
- Project Portfolio Management (PPM) is also a part of the EPM which is used to create a portfolio (per budget size, per calendar year, per budget year, per business line, etcetera) for projects.
- Project Portfolio Management also includes the creation of various scenarios to decide which is the most optimal portfolio (for a certain year, business, budget, etcetera)
- There is already number of tools available for EPM in the market. "Microsoft Project and Microsoft Project Sever" are the tools which have been provided By Microsoft for adopting EPM Capabilities.
- Microsoft Project (or MSP or WinProj) is a project management software program developed and sold by Microsoft which is designed to assist project managers in developing plans, assigning resources to tasks, tracking progress, managing budgets and analyzing workloads.
- MSP is a Microsoft Office tool the can be used to create applications that creates critical path schedules, and critical chain and event chain methodology Schedules can be resource leveled, and chains are visualized in a Gantt chart. Additionally, Project can recognize different classes of users. These different classes of users can have differing access levels to projects, views, and other data. Custom objects such as calendars, views, tables, filters, and fields are stored in an enterprise global which is shared by all users.
- Microsoft Project 2010 features the Ribbon user interface; the current Version for the MSP is 2010.
- The following diagram shows the basic look of a project which has been created using project sever 2010.

- The above diagram shows the project which has been created by manager which contains all main Phases involved in that project. The Gantt chart shows the Schedules for each phase.
- This contains Menu with all the capabilities includes task scheduling Resource management.
All these above can be done when we have been installed with MS Project Software. These files cannot be useful if we don't have project. This leads Microsoft to Develop Microsoft Office Project server 2010.
1) Microsoft Office Project Server is a project management server solution made by Microsoft. It uses Windows SharePoint Services as its foundation, and supports both a web interface and Microsoft Project as the client application.
2) Microsoft extends the capabilities of Microsoft Project with Project Server and Project Web Access. Microsoft Project Server stores project information in a central SQL Server database, protected from unauthorized access and corruption. A Project Administrator can control security defining users and access rights.
3) Being it built on Sharepoint, We can extend its capabilities by developing the Webpart programming and can use Sharepoint object model for programming from other applications using SP API's.
4) The following screen shows a project created by the manager in the Project Sever 2010 Web application.
5) We can sync this application with MS Project by creating project service application in Sharepoint.
SharePoint 2010 Search
Microsoft Provides following search Capabilities for Sharepoint Enterprise Search
a) SharePoint Foundation 2010
b) Search Server 2010 Express
b) Search Server 2010
d) SharePoint Server 2010
e) FAST Search Server 2010 for SharePoint
2) Microsoft provides SharePoint Foundation 2010 and Search Server 2010 Express free of charge for you to use on licensed Windows® servers. These entry level products offer the ability to crawl and index content and provide a user interface for executing queries against the catalog of crawled content.
3) SharePoint Server 2010 and Microsoft Search Server 2010 offer improved scalability and options for indexing content from many different sources, while fulfilling the configurability, manageability, and reporting requirements of your organization.
4) SharePoint Server 2010 provides a great platform for creating general productivity search applications.
5) FAST Search Server 2010 for SharePoint is a new product from Microsoft, and it delivers the power of FAST with the simplicity and total cost of ownership (TCO) benefits of Microsoft products. FAST Search Server 2010 for SharePoint further enhances the crawling, content processing, user interface, and scale
of SharePoint Server 2010.
Feature Comparison
You can use the following table to make quick comparisons of the enterprise search features provided by each product in the SharePoint 2010 Products.| Feature | SharePoint Foundation 2010 | Search Server 2010 Express | Search Server 2010 | SharePoint Server 2010 | FAST Search Server 2010 for SharePoint |
| Basic site search | Y | Y | Y | Y | Y |
| Best Bets | Y | Y | Y | Y | |
| Visual Best Bets | Y | ||||
| Similar Results | Y | ||||
| Duplicate Results | Y | Y | Y | Y | Y |
| Search Scopes | Y | Y | Y | Y | |
| RSS Feeds for Search Results | Y | Y | Y | Y | Y |
| Alerts for Search Results | Y* | Y* | Y* | Y* | |
| Advanced Search Page | Y | Y | Y | Y | |
| Search Enhancement based on User Contexts | Y | ||||
| Crawled and Managed Properties | Y | Y | Y | Y** | |
| Entity Extraction | Y | ||||
| Query Federation | Y | Y | Y | Y | |
| Query Suggestions | Y | Y | Y | Y | |
| Sort Results on Managed Properties or Rank Profiles | Y | ||||
| Relevancy Tuning by Document or Site Promotions | Y | Y | Y | Y** | |
| Shallow Results Refinement | Y | Y | Y | Y | |
| Deep Results Refinement | Y | ||||
| Document Preview | Y | ||||
| Windows 7 Federation | Y | Y | Y | Y | |
| People Search | Y | Y | |||
| Phonetic Name Search*** | Y | Y | |||
| Nickname Search*** | Y | Y | |||
| Self Search | Y | Y | |||
| Social Search | Y | Y | |||
| Taxonomy Integration | Y | Y | |||
| Multi-Tenant Hosting | Y | ||||
| Rich Web Indexing Support | Y |
First Steps
There are some general tasks you will need to perform when you are evaluating search products or implementing enterprise search solutions that meet your organization's requirements. The following sections can help you get started.
Identify your content
The first step you need to take before performing any actions is to identify the content in your organization that you want to index. Content from SharePoint sites is automatically included in all of the SharePoint search products, but you can also index content from file shares, Microsoft Exchange public folders, external Web sites, Lotus Notes databases, and your line-of-business applications.You can also use SharePoint Designer 2010 or Visual Studio 2010 to create Business Data Catalog applications that enable custom databases, Web services, and other custom solutions to be indexed.
Note: SharePoint Foundation 2010 can only index content in SharePoint sites. All other enterprise search products from Microsoft can index content in the content repositories mentioned above by using the connector framework.
FAST Search Server 2010 for SharePoint also provides enhanced capabilities for indexing business intelligence data. You can obtain the Business Intelligence Indexing Connector to provide enhanced search and analysis for business intelligence assets.
Crawl your content
The next step is to crawl the content in the content repositories that you have identified. You can implement both full and incremental crawl schedules to ensure that indexed data is as fresh as possible.The new index partitioning capabilities of Search Server 2010, SharePoint Server 2010, and FAST Search Server 2010 for SharePoint enable you to balance the indexing load (and query load) across servers that are dedicated to provide search for large amounts of content.
Scale your search infrastructure
One of the design goals for Search Server 2010 and SharePoint Server 2010 is to provide sub-second query response times for up to 100 million indexed documents. For FAST Search Server 2010 is designed to provide sub-second query response times for more than 1 billion indexed documents. To achieve sub-second query response times for your organization you may need to scale your server farm to include multiple query servers. Additionally, to ensure that indexed data is as fresh as possible when indexing a large number of documents, you may need to include multiple indexers. The highly componentized architecture of the enterprise search products from Microsoft enables you to do just that; for example, you can implement partitioned indexes on multiple indexers to be able to cope with crawling demands, and you can include multiple query servers to balance the query processing load at search time.Customize the end-user search experience
Optionally, you may want to provide a customized user interface so that information workers can search for information and manipulate results in the most efficient way for your business. The Enterprise Search Center for SharePoint Server 2010 and the FAST Search Center are highly customizable without requiring developer effort. For example, you can create search scopes, modify properties of search Web Parts, apply XSLT styles, and apply themes to search centers with minimal effort. All of this can be done through the Web browser or by using SharePoint Designer 2010.If you need to customize the search experience further, then developers can create a completely customized user interface by creating new Web Parts that inherit functionality from the existing search Web Parts. Furthermore, the search API is completely open so developers can create new paradigms and ways of working with search, such as by creating new Web Parts or even Silverlight applications that run searches and render results.
Customize the content processing pipeline
One of the key differentiators between FAST Search Server 2010 for SharePoint and other search products is the ease with which you can customize content processing at indexing time. FAST Search Server 2010 for SharePoint enables you to create your own metadata extractors that will be used in the content processing pipeline. This enables you to define how managed properties are populated from crawled content, and you can then use that metadata in deep refiners; you can then include these organization-specific vocabularies in the metadata refinement panel which enables you to provide search solutions in the terms and language of your business.Thursday, August 19, 2010
Sharepoint 2010 Basics
1) Introduction to SharePoint 2010 :
2) Sharepoint 2010 and custom workflows :
3) Business Connectivity Services in SharePoint 2010:
a) Business Data Catalog in Sharepoint 2007 is now Enhanced as Business Connectivity Services in Sharepoint 2010.
Thursday, July 22, 2010
Sharepoint Backup Scheduling using Powershell
Here we go
This is about powershell backup script to automate sharepoint backups.
Hope most of you got a good idea about microsoft new revolution PowerShell. That even rocking Sharepoint 2010.
(To know more about Windows poweshell click
Here)
(To know more about Sharepoint poweshell click Here)
* Refers to the above links Windows powershell runs with powershell commands.
* These powershell script files will be stored with extension .ps1
* To run this script files user needs to be provided with powershell admin priviliges.
* You can use Backup-SPFarm to do it. For help and examples, type get-help Backup-SPFarm -examples.
For example, the follow script will start a full backup to
Backup-SPFarm -Directory
Save it as .ps1 . You may need to use "set-executionpolicy RemoteSigned" to allow a local unsigned ps1 file to run.
And put the following as your scheduled command line, or inside your batch file....
powershell -command .ps1
In task scheduler, the account need to be set to the one who has admin permissions (or at least with powershell permission)
otherwise it cannot run properly.
When you do a Farm level backup, SharePoint tells SQL to do database dump to that location. Here are some things that have to
work in order for a farm backup to work:
1.Your Central Admin app pool account must have read/write access to the location of the backups.
2.Your SQL Service account must have read/write access to the location of the backups.
3.If you're running a farm backup from STSADM or Windows PowerShell, the account you're running it as must have read/write
access to the location of the backups
4.The location must be accessible from the SharePoint machine the backup is running on.
5.The location must be accessible from the SQL instance that SharePoint is trying to back up.
6.This is why all the examples are UNCs, \\server\share, and not local paths, C:\backups
7.Hope that helps
Go through following links which refers to write powershell script for Web applications,Site collections,Sites and lists or
libraries
http://technet.microsoft.com/en-us/library/ee428315.aspx

