Nav2009 architecture overview


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Notes to Presenter:Be sure include a reference that Share Point client is also part of NAV 2009 release – just not shown here. The purpose with this slide is to emphasise that Classic client is part of 2009 relaease too.
  • Key Messages:With pages, groups of Field can be intelligently assembled based on static groupings and based on importance of fields
  • Key Messages:Metadata is ”data about data”Types are metadata (integer, decimal, text, boolean ...)Properties on controls are metadata (visible, enabled, size)Object definitions are metadata (field1 in a table is integer type and primary key, field2 is a text of size 30, ...)User settings stored in the zup file are metadata (last window opened in the system was form100 and it had size x, y)
  • Notes to Presenter: Mention that Visual Studio Express Web Edition has free RDL editor – no extra cost
  • Key Messages:Not only these base 8 functions / including a Codeunit will also expose the methods of that codeunit in the web service
  • Key MessagesThe tool may be run multiple times with more rules and input added to give a better quality transformed Page with each run.
  • Nav2009 architecture overview

    1. 1. MicrosoftDynamics NAV 2009 and Architecture OverviewNameTitleMicrosoft Corporation
    2. 2. Session Objectives• Gain an understanding of NAV 2009Architecture• Understand the role the Dynamics NAV Serverplays in your system and the new features itbrings• In understanding differences between theC/SIDE architecture and the Dynamics NAVthree-tier architecture, it will be easier to plandevelopment projects, customer deploymentsand troubleshoot issues
    3. 3. Agenda• Dynamics NAV 2009 release• Architecture comparison• Dynamics NAV Service Tier• Platform features• Development for Dynamics NAV
    4. 4. Dynamics NAV 2009 ReleaseMicrosoft Dynamics NAV 2009 will offer you thechoice to stay with the Dynamics NAV Classic clientor move to the RoleTailored client• One Solution– Same application– Same development– Same Office integration– Same Outlook integrationRoleTailoredClientClassic ClientClassic ClientMicrosoftDynamics NAV 5.0MicrosoftDynamics NAV 2009
    5. 5. Dynamics NAV Three TierArchitecture Presentation Layer• Rich User Interface onclients• SharePoint based PortalBusiness Logic Layer• Dynamics NAV Server• Web Service and WindowsCommunication FrameworkInterface• Business Logic running onmiddle tier server as .NETApplicationData Layer• SQL Server 2005/2008
    6. 6. Forms and Pages• Classic Client uses Forms– Forms are objects with statically defined UI elements –WYSIWYG– Forms state (memory) is held entirely on the client– Non validation code not encouraged but allowed• RoleTailored Client uses Pages– Structural xml-like definition– Pages can be interpreted by different client typesallowing them to be reused by NAV Portal and for WebServices– Page state (memory) held on both client and NST– Fewer triggers than Forms but code is allowed
    7. 7. Architecture ComparisonFeature Classic Client RoleTailored ClientForms, Pages, Code on Forms,Codeunits, ”Classic Application Objects”As today Forms are transformed to Pages, allcode runs as .NET managed assemblies,Property driven (Metadata)Reports/Batch Jobs Existing reports unchanged SQL Server based reporting, requiresrequest forms to be transformedWeb Services Not Available Multi-threaded NST able to handle WebServices. Create, Customize and easilydeploy Web ServicesC/AL Code runs on the serverXMLPort/Dataport XMLPorts & Dataports supported astodayEnhance XMLPort functionality to coverDataportsDeployment As today NST automatically updates when newversions are detectedSharepoint Display Target Continue with existing solutions like NEP NAV Portal – supported out of the boxNAS As today Will continue to work as currently butrecommend moving integrations to WSbased platformMetadata* In the system under the covers,Metadata is type definitions, propertieson objects and object definitionsthemselves. FOB as text object is atextual representation of the metadata ofthat objectRefers to user personal settings, objectdefinitions, communication packets,properties of the system at runtime
    8. 8. Architecture ComparisonClassic Client RoleTailored ClientC/SIDE Client RoleTailored ClientAuthorisation/AuthenticationApplication Objects MetadataPresentation Layer New Presentation LayerCode, Triggers, Validation Simple type validationNAV Service TierAuthorisation/AuthenticationApplication ObjectsCode, Triggers, ValidationWeb ServicesDatabase Server Database ServerC/SIDE Server or SQL 2005/8 SQL Server 2005/8
    9. 9. Dynamics NAV Server Goals• NAV 2009 Technology Goals– Support new RoleTailored User Experience (UX)– Provide Web Services– Minimize changes in C/AL code from C/SIDEarchitecture to run on Dynamics NAV Server– Provide development tools (object designers) fornew platform features– Leverage .NET Framework for application runtime
    10. 10. Platform Features• Web Services– Industry Standard (Basic Profile)• Office, Sharepoint, Infopath• 3rd Party vendors– Easy to publish– Focus point for integrations– Eventual replacement for NAS• Business Oriented– Complex Data types• Header Lines relationships• Validation & Triggers
    11. 11. Platform Features• Reports– Based on SQL Report Control– Colourful– Charts and Graphs– Interactive• Show and hide by expanding/collapsing line information• Dynamic Sorting• Reuse the code environment from C/SIDEDevelopment Environment• Reuse much of existing report definitions• Use Visual Studio to define the layout
    12. 12. DEVELOPMENT
    13. 13. DevelopmentforDynamicsNAV2009• All development through Object Designer• Export/Import files support FOB, txt and xml• New designer for Pages• External Transformation Tool for Forms toPages conversion• Reports defined in Dynamics NAV, layoutdefined in Visual Studio• After compilation, Dynamics NAV Serversdetect changes and provide newest object toclients
    14. 14. Development• Page Designer– Define source table– Define page type– Design page• Fields and structure• Actions, Related Information• Reports• FactBoxesPage TypesPart PageList PageCard PageSimple PartRole CenterList PartDocument PageWorksheet PageConfirmation DialogNavigate Page
    15. 15. Development• Web Service Designer– Use Page Designer to specify Web service– System auto generates Web service methods– Extend by attaching Codeunits or methods withXMLPort parameters
    16. 16. Form Transformation Tool• Form Transfomation tool converts Form Objects to Page Objects.Forms are not deleted and the tool may be run multiple times.• To enable release of Dynamics NAV with the RoleTailored client• ISVs – To enable release of add-ons with the RoleTailored client• Partners – To upgrade tailored solutions at the customers to theRoleTailored clientDatabase1 RunTransformationToolForms.xmlTransformationInput FilesPages.xml2 341) Export Forms as XML2) Submit Forms and Transformation input file to Transformation Tool3) Transformation Tool makes page objects and logs results4) Import new Page Objects into the database2 Log File3
    17. 17. C/AL Development Considerations• Use Web Services on NST for integrationprojects• Automation objects– Code runs on the NST• Files– Code runs on the NST• Triggers on Controls, Forms/Pages & Reports– Form Transformation tool will detect conflicts foryou and is easy to run with no impact to your sytem
    18. 18. © 2006 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.