How to Manage Data Integration within Microsoft Dynamics

Editor's Notes

• #3: Питання: 1. 2. 3.
• #4: Питання: 1. 2. 3.
• #18: З'являються по порядку
• #25: Common service data tier The data tier is the lowest level and consists of a database (loosely speaking) and a well-defined data access layer. The data management tier with Microsoft CRM supports Microsoft SQL Server as the primary data store. The data access layer provides a consistent programming interface for the service developer, which abstracts platform business logic from the underlying data source. The domain tier is the only direct consumer of the common service data layer. Application and custom business logic Just as there are two distinct presentation clients in Microsoft CRM, there are also two application layers. For the Outlook-based client, a lightweight application framework was built to support the Web-based application logic, but in a disconnected mode. The browser client uses Microsoft ASP.NET application components within an application framework. There is little business logic within the application tiers; the majority of application logic revolves around rendering and data validation. The Microsoft CRM application layer only adds a small amount of customized business logic; the majority was "built-in" to the platform itself. Both application tiers use XML messages to communicate with the underlying platform layer. Communication between the application tier and the platform tier uses SOAP for both Outlook- and browser-based clients. Service tier: domain logic The service tier is responsible for creating problem domain-specific objects. This layer contains the building blocks for an application; but, by itself, is nothing more than a collection of related objects. However, the interaction between those objects within the domain can be assumed to implement more extensible logic, such as the Quote to Order to Invoice processing and pricing logic. The service tier contains more than just the Microsoft CRM business objects. It’s responsible for controlling access to objects and the database, raising events for workflow processes and custom business logic implementations. The user interface and presentation tier Microsoft CRM has two distinct presentation components, Microsoft Internet Explorer as the rich, Web-based4 user experience; and Microsoft Outlook as the rich, Microsoft Windows operating system-based experience. Both components make use of the rendering technology built into Internet Explorer. The internal rendering engine is hosted inside Outlook to present the same general look and feel as the Web application, but without the need for a Web server.
• #30: AdminServer - Provides an access point for the Console and starts Scribe Internal Database maintenance functions if maintenance is enabled. MonitorServer - Hosts the monitoring process. BridgeServer - Hosts processes supporting Publishers and Bridges. MessageServer - Hosts processes supporting Microsoft Message Queuing (MSMQ). EventManager - Hosts automated DTS file execution based on Time, File, or Query.