The document provides an architectural overview of Microsoft Dynamics CRM 2011, detailing its design goals, metadata models, and security features. It discusses the extensibility model, highlighting the platform's customization capabilities, integration with .NET frameworks, and various application components. Additionally, it explains the roles, privileges, and access rights management within the CRM system, emphasizing a role-based security model.

1. ARCHITECTURE OVERVIEW OF BUSINESS SYSTEMS: MS DYNAMICS CRM
Dmytro Golodiuk / Corporate IT – Business applications / Architecture committee
Nov 16, 2014

2. ARCHITECTURE VIEWPOINTS
by Rozanski & Woods
Context Viewpoint
Functional
Viewpoint
Informational
Viewpoint
Development
Viewpoint
Deployment
Viewpoint
Concurrency
Viewpoint
Operational
Viewpoint
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 2

3. WHAT IS MS DYNAMICS CRM 2011?
The End-to-End Solution
Marketing
Effectiveness
Extended CRM
Applications
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 3

4. MICROSOFT CRM DESIGN GOALS
Provide low total cost of ownership (TCO)
Provide low-cost product customization
Scale up and out to hosted environments
Scale down to a single user desktop
Separate, but equal, application and platform tiers
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 4

5. THE METADATA AND DATA MODELS
In Microsoft Dynamics CRM
Metadata object Description
Entity An entity is a container for data, similar to a table in a traditional database. Each entity contains a
set of attributes. For Microsoft Dynamics CRM, there are a set of entities that exist when you first
install. Some of these are customizable. In addition, you can create custom entities to contain
business data.
Attribute An attribute is a container for a piece of data in an entity. Microsoft Dynamics CRM supports a
wide variety of attribute types.
Relationship A relationship defines an association between two entities: one-to-many, many-to-one, many-to-many,
and self-referential.
Option Set An option set defines a set of options provided for a picklist. Several picklist attributes may use a
global option set so that the options they provide are always the same and can be maintained in
one location.
Option An option is one of the values available in an option set. Each option in an option set has a
unique integer value and an associated set of localized labels.
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 5

6. THE METADATA AND DATA MODELS
Out of Box Entities
Administration and Security Entities
(Organization, Business Unit, User, Team,
Privilege, Role, Field Security)
Activity Feeds Entities
Customer Entities (Account, Contact)
Business Management Entities
Service Entities (Contract, Incident,
Knowledge Base)
Sales Entities (Lead, Opportunity,
Competitor, Quote, Order, Invoice)
Marketing Entities (Campaign, List)
Activity Entities
Goal Management Entities
Product Catalog Entities
Sales Literature Entities
Schedule and Appointment Entities
Template Entities
Annotation (Note) Entity
UserQuery (Saved View) Entity
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 6

7. THE METADATA AND DATA MODELS
Audit
Entity
Data
Changes
Detect
Duplicate
Data
Delete
Data in
Bulk
Import
Data
Manage Your Data
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 7

8. THE SECURITY MODEL
Business
Unit
Security
Role
Privilege
(access
rights)
Access
Level
F(BU, SR, P, AL)
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 8

9. THE SECURITY MODEL
 Provide users with the access only to
the appropriate levels of information
that is required to do their jobs.
 Categorize users by role and restrict
access based on those roles.
 Support data sharing so that users and
teams can be granted access to
records that they do not own for a
specified collaborative effort.
 Prevent a user's access to records the
user does not own or share.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
9
Goals

10. THE SECURITY MODEL
Roles
Privileges
Create
Read
Write
Delete
Append
Append To
Assign
Share
Access
Levels
Global  Organization
Deep  Parent: Child BU
Local  BU
Basic  User
None  No access
11/20/2014 Subject 10
Role-based security

11. THE SECURITY MODEL
Record-Based Security
Access
Rights
Sharing
Records
Assigning
Records
Access Rights
Read
Write
Assign
Append
Append To
Share
Delete
11/20/2014 Subject 11

12. THE SECURITY MODEL
Field-level security
Which Security Roles Allow You to See Secured Fields?
How Do Secured Fields Behave for Retrieve and RetrieveMultiple?
When a Secured Attribute is in the Column Set
When a Secured Attribute is in the Filter Condition
When Grouping on Secured Attributes
When Ordering on Secured Attributes
How Do Secured Fields Behave for Create or Update?
How Do Secured Fields Behave When Records are Shared?
How Do Secured Fields Behave for Filtered Views?
How Do Secured Fields Behave for Offline Synchronization?
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 12

13. THE EXTENSIBILITY MODEL
Dynamics CRM Puts Innovation at the Center
Personalize
TAILOR CRM TO YOUR UNIQUE
NEEDS
Connect
SEAMLESSLY INTEGRATE CRM
TO EXISTING SYSTEMS
Build
RAPIDLY BUILD OTHER LOB
APPLICATIONS
11/20/2014 Subject 13

14. GENERAL MULTY LAYER ARCHITECTURE
Presentation Layer
UI Components UI Process Components
Service Layer
Interfaces Message Types
Business Layer
Application Façade
Business Workflow
Business
Components
Business Entities
Data Layer
Data Access Components Data Helpers / Utilities Service Agents
Cross
Cutting
Security
Operational
Management
Communication
…
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 14

15. CRM 2011 ARCHITECTURE DRILL DOWN
Reporting
(Dashboards,
Charts, Excel,
FetchXML and SRS)
Integrated
Applications
Web Outlook Mobile Tablet
Extensible Application: Form and
client side events, Ribbon, Sitemap,
Web Resources, JS libraries…
Web Services
Front End
Integration
Pre-Event Plug-ins
(.NET Assemblies)
Post-Event Plug-ins
(.NET Assemblies)
Custom Workflow
(.NET Assemblies)
Backend
Integration
Server-to-
Server
Synchronous and Asynchronous Business Logic
Business Entity Components
Data Access Components
Data Access Platform
Metadata Data
Filtered SQL Views
Workflow
Security
11/20/2014 Subject 15

16. THE EXTENSIBILITY MODEL
CRM / xRM Developer Platform
Rapid Development
.NET 4 & WF4
Solution Packaging
Strong types & LINQ
Visualizations
Rich Platform Services
Web Services - WCF / REST / OData
Transaction Support
SharePoint, Office
Claims Authentication
Cloud
Custom code on Server
Sandbox with external calls
Azure Integration
Global Markets
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 16

17. THE EXTENSIBILITY MODEL
What is the .NET Framework?
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 17

18. THE EXTENSIBILITY MODEL
.NET Framework: Objectives
Consistent object-oriented
programming environment
Code-execution environment
• Minimize software deployment and
versioning conflicts
• Safe code execution
• Elimination the performance
problems of scripted or interpreted
environments
Consistency across widely
varying types of applications
(such as Windows-based
applications and Web-based
applications)
.NET-based code integration
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 18

19. THE EXTENSIBILITY MODEL
.NET Framework Architecture
Visual Studio 2012+
ASP.NET (Web Form, MVC,
Web Page, SPA)
Windows
Store Apps
Base Class
Library
WPF
Languages
(C#, VB.NET,
etc.)
Windows
Desktop Apps
(Windows
Forms)
Silverlight
Dynamics
Language
Runtime
ASO.NET
LINQ
Managed
Extensibility
Framework
Entity
Framework
Parallel
Extension
Portable
Class Library
WCF
Signair
Portable
Class Library
ASP.NET
Web API
WF
WinRT
Common Language Runtime
Operating System
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 19

20. THE EXTENSIBILITY MODEL
Common
Language
Runtime
This acts as the
execution engine for the
.NET Framework. All
.NET programs
executes under the
supervision of CLR.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
20
Components of .NET Framework 4.5 Architecture

21. THE EXTENSIBILITY MODEL
Base
Class
Library
This is a library of
functionalities which are
available to all languages
using the .NET
Framework. It consists of
classes, interfaces of
reusable types that
integrates with CLR
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
21
Components of .NET Framework 4.5 Architecture

22. THE EXTENSIBILITY MODEL
Portable
Class
Library
This is a library of
functionalities which are
available to all languages
using the .NET
Framework. It consists of
classes, interfaces of
reusable types that
integrates with CLR
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
22
Components of .NET Framework 4.5 Architecture

23. THE EXTENSIBILITY MODEL
Managed
Extensibility
Framework
(MEF)
MEF is a library for
creating lightweight,
extensible applications. It
allows application
developers to discover
and use extensions with
no configuration required.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
23
Components of .NET Framework 4.5 Architecture

24. THE EXTENSIBILITY MODEL
Dynamic
Language
Runtime
This provides the
runtime environment for
dynamic languages like
python etc. for
executing under the full
control of CLR.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
24
Components of .NET Framework 4.5 Architecture

25. THE EXTENSIBILITY MODEL
WinRT
WinRT or Windows Runtime APIs
provides the user interface
elements for building Windows
Store apps, and provides access
to Windows 8 or Windows RT OS
features. WinRT supports
development in C and other
managed languages C# and
VB.NET, as well as JavaScript
and TypeScript.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
25
Components of .NET Framework 4.5 Architecture

26. THE EXTENSIBILITY MODEL
Asp.Net
This is used to build rich
internet based web
application.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
26
Components of .NET Framework 4.5 Architecture

27. THE EXTENSIBILITY MODEL
Windows
Store Apps
(Metro
Style Apps)
A Windows Store app is a
new type of application
that runs on Windows 8
devices and can take
advantage of new WinRT
APIs. These can only be
distributed in the
Windows 8 store.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
27
Components of .NET Framework 4.5 Architecture

28. THE EXTENSIBILITY MODEL
Desktop
Apps
(Windows
Forms)
A Windows Desktop app is
traditional Windows Forms
application with a new name.
Software developed for Windows
XP, Windows Vista and Windows
7 will be categorized as a
Windows Desktop app when
running in Windows 8. Examples
of Windows Desktop apps are
Microsoft Office families products,
notepad etc.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
28
Components of .NET Framework 4.5 Architecture

29. THE EXTENSIBILITY MODEL
WPF
WPF is used to create
applications with a rich user
experience. It includes
application UI, 2D graphics, 3D
graphics and multimedia. It
takes advantage of hardware
acceleration of modern graphic
cards. WPF makes the UI
faster, scalable and resolution
independent.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
29
Components of .NET Framework 4.5 Architecture

30. THE EXTENSIBILITY MODEL
Silver
Light
This is a cross-browser
web based technology
which allows designers
and developers to deliver
Rich Internet Applications
(RIA) embedded in Web
pages.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
30
Components of .NET Framework 4.5 Architecture

31. THE EXTENSIBILITY MODEL
Ado.Net
This is used to create
Data Access Layer to
query and manipulate
data from underlying
data source like SQL
Server, Oracle, and
DB2 etc.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
31
Components of .NET Framework 4.5 Architecture

32. THE EXTENSIBILITY MODEL
LINQ
This allows you to query the
data from the various data
sources (like SQL databases,
XML documents, Ado.Net
Datasets, Various Web
services and any other objects
such as Collections, Generics
etc.) using a SQL Query like
syntax with .Net framework
languages like C# and VB.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
32
Components of .NET Framework 4.5 Architecture

33. THE EXTENSIBILITY MODEL
Entity
Framework
This is used to query
and store data into to
the relational databases
(like SQL Server,
Oracle, DB2 etc.) in
ORM fashion.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
33
Components of .NET Framework 4.5 Architecture

34. THE EXTENSIBILITY MODEL
Parallel
Extension
This allows you to
distribute your work
code across multiple
processors to take
advantage of the
hardware.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
34
Components of .NET Framework 4.5 Architecture

35. THE EXTENSIBILITY MODEL
WCF
This is used for building
and developing services
based on WS-*
standards.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
35
Components of .NET Framework 4.5 Architecture

36. THE EXTENSIBILITY MODEL
Asp.Net
WebAPI
Asp.Net Web API is a
framework for building
HTTP services that can
be consume by a broad
range of clients including
browsers, mobiles, iphone
and tablets.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
36
Components of .NET Framework 4.5 Architecture

37. THE EXTENSIBILITY MODEL
SignalR
ASP.NET SignalR is a library that
simplifies the process of adding
real-time web functionality to
applications. Real-time web
functionality is the ability to have
server code push content to
connected clients instantly as it
becomes available, rather than
having the server wait for a client
to request new data.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
37
Components of .NET Framework 4.5 Architecture

38. THE EXTENSIBILITY MODEL
WF
This is used to build
process oriented
business workflow and
rules engine.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
38
Components of .NET Framework 4.5 Architecture

39. THE EXTENSIBILITY MODEL
Visual
Studio
2012
The Visual Studio IDE offers a
set of tools that help you to
write and modify the code for
your programs, and also
detect and correct errors in
your programs. Using Visual
Studio 2012 you can build
Windows Store apps, desktop
apps, mobile apps, ASP.NET
web apps, and web services.
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
39
Components of .NET Framework 4.5 Architecture

40. THE EXTENSIBILITY MODEL
Streamlined API with
a focused set of
methods
Use of standard .NET
Types in most cases
Fast processing
through binary
serialization
Improved
performance, security,
testability, etc.
Benefits
WCF Web Services
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 40

41. THE EXTENSIBILITY MODEL
Interoperability via Web Services
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 41

42. THE EXTENSIBILITY MODEL
Windows Workflow Foundation
Durable
timers
Benefits
Visualizing
user
process
Better
collaboration
between
technical and
non-technical
people
Comprehensive
technology
stack
Reusability and
integrations
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 42

43. THE EXTENSIBILITY MODEL
Supported Extensions (SE)
Using MS
Dynamics
Web App.
Customizations Using the
Microsoft Dynamics CRM SDK
Plugins Processes
Form
Scripting
Reporting
Services
Filtered
Views
with
external
apps
Ribbon
Customi
zation
ISV
Config.
(depreca
ted)
Unsupported Customizations (UC)
Extensions for Microsoft Dynamics CRM
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 43

44. THE EXTENSIBILITY MODEL
SE | Customizations Using the Microsoft Dynamics CRM SDK
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 44

45. THE EXTENSIBILITY MODEL
SE | Customizations Using the Microsoft Dynamics CRM SDK
Discovery
Service
Organization
Data Service
Organization
Service
Deployment
Service
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 45

46. THE EXTENSIBILITY MODEL
An extension mechanism
for custom platform-based
business logic
Support an event handler interface
that is based on a pipeline
execution model
Improved
event
processing
subsystem
Event
framework
API
Backwards
compatibility
Synchronous
and
asynchronous
execution
SE | SDK | Plug-ins
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 46

47. THE EXTENSIBILITY MODEL
SE | SDK | Plug-ins: Architecture and Related Components
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 47

48. THE EXTENSIBILITY MODEL
SE | SDK | Plugins: Pipeline Stages
Event Stage name Stage number Description
Pre-Event Pre-validation 10 Stage in the pipeline for plug-ins that are to execute before the main system operation.
Plug-ins registered in this stage may execute outside the database transaction.
Pre-Event Pre-operation 20 Stage in the pipeline for plug-ins that are to execute before the main system operation.
Plug-ins registered in this stage are executed within the database transaction.
Platform
Core
Operation
MainOperation 30 In-transaction main operation of the system, such as create, update, delete, and so on.
No custom plug-ins can be registered in this stage. For internal use only.
Post-Event Post-operation 40 Stage in the pipeline for plug-ins which are to execute after the main operation. Plug-ins
registered in this stage are executed within the database transaction.
Post-Event Post-operation
(Deprecated)
50 Stage in the pipeline for plug-ins which are to execute after the main operation. Plug-ins
registered in this stage may execute outside the database transaction. This stage only
supports Microsoft Dynamics CRM 4.0 based plug-ins.
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 48

49. THE EXTENSIBILITY MODEL
Process
Workflow
Customization
Custom Workflow
Activities
(all deployments)
System.Activities
(System.Workflow.Activities)
XAML (Declarative)
Workflows
(on-premises
deployments only)
Dialog
Customization
Custom Workflow
Activities
(all deployments)
System.Activities
(System.Workflow.Activities)
SE | SDK | Processes (formerly Workflows)
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 49

50. THE EXTENSIBILITY MODEL
SE | SDK | Processes vs Dialogs
Workflows Dialogs
Can be either started by a user or can be automated. Must be started by a user.
Are asynchronous processes, and do not require user
input to run to completion. These processes run in the
background.
Are synchronous processes, and require user input to run
to completion. When you run these processes, a wizard-like
interface is presented to you so you can make
appropriate selections to run the processes.
The entity that stores the details about a running workflow
is AsyncOperation.
The entity that stores information generated by a running
dialog is the ProcessSession (dialog session) entity.
Both Windows Workflow Foundation 4 and Windows
Workflow Foundation 3.5 custom activities are supported.
Only Windows Workflow Foundation 4 custom activities
are supported.
Triggers are supported for workflows. For a list of
supported triggers, see Supported Types, Triggers, and
Entities for Processes (Workflows and Dialogs).
Triggers are not supported for dialogs.
Workflows that are created or updated outside of
Microsoft Dynamics CRM by creating or updating the
underlying XAML file are supported in Microsoft
Dynamics CRM. For information about these custom
XAML workflows, see Custom XAML Workflows for
Microsoft Dynamics CRM 2011.
Dialogs that are created or updated outside of Microsoft
Dynamics CRM by creating or updating the underlying
XAML file are not supported in Microsoft Dynamics CRM.
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 50

51. THE EXTENSIBILITY MODEL
SE | SDK | Process Architecture Diagram
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 51

52. THE EXTENSIBILITY MODEL
SE | SDK | Process Life Cycle: Workflow
Create WF in Draft state, Activation WF
• Subscription to specific events
• Event is triggered
• Add operation to the async service queue manager  WF exec. job
• Awaits execution in the queue in the Ready state
Creation of WF instance by WWF run-time engine
• Change state from Ready to Locked
Update the asynchronous operation on each transition
• Set Suspended state
• Remove from memory
• Satisfying Suspended state conditions
Set state Completed when all workflow activities have
completed successfully
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 52

53. THE EXTENSIBILITY MODEL
SE | SDK | Process Life Cycle: Dialog
Create dialog in Draft state,
Activation of Dialog
Start dialog from its primary entity
or by URL
• Create process (dialog) session instance
Complete running the dialog:
Complete or Incomplete state
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 53

54. THE EXTENSIBILITY MODEL
SE | SDK | Form Scripting
Xrm.Page Object
Model
Data Access Using
JavaScript
Use an IFRAME
and Web Resource
Controls on a Form
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 54

55. THE EXTENSIBILITY MODEL
SE | SDK | Form Scripting | Xrm.Page Object Model
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 55

56. THE EXTENSIBILITY MODEL
SE | SDK | Form Scripting | Data Access Using JavaScript
Task Web Service
Create, Retrieve, Update and Delete records. REST Endpoint
Associate and Disassociate records REST Endpoint
Assign Records SOAP Endpoint
Retrieve Metadata SOAP Endpoint
Execute Messages SOAP Endpoint
OrgOarngiaznaitzioanti oDna Stae Srveicrveice
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 56

57. THE EXTENSIBILITY MODEL
SE | SDK | Form Scripting | Use an IFRAME and Web
Resource Controls on a Form
Image (JPG,
PNG, GIF,
ICO) Web
Resources
Web Page (HTML)
Web Resources
Silverlight
(XAP) Web
Resources
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 57

58. THE EXTENSIBILITY MODEL
SE | SDK | Filtered Views
SELECT TOP 1000 AccountNumber, Name FROM [zeppelin_MSCRM].[dbo].[AccountBase]
SELECT TOP 1000 AccountNumber, Name FROM [zeppelin_MSCRM].[dbo].[Account]
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 58

59. THE EXTENSIBILITY MODEL
SE | SDK | Filtered Views
SELECT TOP 1000 AccountNumber, Name FROM [zeppelin_MSCRM].[dbo].[FilteredAccount]
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 59

60. THE EXTENSIBILITY MODEL
Reporting
Advanced
Find
SSRS
SQL-based
Filtered
Views
Only for on-premise
Fetch-based
FetchXml
RDL
sandboxing
Custom
code
SE | SDK | Reporting
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 60

61. THE EXTENSIBILITY MODEL
Unsupported Customization
Modifications to any files in
the wwwroot
Modifications to MS CRM
site
Use of client certificates
Modifications to the physical
schema of the database
Data changes in the
database using SQL
commands or any
technology other than those
described in the Microsoft
Dynamics CRM SDK.
Reuse of any MS Dynamics
CRM JavaScript code,
including ribbon commands
Use of custom HttpModules
to inject HTML/DHTML into
the Microsoft
Dynamics CRM Forms.
Silverlight Application
Library Caching
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 61

62. PRODUCTION FOCUS
Deployment options
On-premise
• Own data center
• Internet-facing deployment (IFD) – only when users
outside internal network
Partner-hosted
• Partner's data center
• Customer access to CRM is usually achieved by
IFD
Online
• Customer subscribes to the Microsoft Dynamics
CRM Online service that is hosted by Microsoft in
its data centers
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 62

63. PRODUCTION FOCUS
Deployment differences
Customization and configuration
option
On-premise Online
Internet Lead Capture feature Not available Included
Scheduled reports feature Included Not available
Query language for custom reports SQL or FetchXML FetchXML only
Maximum number of the custom
entities
Unlimited
Maximum number of the workflow
processes
Unlimited
Custom workflow activities
(assemblies)
Supported Not supported
Custom database indexes Supported Not supported
Database backup As required Upon request
Database restore As required Not available
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 63

64. PRODUCTION FOCUS
MS Dynamics CRM 2011 Deployment: Server roles
Server Role Description Server Group
Discovery Web Service Finds the organization that a user belongs to in a multi-tenant deployment. Front End Server
Organization Web Service Supports running applications that use the methods described in the Microsoft Dynamics CRM SDK. Front End Server
Web Application Server Runs the Web Application Server that is used to connect users to Microsoft Dynamics CRM data. The
Web Application Server role requires the Organization Web Service role.
Front End Server
Help Server Makes Microsoft Dynamics CRM Help available to users. Front End Server
Asynchronous Service Processes queued asynchronous events, such as workflows, bulk e-mail, or data import. Back End Server
Sandbox Processing
Service
Enables an isolated environment to allow for the execution of custom code, such as plug-ins. This
isolated environment reduces the possibility of custom code affecting the operation of the
organizations.
Back End Server
Deployment Web Service Manages the deployment by using the methods described in the Microsoft Dynamics CRM SDK. Deployment
Administration
Server
Deployment Tools Consists of the Deployment Manager and Windows PowerShell cmdlets. Microsoft Dynamics CRM
administrators can use the Windows PowerShell cmdlets to automate Deployment Manager tasks.
Deployment Manager is a Microsoft Management Console (MMC) snap-in that system administrators
can use to manage organizations, servers, and licenses for deployments of Microsoft Dynamics CRM.
Deployment
Administration
Server
Microsoft Dynamics CRM
Reporting Extensions
Provides reporting functionality by interfacing with the Microsoft Dynamics CRM system and Microsoft
SQL Server Reporting Services.
N/A
SQL Server Installs the MSCRM_CONFIG database on the SQL Server. N/A
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 64

65. PRODUCTION FOCUS
Email Router Outlook client
Language
MUIs
Update
Rollups
List
Component for
MS SharePoint
3d party apps
Related tools
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 65

66. PRODUCTION FOCUS
Integration
Organization Service
Protocol: SOAP
http(s)://{ServerName}/{OrgName}/XRMServices/2011/Organization.svc
Organization Data Service
Protocol: OData (REST)
http(s)://{ServerName}/{OrgName}/XRMServices/2011/OrganizationData.svc
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 66

67. SOAP VS REST
REST WS SOAP WS
Abbreviation
Representational
State Transfer
Simple Object
Access Protocol
Standard No standard
Declarative
(standard WSDL is
used)
Support
Numerous content
types
Only XML
Reliability Application specific
WS- Reliable
messaging
Caching
Get operations can
be cached if
desired.
No
Size of message Lightweight
Comparatively
heavy
Implementation Simple Complex
Application areas
Limited bandwidth
and resources
Totally stateless
operations
Caching situations
Asynchronous
processing and
invocation
Formal contracts
Stateful operations
Developer view Resource oriented Object oriented
Transport protocol
support
HTTP HTTP, SMTP, JMS
11/20/2014
MS Dynamics CRM 2011: Architecture
Overview
67

68. PRODUCTION FOCUS
Integrating Microsoft Dynamics CRM & SharePoint 2013
Document
Integration
Extensibility
Analytics
with
PowerView
Business
Connectivity
Services
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 68

69. PRODUCTION FOCUS
SharePoint & CRM are Complementary
Structured &
Semi-structured
Data
Social
Engagement &
Collaboration
Information
Evolution &
Storage
Informal Rules Enterprise
Search
Across Teams
& Domains
Structured
Relational
Data
Social
Interactions &
Tasks
Information
Generation &
Analytics
Formalized
Processes
Data Query &
Filter
Within Teams
& Domains
SharePoint
CRM
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 69

70. PRODUCTION FOCUS
Document Integration
 Out of Box Document
Integration
 Works with
Online & On-Premises (SharePoint & CRM)
 Update for other Browsers (Firefox, Chrome,
etc) coming in December
Native SharePoint Actions
(Check-in, Checkout, …)
Native CRM View of Documents
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 70

71. PRODUCTION FOCUS
Document Integration
 Document Library
Structure
 Document Library per CRM Entity
 Separate Folder for each
CRM Record
Open in SharePoint
button
Documents reside in
SharePoint
Manually Change
Locations if need be
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 71

72. PRODUCTION FOCUS
Windows
Authentication
Claims-based
authentication:
internal access
Claims-based
authentication:
external access
Claims-based
authentication:
internal and
external access
Authentication
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 72

73. PRODUCTION FOCUS
Authentication
Authentication model Scenario
Windows Authentication
Clients authentication using NTLM or Kerberos. Windows
Authentication is used in an intranet environment where all users
are members of your Active Directory domain.
Claims-based
authentication: internal
access
If you have a multiple domain environment where trust does not
exist between the domains, or where some users exist in a
different attribute store such as a partner organization, you can
use claims-based authentication to handle internal user
authentication.
Claims-based
authentication: external
access
Accessing Microsoft Dynamics CRM data over the Internet
through an Internet-facing deployment (IFD) is now done with
claims-based authentication.
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 73

74. PRODUCTION FOCUS
Authentication | Supported authentication scenarios
Deployment Authentication model
Microsoft Dynamics CRM
Online
Claims-based or Active Directory (through federation)
authentication
Microsoft Dynamics CRM
2013 on-premises
Claims-based or Active Directory authentication
Microsoft Dynamics CRM
2013 Internet-facing
deployment (IFD)
Claims-based or Active Directory authentication
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 74

75. PRODUCTION FOCUS
Authentication | AD/ADFS Diagrams
Windows
Authentication
Internal ADFS
External ADFS
Other Identity
Stores, AD,
Windows
Live, Oracle
Etc
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 75

76. SUMMARY
 Microsoft Dynamics CRM 2011 has a multi-tier architecture that provides high scalability, flexibility, and extensibility.
 The presentation tier displays the user interface through the CRM web client, CRM for Outlook, or CRM for the Mobile
clients, and can be customized by using the client-side integration and web resources.
 The application tier runs on the CRM server and includes the web servers, business logic, security, and data access
components. It can be customized by using the server-side integration, workflows and dialogs, and the plugins and
custom workflow activities.
 The data tier stores the customer data and metadata. Customization is supported through metadata changes, but direct
database access is not supported. Every application that interacts with CRM does so through the web services in the
CRM platform. Alternatively, applications can use the SQL-based queries to retrieve the CRM data by using filtered views.
 There is a range of supported and unsupported configuration and customization methods available for Microsoft
Dynamics CRM 2011. The unsupported methods may work initially, but might not work after an update or upgrade and will
not be supported by Microsoft.
 Microsoft Dynamics CRM offers the on-premise, partner-hosted, and online deployment options, with a few
customization and configuration differences between these options.
 Using an implementation methodology, such as Microsoft Dynamics Sure Step, ensures that a proven, repeatable process
is followed so that nothing gets overlooked or omitted.
 A System Administrator or System Customizer security role is required to customize Microsoft Dynamics CRM 2011.
The System Customizer security role has some limitations, such as creating plugins and web resources.
11/20/2014 MS Dynamics CRM 2011: Architecture Overview 76

77. Dmytro Golodiuk
Microsoft Certified Professional
Senior SDE
Zeppelin
SBU Construction equipment CIS
Corporate IT
Mob. +380 (97) 53 88 621
Skype: dimanngo
Dmytro.Golodiuk@zeppelin.com
dimanngo@hotmail.com
www.zeppelin.com
www.zeppelin.ua