SharePoint 2010 in the Gartner Magic Quadrant for ECM

Microsoft is placed in the Leaders Quadrant of Gartner Research (October 13, 2011), which looks at the enterprise content management market and how Gartner rates vendors and their packaged ECM products. According to Gartner “Changing delivery models, new value propositions, solution configurations and partner ecosystems make ECM relevant to every business.”.

Market Overview

ECM Today and Tomorrow

ECM has a rich history going back almost 30 years to the introduction of computer networks and document scanners to build the first document image processing applications. Functional elements such as the repository, scanning and capture tools, and workflow engines were often sourced from several vendors since full suites were rare. That changed during the late 1990s as IBM and others built out suites of technology to bring an integrated offering to bear. In the early 2000s, the impact of the Web hit ECM, and the concept of managing Web content and websites as user-friendly assets came under the ECM umbrella. By the mid 2000s, the market started experimenting with Microsoft's SharePoint 2003 as a low-end collaborative content management environment and those experiments got more serious by the time SharePoint 2007 was deployed. At the same time, other vendors were going through waves of acquisition — large vendors like EMC bought Documentum, IBM bought FileNet and then Oracle bought Stellent. Now, with four major vendors scrambling for ECM sales, the market really became a battleground post 2008. These top vendors control close to half the revenue of the ECM market today.

However, the future of ECM will not lie completely in the hands of these major players. Like in many IT markets, change is driven from the edges, by smaller vendors with innovative technology ideas not bound by the relative inflexibility of large corporations. These smaller vendors are often those in the Visionaries and Niche Players segments of the Magic Quadrant. Some of the forces of change on the future ECM market will come from these four key areas:

·         The Cloud. Public cloud deployments of ECM allow enterprises the flexibility of launching new content initiatives quickly with no upfront costs for servers, system integrators and (usually) software licenses. The enterprise pays a per-user fee, and perhaps a fee for the volume of documents stored, and can reduce the size of a deployment, when needed. Today, this is often best suited to ECM needs that are more basic, such as advanced file server use cases, where customization and integration are not needed.

·         Mobility. Given the clear demand for anywhere access and the rise of smartphones and tablets, ECM systems are deploying very functional clients for these devices in a post-PC era. In addition to simple use cases like repository access to documents, many vendors are developing interfaces for participation in process approvals and exception handling, camera-image (both still and video) and bar code inputs, case management system interfaces and, of course, the ability to maintain presence awareness of mobile users in an ECM system.

·         Analytics. Content analytics defines a family of technologies that processes content and the behavior of users in consuming content to derive answers to specific questions. Content types include text of all kinds, such as documents, blogs, news sites, customer conversations (both audio and text), and social network discussions. Analytic approaches include text analytics, rich media and speech analytics, and behavioral analytics. As enterprises bring more of their content under the control of an ECM tool, they want to gain more valuable insights from the usage patterns, the latent knowledge in the content as well as the social interactions that occur during the collaborative creation and dissemination of the content.

·         Big Content. Commonly accepted consumer file formats like audio and video have made their way into the enterprise and ECM systems are being leveraged to manage them in conjunction with many other file types. Enterprises seek to create a simpler view into a client or an issue which is agnostic of file type, and ECM tools are rising to the occasion. Big content refers both to the growth in size of repositories that organizations are able to achieve as file formats get larger, and also to the growth in diversity of content types. The world is getting bigger in terms of absolute quantities of content that enterprises must manage as well as diversity.

These new forces of change are having an effect on the solutions that vendors are building and they will spawn further new solutions. Gartner sees the market shifting toward four collections of technologies to suit them.

The Four Worlds of ECM

Changing delivery models, new value propositions, solution configurations and partner ecosystems make ECM relevant to every business. Understanding the four usage scenarios of ECM can help put enterprises on the path to success. Very few vendors have market-leading emphasis and ability in all four. Though many implementations span several scenarios, almost all will have to relate to content management as infrastructure.

The four major usage scenarios or "worlds" of ECM are as follows:

1. Transactional content management solutions focus on imaging, workflow/business process management (BPM), compliance/archives, records management and e-forms. Content contained within applications in this category tends to be static, rather than dynamic, though this may change as XML representations become more common. Processes tend to be stable, long-running and have a high volume of forms or documents that demand scalability, life cycle control and human approval, primarily for exceptions. An application interface is almost guaranteed. CCAs like those for invoice automation, case management frameworks, and other horizontal and vertical market templates and solutions are key considerations in vendor selection. Examples of solutions include offerings for customer communications management, processing of loan applications and electronic patient files.

Sample vendors: EMC, Hyland Software, IBM, OpenText, Perceptive Software, Saperion.

2. Social content management solutions focus on compound content object control and library services; document collaboration; workflow automation with alerts and calendaring; social content like wikis, blogs and videos; task tracking; browser or portal viewing; markup, annotation and version control. The focus is on systems of engagement — orchestrating high-value people involved in the project-based or long-running development and delivery of high-value documents, content or knowledge management, and optimizing the processes, interfaces and objectives that relate them through collaboration. Examples of these solutions include offerings for new drug discovery, new hire recruiting, onboarding and training, and construction project management.

Sample vendors: Alfresco, IBM, Microsoft, OpenText.

3. Online channel optimization solutions focus on Web channel sets of technology, including WCM, DAM, portals, electronic forms, Web and content analytics, social software, XML authoring, rich-media management, social content and collaboration, mobile device support and so on. The aim is to "idealize" them to serve as Web-delivered, context-aware engagement platforms for a variety of industry-focused solutions. Most important in delivering value will be a focus on relevancy and consequent measurable increases in the impact of the delivered experience. Examples of templates or solutions to engage customers more fully include online retail optimization, Web channel distributed claims processing, and constituency self-service in government.

Sample vendors: Adobe, OpenText, Oracle.

4. Content management as infrastructure solutions are increasingly being delivered by infrastructure vendors such as IBM, Oracle and Microsoft, which are embedding content management capabilities into their stacks. They are also increasingly becoming infrastructure platforms for supporting multiple CCAs. For example, when Microsoft SharePoint takes hold in an organization, users naturally begin exploring its suitability for a wider range of content management applications and its potential as a replacement for existing solutions. Essential considerations for this category include abilities to manage rich metadata, enable full life cycle control, allow easier migrations from other repositories, network drives or file servers, and to bring some analytic or business intelligence-like capability to unstructured data overall. Understanding how content relates to larger enterprise information management disciplines will also become critical.

Sample vendors: IBM, Microsoft, Oracle.

Market Definition/Description

ECM, defined as a strategy, can help enterprises take control of their content and, in so doing, boost effectiveness, encourage collaboration and make information easier to share.

ECM, defined as software, consists of a set of capabilities and/or applications for content life cycle management that interoperate, but that can also be sold and used separately.

The core components of an ECM suite and the updated weights for the Magic Quadrant scoring are described below.

Document management for check-in/check-out, version control, security and library services for business documents. Advanced capabilities such as compound document support and content replication score more highly than do basic library services.

Web content management (WCM) for controlling the content of a website through the use of specific management tools based on a core repository. This includes content creation functions, such as templating, workflow and change management, and content deployment functions that deliver prepackaged or on-demand content to Web servers. The minimum requirement is a formal partnership with a WCM provider. Native capabilities score more highly than partnerships. The relative complexities of provisioning content to users across intranet, extranet and Internet applications are also considered, as are the implications of analytics, social content and delivery models.

Several ECM vendors qualify for independent analysis of their WCM functionality (see "Magic Quadrant for Web Content Management").

Records management for long-term retention of content through automation and policies, ensuring legal, regulatory and industry compliance. The minimum requirement is an ability to enforce retention of critical business documents, based on a records retention schedule. Higher ratings are given for certified compliance with standards such as the Department of Defense (DoD) Directive 5015.2-STD, The National Archives (TNA), the Victorian Electronic Records Strategy (VERS) and Model Requirements for the Management of Electronic Records (MoReq2).

Several ECM vendors qualify for independent analysis of their records management functionality (see "MarketScope for Records Management").

Image-processing applications for capturing, transforming and managing images of paper documents. For this component we require a vendor to offer two things: (1) document capture (scanning hardware and software, optical and intelligent character recognition technologies, and form-processing technology) performed either using native capabilities or through a formal partnership with a third-party solution provider such as KnowledgeLake, Kofax, EMC (Captiva) and IBM (Datacap); (2) the ability to store images of scanned documents in the repository as "just another" content type in a folder, and to route them through an electronic process. Extra credit is granted for vertical or horizontal solutions delivered directly or through partners.

Several ECM vendors qualify for independent analysis of their image-processing functionality (see "Critical Capabilities for Composite Content Applications: Case Management").

Social content for document sharing, collaboration and knowledge management, and for supporting project teams. Blogs, wikis and support for other online interactions have been added. Social content — including video — is the fastest-growing category of new content in the enterprise. The name of this component has been changed from "document collaboration" to "social content" to reflect broader audience and content types.

Workflow/business process management (BPM) for supporting business processes, routing content, assigning work tasks and states, and creating audit trails. The minimum requirement is simple document review and approval workflow. Higher scores are given to vendors with graphical process builders, and both serial and parallel routing. Many vendors are drawing on stronger process capabilities to deliver frameworks or templates as CCAs.

Several ECM vendors qualify for independent analysis of their workflow/BPM functionality (see "Magic Quadrant for Business Process Management Suites").

Extended components can include one or more of the following: DAM, document composition, e-forms, search, content and Web analytics, email and information archiving, email management and packaged application integration.

Weighting changes from 2010 to 2011:

·         Document management: 15% = no change

·         WCM: 10% = no change

·         Records management: 15% in 2010, 10% in 2011 = -5% change

·         Image-processing applications: 15% = no change

·         Social content: 10% in 2010, 15% in 2015 = +5% change

·         Workflow/BPM: 25% = no change

·         Extended components: 10% = no change

See "Evaluating ECM Using the Magic Quadrant for Enterprise Content Management 2010."

Added

Software Innovation is a Scandinavian company specializing in ECM from a composite content application perspective.

Dropped

We have removed Autonomy because it is not actively promoting any products as ECM; rather, it focuses on meaning-based computing.

We have removed Xythos Software, a Blackboard company, because we have seen no client interest in its content management technology, nor have we seen any promotional efforts, since 2010.

You can enjoy reading the full Gartner Report here.

SharePoint 2010 Leads Gartner Magic Quadrant for Horizontal Portals for 2011

SharePoint 2010 Continues to Lead Gartner Magic Quadrant for Horizontal Portals for as per Gartner (October 2011 ), Gartner positions Microsoft in the Leaders Quadrant on the 2011 Magic Quadrant for Horizontal Portals based on an evaluation of completeness of vision and ability to execute.

SharePoint 2010 gets a better position in the magic quadrant compared to 2010 report (for 2010 report click here).

Microsoft SharePoint's sweeping growth in the portal market is largely a factor of its appeal to business users, rather than the portal's IT owners. Until recently, most portal providers appealed to enterprise IT leaders first, often emphasizing the security and compliance counterpoints to this new, flexible, yet seemingly risky, user-centricity.

Market Overview

Portal Customers and Vendors Focus on the User Experience

Gartner client discussions point to significantly altered portal emphases in recent years. Whereas portal initiatives often involve aggregating and delivering information sources and extending business applications and processes, new portal customers recognize that they must engage end users to ensure the success of their portal efforts. Organizations are finding that older portals do not (or never did) garner significant adoption and loyalty from end users, which has led to significant portal failure and stagnancy.

Consumerization is largely responsible for this trend, with Web consumers and information workers bringing greater expectations into the workplace. Consumers have far different expectations of their organizations' portals and websites than what they had only a few years ago. They expect portals to be highly personalized, engaging, social, accessible, mobile, easy-to-use and synchronized across a wide range of channels.

In the meantime, users and consumers have a choice: If they don't like what their business gives them to support their information and collaboration needs, they can easily use consumer mechanisms, ranging from Google Documents to Facebook to Drop Box. Although organizations can still compel their internal users toward their own portals for access to enterprise applications and processes, person-centric activities such as collaboration and knowledge management tend to split off into numerous silos. This trend raises risks for the enterprise, creating new and more widespread privacy and compliance concerns, as well as new levels of knowledge and information management chaos. Rather than using portal technology only to gather value for themselves, enterprise IT and business organizations must ensure valuable and engaging experiences for their end users, whether they're employees, partners, customers or citizens.

Clearly, IT organizations, their business leaders and their end users need platforms that offer value and provide a balance of control and flexibility. Portal vendors are quickly realizing that they must enable flexibility and manageability by business users. They must offer social experiences and mechanisms that enhance usability and ensure end-user adoption of their products. Meanwhile, enterprise portal vendors must bring the appropriate level of user appeal into a productive, reliable, extensible and secure portal environment.

The user experience trend also means that portal providers must rely less on consultants, system integrators (SIs) and designers to ensure an engaging and productive user experience. That is, they must provide a shorter path to a fruitful user experience out of the box.

"Portlets-R-Us": The Portlet Catalog Becomes the App Store

Portal customers and vendors seeking to respond more readily to business needs are also revisiting and relabeling fundamental portal concepts. To accommodate more business needs, respond to consumerization, delegate capability to the business, improve extensibility and interoperability with third-party providers, and cultivate developer and vendor ecosystems, many portal providers are building or reviving their portlet catalog capabilities. Some vendors are starting to refer to them as "App Stores." Now that consumers and developers alike have grasped the concept (largely through their smartphone and tablet experiences), the market seems ripe for the concept.

Portlet catalogs typically offer portal components, modules, skins, themes, templates and connectors that customers can easily plug into their portal frameworks to improve usability and design, or to offer industry- or application-specific capability. The portlet store concept is applicable to internal scenarios, where organizations want to provision certain capabilities that can be readily and safely invoked by their business users and departmental developers, as well as to external communities, which use the portlet marketplaces to share and sell their components to other organizations. Internal portal app stores can be used to enable IT organizations to deploy useful, compliant and secure portal components that site administrators and end users can then plug into their personal or group sites.

Vendors including IBM, Microsoft, Oracle, Liferay, Backbase, DotNetNuke and Drupal support the portlet store concept, and many are relabeling their efforts to align with consumer app store trends. Vendors are also supporting consumer-Web widget standards, including OpenSocial, to leverage widely available components, such as Google Gadgets.

The Portal Market Split: UXPs and Lean Portals

The horizontal portal market will serve as a foundation for emerging UXPs (see "The Emerging User Experience Platform"), which provide the integration of technologies used to deliver portals, mashups, rich Internet applications (RIAs), Ajax-enabled websites, Web content management (WCM) and mobile applications. This integration can take the form of a set of separate, yet integrated, products that can be delivered as a suite or as a single product. Early examples of UXPs are largely derived from traditional portal technology, and include Microsoft SharePoint, Oracle WebCenter and IBM's broadening WebSphere Portal, with its related collaboration and content management portfolio, which is evolving toward a more cohesive UXP.

Although a dozen years of evolution and consolidation in the portal market have brought us sophisticated and versatile products, they've also brought functional bloat and technical complexity. Many organizations want lean portals: simple, more cost-effective products that focus on the portal's primary proposition and provide a personalized point of access to relevant information, business processes and people. Lean portals rely on modern architectures and representational state transfer (REST)-oriented standards for interoperability, often bringing customers faster time to value, without violating software standards in adjacent spaces, such as content management and analytics. The tendency toward lean portals accompanies a desire for lower costs, so it's a space in which open-source providers are playing a more prominent role.

The portal market's bifurcation is opening opportunities for software and service providers on both sides of the rift. Backbase and edge IPK, which is new to this year's Magic Quadrant, qualify as lean-portal providers. Although Liferay is beginning to broaden and deepen its portal capability with a view toward UXP, most customers acquire it for its lean-portal qualities. Open-source products such as DotNetNuke and Drupal are also entering the market with a lean proposition. Salesforce.com enters this Magic Quadrant combining a lean proposition with a software as a service (SaaS) model, which is aimed at lowering costs, easing accessibility and ensuring adoption.

On the UXP side, although they didn't meet the criteria for this year's portal Magic Quadrant, vendors such Adobe and Cisco loom large as potential players in the emerging UXP market, entering via content management in Adobe's case and collaboration in Cisco's.

Market Definition/Description

Gartner defines a portal as "a Web software infrastructure that provides interaction with relevant information assets (for example, information/content, applications and business processes), knowledge assets and human assets by select targeted audiences, delivered in a highly personalized manner." Enterprise portals may face different audiences, including:

·         Business-to-employee (B2E)

·         Business-to-consumer (B2C)

·         Business partners (B2B)

Of course, the public-sector corollaries to these three high-level audience types are also considered applicable. A portal product is a packaged software application that is used to create and maintain enterprise portals. These products can be used to design vertical or horizontal portals:

·         Vertical portals focus on accessing specific applications or business functions.

·         Horizontal portals integrate and aggregate information from multiple cross-enterprise applications, as well as specific line-of-business tools and applications.

Inclusion And Exclusion Criteria

To be considered for the 2011 Magic Quadrant for Horizontal Portals, vendors must meet a combination of criteria. They need to provide technology supporting deployment in a variety of scenarios, including employee, customer/constituent-facing and partner portals.

The vendor must provide the following capabilities:

·         A container or framework and component model (i.e., "portlets" or a similar component model)

·         Security administration, including the ability to manage security rights and privileges by individual, group or role, such as single sign-on

·         The ability to integrate with a wide range of data sources, applications, content, and services via various mechanisms, such as enterprise service bus, REST, Really Simple Syndication, Web services, iFrames and screen-scraping

·         Personalization, including the ability to direct relevant content and information to individuals, groups and roles; change the content and behavior of page components, pages or page groups; and provide end-user customization (personalization may be driven by any number of static user-centric attributes, dynamic session-centric attributes, collaborative filtering or social relationships)

·         Content management, including the ability to create, organize and publish content in the context of the portal, as well as search and content aggregation

·         Business process management (BPM), including some means of providing or integrating with workflow and BPM tools or platforms

·         Support for multichannel and multidevice delivery and presentation

The vendor must provide sales and support for the portal product in at least two of the following five geographic regions: North America; Latin America; Europe, the Middle East and Africa; Japan; and the Asia/Pacific (APAC) region.

The vendor must support clients in more than one industry vertical.

The vendor must have achieved one of the following:

·         At least $4 million in annual portal-related product and service revenue as of 2010

·         An installed base of at least 100 enterprise customers

Added

DotNetNuke, Drupal, edge IPK and salesforce.com met the criteria for this year's Magic Quadrant for Horizontal Portals and have been added to this assessment.

(Note: Tibco Software did not respond to requests for supplemental information or to review the draft contents of this document. Therefore, Gartner's analysis is based on other credible sources, including public information, Tibco's website, more than five discussions with PortalBuilder customers, our day-to-day interaction with Tibco users and information provided to us for the 2010 edition of this research.)

Dropped

No vendors were dropped from this year's Magic Quadrant for Horizontal Portals.

(Note: To support this research, Gartner collected information from vendors on their offerings, organizations and strategies through an extensive request for information, as well as supplementary briefings. We also surveyed and interviewed portal customers, some of which were provided by the vendors and some of which we located on our own. We also used information and experience gathered in our numerous client inquiries and other customer interactions.)

Click here to Read the full report, enjoy it

Error:This page allows a limit of 200 controls, and that limit has been exceeded

I received the above error when extending an existing web application in SharePoint 2010.

Solution :
SharePoint be default limits the number of controls per page to 200 in the extended site web.config file, all what you have to do is:

1. Edit the web.config of your application (e.g: C:\Inetpub\wwwroot\wss\VirtualDirectories\80)
2. Search for configuration/SharePoint/SafeMode then change the MaxControls attribute to a suitable value higher than 200, I tried 500 it worked like charm.

New-SPConfigurationDatabase: The user does not exist or is not unique

New-SPConfigurationDatabase : The user does not exist or is not unique.At line:1 char:28+ New-SPConfigurationDatabase <<<< + CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase: SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], COMExce ption + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon figurationDatabaseHere are some details on my setup:
-SharePoint 2010 Ent.
-Windows w2k8 R2 Ent x64.
-Using SQL Server 2008 R2 x64-The local accounts I added to SQL Server both have the rights to create dbs (dbcreator and also sysadmin)-Windows Firewall is off (this probably isn't a factor)-I checked the version of Geneva Framework I have in assembly and it was 1.0.0.0. anyway, but I uninstalled this via Add/Remove, rebooted server, installed again, no luck.-At the farm credentials stage, I am using the following credentials: Name of Windows account I am using (eg Hany, but not ComputerName\AccountName), and the password to login.-When I installed SQL Server, I added the Administrator local account and my named local account but also with mixed auth and a password.-I am running a fully updated version of Windows Server. I haven't installed the other updates mentioned in various posts.
I faced this problem and I managed to solve it through the following steps:
· Make sure that your machine name is limited to 15 bit to be within the NetBIOS naming limits.
· Makes sure that the local windows accounts you are using to run the command as well as the perform the database access account is are using the following format:
MachineName\accountname, where the MachineName is your new machine name

Comparing Microsoft Dynamics CRM and SharePoint

In this post will try to state part of a session I delivered in early 2010, in one of the community events in Saudi Arabia, I will discuss the comparison between , SharePoint and Dynamics CRM
SharePoint and Microsoft Dynamics CRM - Similarities

• Both run as server applications on the Windows platform.
• Both are built on the .NET developer platform.
• Both use SQL Server as their database engine.
• Both are web applications that run on the Internet Information Server (IIS).

SharePoint and Microsoft Dynamics CRM– Differences

• Data model
  In SharePoint for example, users can add an item to a list, and upload documents to a document library. These lists and libraries are customizable. While a list is similar to a table in a database application, SharePoint cannot create relationships between lists (however, you can use lists as lookups for each other). Microsoft Dynamics CRM has explicit out of the box support for relational database management features. Its "entities" correspond to database tables, which have customizable "attributes" (columns), and it has a powerful set of features for creating relationships between out of the box entities, and custom entities you create.
• SharePoint Pages compared to CRM Forms
  With SharePoint, the primary user experience is through web pages. Customizers of a SharePoint site can use the built-in user interface to create custom pages using Web Parts, and SharePoint Designer can be used to create highly graphical custom pages. These web pages do not generally have any built-in data awareness, and can be created entirely independent of any SharePoint lists or libraries. Dynamics CRM does not provide out of the box support for a generic web page. Every Dynamics CRM entity has only one form that manages the user experience of working with the highly structured data contained within Dynamics CRM.
• Document management (Versioning, Approval, Source Control)
  SharePoint has powerful out of the box features designed for efficient and secure collaboration on shared documents, such as major and minor versions, content approval based on security role, and the ability to require check-outs before allowing edits. Dynamics CRM documents can be attached to an entity's records, but there is no support for versioning or any of the other document management features available in SharePoint.
• Query and Search
  Dynamics CRM provides powerful end-user querying tools that are tailored to the product's relational database strengths. For example, users can easily include columns from multiple related entities within a single result set, and can sort and filter based on values from related entities. With SharePoint, search is much less structured, and the experience is more similar to a Live or Google web search experience where a user can enter a search keyword in the search box, and the SharePoint search engine will potentially find every occurrence of that keyword in every list, library, page or document in an entire site collection. SharePoint enterprise search is less structured and much broader than Dynamics CRM search, and offers users the potential to search across SharePoint content (including document libraries, lists, blogs, and wikis) as well as network file shares, external web sites, other business applications (such as SAP), and even Dynamics CRM data, (if you configure the SharePoint Business Connectivity Service).
  

Jobs for SharePoint

• Document management and collaboration.
• Web sites and web content management.
• Reporting and dashboard applications.
• Enterprise portals and Enterprise search.

Jobs for Microsoft Dynamics CRM

• Marketing Management.

The Dynamics CRM is used by the marketing team to manage the entire marketing process; Dynamics CRM manages the entire marketing processes it helps in: marketing planning and budgeting, campaigns, marketing lists, marketing teams and marketing activities reporting…etc.

• Sales Management.

You can use Dynamics CRM for the management of your sales processes starting from very simple sales process to roughly saying very complex sales processes.

• Customer service

Such as case management, service scheduling, contract management, knowledge base.

• xRM (Any Relationship Management).

xRM is a business application framework that accelerates the development and delivery of enterprise-class, relational business applications. It the one of the amazing extensibility features of Microsoft Dynamics CRM, it moves you to a space where sky is the limit. xRM capabilities forged from customization, configuration and business process automation investments.

The Middle East SharePoint Conference 2010

Qatar hosts the Middle East SharePoint conference 2010, which will be held at the Four Seasons Hotel in Doha, Qatar from December 5-6, 2010. The Middle East event will be the biggest across the region for technology professionals to learn more about Microsoft® SharePoint® 2010, the business collaboration platform for the enterprise, the internet and related technologies.

I will be attending this event. I hope i see you all there.

To Register in the event click here

SharePoint 2010 Leads Gartner Magic Quadrant for Horizontal Portals

Microsoft SharePoint is a consideration in more Gartner portal inquiries — over 70% — than any other vendor.
Five vendors dominated portal selections during the latter part of 2009 and into 2010: Microsoft, IBM, Oracle, SAP and Liferay. Open-source Liferay has made the strongest move toward the forefront of portal decisions for Gartner's customers. IBM has retained its position as a strategic provider of portals for enterprises with complex and widespread needs. Oracle's acquisitions have brought it an enormous portal installed base and, accordingly, enormous attention on the direction of its various portal products.

Open source for portals is hitting its stride. During this prolonged period of economic uncertainty, many companies first looked at open-source products from Liferay, Red Hat JBoss and others as a pure cost consideration. However, these products are also winning deals as they prove themselves at larger organizations. They're relatively easy to acquire, test and implement; their open architectures strike a chord for interoperability and vendor independence; and they provide basic portal functions without the bulk of the megavendors' offerings. Products that come with enterprise content management (ECM), collaboration or social platforms can more easily conflict with other installed products.

The field of viable portal vendors has narrowed considerably, dropping from more than 50 vendors in 2003 to fewer than a dozen in 2010. However, the consolidation of traditional portal vendors doesn't necessarily mean the commoditization of the market. In light of pressing business needs to improve the user experience across channels, and amidst the innovations of Web 2.0 and the cloud, making the right portal choice is more important than ever. The major technology shifts toward Web 2.0, the cloud and business versus the IT influence are galvanizing the portal market. Portals provide a single, personalized point of access to relevant information, processes and people. They appeal to business leaders as a means to improve employee productivity and collaboration, extend business processes and applications to broader audiences, improve business visibility and responsiveness, engage and serve customers, and improve relationships and efficiency among value chain partners. More importantly than ever, portals appeal to end users overwrought with too many systems to log into and too much information. Enterprise portals unify the user experience, and provide relevancy and context across disparate applications. They provide a unified user experience by spanning across on-premises and cloud boundaries, as well as business and social boundaries. IT organizations need them more than ever to pull together and aggregate disparate information, exert control and ensure compliance, and scale their ability to agilely deliver these applications to the business and users. Looking forward, the horizontal portal market will serve as an important foundation for the emerging user experience platform (UXP). Organizations are focusing on business-level issues, requiring better engagement of users across a widening range of devices and channels, and new vendors are entering the market with alternative approaches to accomplishing the portal proposition. As portals, user interfaces, and user interaction technologies and practices have proliferated, they have evolved into disconnected stovepipes. Portal products, mashup tools, rich Internet application (RIA) tools, Ajax solutions, Web content management and mobile application development tools all target their respective platforms effectively, but they require enterprise developers to create separate user interaction models and code bases — with few, if any, cross-platform capabilities. Vendors have started to address enterprise concerns with the convergence of these related technologies. The UXP provides integration of technologies used to deliver portals, mashups, RIAs, Ajax-enabled websites, Web content management and mobile applications. This integration can take the form of a set of separate, yet integrated, products (that may or may not be delivered as a suite) or a single product. Early examples of the UXP are largely derived from portal technology, and include Microsoft SharePoint, Oracle WebCenter along with Universal Content Management (UCM), and IBM's broadening WebSphere Portal with its related collaboration and content management portfolio, which is developing toward a more cohesive user experience platform. The importance of portals and the future of UXP are not lost on vendors; enterprise vendors are using portals to promote their most-sweeping and most-critical agendas. Many of the vendors are using the portal to promote a far broader and deeper agenda, whether it's their developer platforms and tools, content management capabilities, databases and middleware, or enterprise applications. As an inherently cloud-friendly aspect of middleware, portals are also a fundamental vehicle for transitioning customers to the cloud. The portal choice is, therefore, critical to ensure that organizations can accomplish their business goals, while ensuring vendor independence and agility. Organizations tend to make portal decisions based on a wide range of factors, including functionality, familiarity, price, interoperability, usability, momentum among customers and the IT ecosystem at large. As portals have evolved, basic portal functions, such as user management, personalization, content management and integration, have been extended and enhanced, and new capabilities, such as social computing, analytics and business process management, have been added to respond to subsequent customer demands.

Click here to Read the full, report, Enjoy it

Walkthrough SharePoint 2007 upgrade to SharePoint 2010 Project Part 2 of 2

In this part, I will explain the MOSS 2007 Site collection upgrade to SharePoint 2010.
1. Use the Stsadm to perform the pre upgrade check on the MOSS 2007 environment, this option is available in MOSS 2007 SP2.
Run the following command
Stsadm –o PreUpgradeCheck
, check the resulting reports to identify the following:
a. Information & Configuration
i. Content Sources & Start addresses
ii. Farm & Search Topology
iii. Servers
iv. Upgrade Types
v. AAMs, Large Lists & Libraries
b. Important Issues and Dependencies
i. Site Definition (referenced & missing)
ii. Installed Language Pack
iii. Features (referenced & missing)
iv. Custom List Views & Custom Field Types, Web.Config entries

2. I used the “attach content database” migration option. So you need to take a backup of all the content databases in your MOSS 2007 server farm.
3. Restore the content databases to your new SharePoint 2010 server farm. Using the simple SQL server attach database option.
4. You can also use a backup/ restore database option.
5. Make sure that you have the same language pack on MOSS 2007 and SharePoint 2010.
6. Create a new empty SharePoint 2010 web application on the new SharePoint farm. You can do this from SharePoint 2010 central administration
7. Perform the “attach content database” command as shown in the below figure. You can do this from the SharePoint 2010 Management power shell

STSADM -o addcontentdb -url http://itweb.contoso.com/ -databasename SP_2007_Content -databaseserver Demo2010

8. Change the site collection owner of the new restored site collection to a suitable user account, as well as the secondary site collection owner. You can do this from the SharePoint 2010 Management power shell using the below command line
stsadm.exe -o siteowner -url http://SiteURL:Port -ownerlogin doamin\username -secondownerlogin domain\secondusername

9. Merge the compiled source code to the new virtual directory of your web application. You can find details about this source code and its upgrade in the following part 1 of this post:
http://hanymahmoud.blogspot.com/2010/05/moss-2007-upgrade-to-sharepoint-project.html

10. Finally perform the visual upgrade from the site sittings menu (as shown in the below figure) or using the SharePoint 2010 Management power shell. I recommend taking a full backup of you site collection before performing visual upgrade to be able to recover in case of this step encounters any errors.

Walkthrough SharePoint 2007 upgrade to SharePoint 2010 Project Part 1 of 2

I have a project of migrating a solution on top of MOSS 2007 to SharePoint 2010. The project is an intranet portal with 12 applications on top of MOSS 2007. The applications are 3 tiers (DLL,BLL, UI) the UI layer contains a set of web parts controlled by the BLL which in turn accesses the database through the DLL.
1. Upgrade you solution to be on top of MOSS 2007 SP2 and WSS 3.2 SP2.
2. Compile the source code for the solution using VS 2010 and choose the .Net framework 3.5 as your target framework.
3. Replace references to all Microsoft.SharePoint assemblies with the new SharePoint assemblies you may use the below this article to solve the bugs resulted from changing references
http://technet.microsoft.com/en-us/library/cc262967.aspx

4. You can find a list of assemblies and name spaces changes between MOSS 2007 and SharePoint 2010 in the below link
http://techtrainingnotes.blogspot.com/2010/01/sharepoint-2010-namespace-and-assembly.html

5. You may need to add reference to SharePoint assemblies from "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI" such as "microsoft.sharepoint.portal.dll", if you cannot find them in global assembly cache.
I will complete this article in part 2 soon , once I have time to write it.

I in an Interview with some of the Microsoft Communities Leads in Riyadh Saudi Arabia

We recorded this session during the academic launch of VS.Net 2010

enjoy it:
http://www.blogger.com/post-create.g?blogID=29977735

SharePoint and Dynamics CRM the Right Tool for the Job

I will be delivering a session on SharePoint and Dynamics CRM the Right Tool for the Job in Riyadh SharePoint User Group Event - April 2010. In this session I will focus on the comparison between SharePoint and CRM and I will give high level overview about CRM with a live demo on how we can use both technologies together to get the best out of our business. The full event agenda can be found at the this link http://rsugapril10.eventbrite.com

What is new In SharePoint 2010- Egyptian Engineering Association in Saudi Arabia (http://www.eea-ksa.org)

this is the bi-weekly event of the association (http://www.eea-ksa.org) for the IT community in Saudi Arabia, I will be delivering my second session in the main building of the engineering association in Murabaa on Monday 5th April at 9PM to 11PM. I deliver a session about what is new in SharePoint 2010. I will be looking forward to see you all there.

SharePoint 2010 Content Management Interoperability Services (CMIS) Support

SharePoint 2010 will support CMIS once released
A custom solution available now to access external repositories from SharePoint using CMIS
http://code.msdn.microsoft.com/spextcontent

Content Management Interoperability Services (CMIS)

Content Management Interoperability Services (CMIS) Overview
•Use of Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors
•Oct ’06: Microsoft ,EMC, IBM joined forces to propose first Web Services-based standard for exchanging content between ECM systems
•Additional collaborators: Oracle, Alfresco, OpenText, and SAP
• Sep ‘08: Registered for public comment with OASIS(Organization for the Advancement of Structured Information Standards) closed on 22 Dec 2009
•Includes: Common Domain Model (Data Model, Capabilities) and Bindings (SOAP for System to System, REST(Representational State Transfer) for System to Application)
the blow figure shows CMIS architecture (Source EMC)

Guiding Principles for the Development of the CMIS

•Work over existing repositories enabling customers to build and leverage applications against multiple repositories
•Platform and language agnostic
•De-couple web services and content from the content management repository, enabling customers to manage content independently
•Support composite application development and mash-ups by the business or IT analyst
•Provide common web services and Web 2.0 interfaces to dramatically simplify application development
•Use of Widely Adapted Standard Protocols (SOAP and REST)
•Help Customers to Take their ECM Investments to Web 2.0 Era

New SharePoint 2010 ECM Capabilities and Extensibility

Riyadh SharePoint User Group Event; the Event will have a lot of sessions about SharePoint 2010. I will be delivering one session about new SharePoint 2010 ECM Capabilities and Extensibility. the session will take place in Microsoft Innovation Center in Yammah University in 18 March, 2010, at 2:30PM

Walkthrough Integrating SharePoint 2007 with CRM 4.0 using the List Web Part for Microsoft Dynamics CRM 4.0

1. Download the list web part for CRM 4.0 from this link
http://www.microsoft.com/downloads/details.aspx?FamilyID=3B6EB884-EC15-4288-A2A3-D0B47E057458&displaylang=en
2. Install The List Web Part for Microsoft Dynamics CRM 4.0 on the front end SharePoint web servers for the entire SharePoint farm.
3. In the installation wizard Click Next.
4. Click the I Accept button.
5. Click Next
6. Click the Close button on the Setup Completed page.
7. Create a web part page to host the CRM list web part.
8. Click Add a Web Part.
9. In the Add Web Parts dialog, click List Web Part for Microsoft Dynamics CRM 4.0 check box and then click the Add button. The Web Part instance is added to the page.
10. In the edit menu for the Web Part, select the Modify Shared Web Part menu item. The edit pane is displayed on the right side of the page.
11. In the CRM Server URL text box, type (http://CRMServer:Port) and click the Go button.
12. Choose the Organization that you want to connect to.
13. Select the Record Type as Opportunities, Contacts, Accounts, or Leads …etc.
14. select View as Open
15. Click the OK button. The Web Part now ready to display the selected object type.
16. Click Exit Edit Mode on the upper-right side of the page.

What is new in SharePoint 2010 ECM Capabilities

I will start by giving overview about SharePoint’s big picture, and then I will state the SharePoint ECM offerings

The SharePoint 2010 server is most powerful Business Collaboration Platform for the Enterprise and the Web

The old Windows SharePoint Services 3.0 is now rebranded to be SharePoint Foundation 2010, it contains the core SharePoint services as shown in the above figure.

The full SharePoint Server big picture is show in the above figure , I will focus on the ECM part of SharePoint Server in this postThe SharePoint ECM stack starting form the core ECM functionality ending up to different types of clients is shown in the above figure.

SharePoint 2010 ECM Capabilities can be summarized in the following features:
•Highly Scalable Document Libraries Sized Millions of documents
•Enhanced Office Integration
•Record Management
In Place Record Management
Separate Records Repository
•Rich Media Management
Digital Media Streaming (Images, Video, Audio)
•More Scalable Architecture
•Managed Meta Data Services provides
Meta data driven navigation with custom Filters
Meta data driven Search
Easy to use user Interaction with metadata such as (custome column of type metadata and suggestions)
Mange Metadata Across the Farms, Site Collections
•Content Organizer Engine
•Highly Scalable Document Libraries Sized Millions of documents
•Record Management
In Place Record Management
Separate Records Repository
•More Scalable Architecture
Integration with – FAST! lead to Better Search Scalability Redundant for Indexing – Integrated no longer single point of failure
•Office Web Apps from browser without having to have the office clinet inistalled on the client machine
•Offline with SharePoint Workspace
•Claims based authentication