Johan Olssons presentation från Microsoft Partner Network där han pratade om Dynamics NAV 2009

1. Microsoft Dynamics NAV 2009 Johan Olsson Dynamics Technical Specialist Microsoft AB

2. Agenda Dynamics NAV 2009 release Architecture comparison Dynamics NAV Service Tier Platform features Deployment perspective

3. Dynamics NAV 2009 Release Microsoft Dynamics NAV 2009 will offer you the choice to stay with the Dynamics NAV Classic client or move to the RoleTailored client Two environments Same application Same development Same Office integration Same Outlook integration RoleTailored Client Classic Client Classic Client Microsoft Dynamics NAV 2009 Microsoft Dynamics NAV 5.0

4. Dynamics NAV Three Tier Architecture Presentation Layer Rich User Interface on clients SharePoint based Portal Business Logic Layer Web Service and Windows Communication Framework Interface Business Logic Running on middle tier server as .NET Application Data Layer SQL Server 2005/2008

5. 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 types allowing them to be reused by NAV Portal and for Web Services Page state (memory) held on both client and NST Fewer triggers than Forms but code is allowed

6. Architecture Comparison

7. Architecture Comparison

8. 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/SIDE architecture to run on Dynamics NAV Server Provide development tools (object designers) for new platform features Leverage .NET Framework for application runtime

9. Dynamics NAV 2009 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

10. Dynamics NAV 2009 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/SIDE Development Environment Reuse much of existing report definitions Use Visual Studio to define the layout

11. Demo New Report Environment

12. Best PracticesAnalyzer for Microsoft Dynamics NAV 2009 SP1

13. Deployment perspective Extra component to install (NAV Server) If deployed on a single box – no impact on network infrastructure If deployed on seperate hardware (SQL, NAV Server on individual servers) Delegation is needed For delegation to work kerberos needs to be enabled Service Principal Names needed for NAV Server and SQL Server

14. BPA – what is it? Experts define the best practice configuration Best Practices Analyzer can detect deviations from best practice Deviations result in lax security, poor reliability or functional problems For complex deployments, correct configuration costs customers Best practices analyzer can therefore reduce total cost of ownership

15. What is it? The Best Practices Analyzer for Microsoft Dynamics NAV 2009 is a tool for identifying issues that can prevent you from successfully deploying a three-tier environment of Microsoft Dynamics NAV 2009. Dedicated page on PartnerSource and CustomerSource with information about the Best Practices Analyzer tool and download links PS: https://mbs.microsoft.com/partnersource/deployment/resources/supplements/BestPracticesAnalyzerNAV2009 CS: https://mbs.microsoft.com/customersource/downloads/servicepacks/bestpracticesanalyzernav2009.htm

16. What can it do? The Best Practices Analyzer for Microsoft Dynamics NAV 2009 performs the following verifications: Verifies that an appropriate version of Microsoft Dynamics NAV Server is installed. Only Microsoft Dynamics NAV 2009 SP1 is supported. Verifies Microsoft Dynamics NAV connection strings. Verifies that the Microsoft Dynamics NAV Server service, the Microsoft Dynamics NAV Web services service, and the SQL Server service, which are required for Microsoft Dynamics NAV, are running. Checks database permissions to make sure that the required resources can connect to the database.

17. What can it do? Verifies that the necessary service principal names (SPN) have been created and correctly configured on the account that is running the Microsoft Dynamics NAV Server service. Verifies that constrained delegation has been configured. The Best Practices Analyzer does not verify that the RoleTailored client or Web services can connect to Microsoft Dynamics NAV Server. You must verify these connections after resolving all issues that are found by the Best Practices Analyzer

18. Demo BPA Tool

19. KerberosComponents Client Service Service Principal Name (SPN) Key Distribution Center (KDC) Authentication Service (AS) Ticket Granting Service (TGS) Tickets Ticket Granting Ticket (TGT) Kerberos Service Ticket (ST)

20. KerberosAuthentication Process Domain Controller KRB_AS_REQ & Response Delegated TGS REQ & Response for ST KRB_TGS_REQ & Response Connection using client’s credentials Connection using impersonated credentials NAV Client NAV Server SQL Server

21. KerberosService Principle Name (SPN) Unique identifier for a service running on a server Cannot have duplicates Document SPNs!! Associated to users and computers using the ServicePrincipalName AD attribute

22. Q and A

23. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. KerberosComponents Client Service Service Principal Name (SPN) Key Distribution Center (KDC) Authentication Service (AS) Ticket Granting Service (TGS) Tickets Ticket Granting Ticket (TGT) Kerberos Service Ticket (ST)

25. KerberosAuthentication Process Domain Controller KRB_AS_REQ & Response Delegated TGS REQ & Response for ST KRB_TGS_REQ & Response Connection using client’s credentials Connection using impersonated credentials NAV Client NAV Server SQL Server

26. KerberosService Principle Name (SPN) Unique identifier for a service running on a server Cannot have duplicates Document SPNs!! Associated to users and computers using the ServicePrincipalName AD attribute

27. Extensibility Installing Demos/Presale Edit In Excel Search OC

28. Tools for Creating Add-Ins

29. Start Web Services Service Modify properties for Microsoft Dynamics NAV Business Web Services Run services.msc Automatic startup Start

30. ComponentHelper Pre-requisite for all demos Downloads and install Client components Client Extensibility Add-ins Automation objects Web Services registration Installation process similar to other demos

31. ComponentHelper – Server Installation Right-click and Install Import .fob in the classic client

32. ComponentHelper – Server Installation DEMO Run Setup Codeunit Modify URL’s

33. Edit In Excel Demo View, modify, create or delete master data Online or offline Conflict resolution “Any” list Customer, Vendor is added by default Other lists can be added manually Business Logic in NAV honored Change spreadsheet and keep data connection DEMO

34. Edit In Excel – Server Installation Right-click and Install Import .fob in the classic client

35. Edit In Excel – Server Installation Run Setup Codeunit

36. Edit In Excel – Server Installation Not compiled F11 YES

37. Edit In Excel – Client Auto Install Just Do It!

38. Edit In Excel – Client Auto Install Yes – of course Open the Installer Package Complete the installation (VSTO3.0 is a prerequisite) Always allow

39. Edit In Excel – Client Auto Install DEMO Excel needs permission to install the template

40. Search Demo Search multiple tables Link and drill into pages in the Roletailored Client Available as System Tray for all platforms (shortcut Windows+Z) Available as Gadget for Windows Vista / Windows 7 DEMO

41. Search – Server Installation Right-click and Install Import .fob in the classic client

42. Search – Server Installation Run Setup Codeunit

43. Search – Client Installation Start NAV Search Right-click and Install (Gadget available for Vista / 7)

44. Search – Client Configuration NAV Search Installation location DEMO Default is W1 – change the Config file if necessary