Microsoft Dynamics NAV 2009

Johan OlssonDynamics Technical Specialist Microsoft AB

Agenda

Dynamics NAV 2009 releaseArchitecture comparisonDynamics NAV Service TierPlatform featuresDeployment perspective

Dynamics NAV 2009 ReleaseMicrosoft Dynamics NAV 2009 will offer you thechoice to stay with the Dynamics NAV Classic client or move to the RoleTailored client

Two environmentsSame application Same developmentSame Office integrationSame Outlook integration RoleTailored

Client

Classic Client

Classic Client

Microsoft Dynamics NAV 5.0

Microsoft Dynamics NAV 2009

Dynamics NAV Three Tier Architecture

Presentation LayerRich User Interface on clientsSharePoint based Portal Business Logic LayerWeb Service and Windows Communication Framework Interface

Business Logic Running on middle tier server as .NET Application

Data LayerSQL Server 2005/2008

Architecture ComparisonFeature Classic Client RoleTailored Client

Forms, Pages, Code on Forms, Codeunits, ”Classic Application Objects”

As today Forms are transformed to Pages, all code runs as .NET managed assemblies, Property driven (Metadata)

Reports/Batch Jobs Existing reports unchanged SQL Server based reporting, requires request forms to be transformed

Web Services Not Available Multi-threaded NST able to handle Web Services. Create, Customize and easily deploy Web Services

C/AL Code runs on the server

XMLPort/Dataport XMLPorts & Dataports supported as today

Enhance XMLPort functionality to cover Dataports

Deployment As today NST automatically updates when new versions are detected

Sharepoint Display Target Continue with existing solutions like NEP

NAV Portal – supported out of the box

NAS As today Will continue to work as currently but recommend moving integrations to WS based platform

Metadata* In the system under the covers, Metadata is type definitions, properties on objects and object definitions themselves. FOB as text object is a textual representation of the metadata of that object

Refers to user personal settings, object definitions, communication packets, properties of the system at runtime

Architecture ComparisonClassic Client RoleTailored ClientC/SIDE Client RoleTailored Client

Authorisation/Authentication

Application Objects Metadata

Presentation Layer New Presentation Layer

Code, Triggers, Validation Simple type validation

NAV Service Tier

Authorisation/Authentication

Application Objects

Code, Triggers, Validation

Web Services

Database Server Database Server

C/SIDE Server or SQL 2005/8 SQL Server 2005/8

Dynamics NAV 2009 Platform Features

Web ServicesIndustry Standard (Basic Profile)

Office, Sharepoint, Infopath3rd Party vendors

Easy to publishFocus point for integrationsEventual replacement for NAS

Business OrientedComplex Data types

Header Lines relationshipsValidation & Triggers

Dynamics NAV 2009 Platform Features

ReportsBased on SQL Report ControlColourfulCharts and GraphsInteractive

Show and hide by expanding/collapsing line informationDynamic Sorting

Reuse the code environment from C/SIDE Development EnvironmentReuse much of existing report definitionsUse Visual Studio to define the layout

Demo

New Report Environment

Best Practices Analyzer for Microsoft Dynamics NAV 2009 SP1

Deployment perspective

Extra component to install (NAV Server)If deployed on a single box – no impact on network infrastructureIf deployed on seperate hardware (SQL, NAV Server on individual servers)

Delegation is neededFor delegation to work kerberos needs to be enabledService Principal Names needed for NAV Server and SQL Server

BPA – what is it?

Experts define the best practice configurationBest Practices Analyzer can detect deviations from best practiceDeviations result in lax security, poor reliability or functional problemsFor complex deployments, correct configuration costs customers Best practices analyzer can therefore reduce total cost of ownership

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 linksPS: https://mbs.microsoft.com/partnersource/deployment/resources/supplements/BestPracticesAnalyzerNAV2009CS: https://mbs.microsoft.com/customersource/downloads/servicepacks/bestpracticesanalyzernav2009.htm

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.

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

Demo

BPA Tool

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)

KerberosAuthentication Process

Domain Controller

NAV Client NAV Server SQL Server

KRB_AS_

REQ &

Res

pons

e

KRB_TGS_

REQ &

Resp

onse

Connectionusing client’s credentials

Connectionusing

impersonated credentials

Delegated TGS REQ & Response

for ST

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

Q and A

© 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.

KerberosComponents

Client Service

Service Principal Name (SPN)

Key Distribution Center (KDC)Authentication Service (AS)Ticket Granting Service (TGS)

TicketsTicket Granting Ticket (TGT)Kerberos Service Ticket (ST)

KerberosAuthentication Process

Domain Controller

NAV Client NAV Server SQL Server

KRB_AS_

REQ &

Res

pons

e

KRB_TGS_

REQ &

Resp

onse

Connectionusing client’s credentials

Connectionusing

impersonated credentials

Delegated TGS REQ & Response

for ST

KerberosService Principle Name (SPN)

Unique identifier for a service running on a server

Cannot have duplicatesDocument SPNs!!

Associated to users and computers using the ServicePrincipalName AD attribute

Extensibility

Installing Demos/Presale Edit In ExcelSearchOC

Tools for Creating Add-Ins

Visual Studio Express C#

Microsoft.Dynamics

Framework.UIExtensibility.dll

Your WinForms controls

Start Web Services Service

Run services.msc

Automatic startup

Start

Modify properties for Microsoft Dynamics NAV Business Web

Services

ComponentHelper

Pre-requisite for all demosDownloads and install Client components

Client Extensibility Add-insAutomation objectsWeb Services registration

Installation process similar to other demos

ComponentHelper – Server Installation

Import .fob in the classic client

Right-click and Install

ComponentHelper – Server Installation

Run Setup Codeunit

Modify URL’s DEM

O

Edit In Excel Demo

View, modify, create or delete master data

Online or offlineConflict resolution

“Any” listCustomer, Vendor is added by defaultOther lists can be added manually

Business Logic in NAV honoredChange spreadsheet and keep data connectionDEM

O

Edit In Excel – Server Installation

Right-click and Install

Import .fob in the classic client

Edit In Excel – Server Installation

Run Setup Codeunit

Edit In Excel – Server Installation

Not compile

d

F11

YES

Edit In Excel – Client Auto Install

Just Do It!

Edit In Excel – Client Auto Install

Yes – of courseOpen the Installer

PackageComplete

the installation(VSTO3.0 is

a prerequisite)

Always allow

Edit In Excel – Client Auto Install

Excel needs permission to

install the templateDEMO

Search Demo

Search multiple tablesLink and drill into pages in the Roletailored ClientAvailable as System Tray for all platforms (shortcut Windows+Z)Available as Gadget for Windows Vista / Windows 7 DEM

O

Search – Server InstallationRight-click and

Install

Import .fob in the classic client

Search – Server Installation

Run Setup Codeunit

Search – Client Installation

Right-click and Install(Gadget available for Vista

/ 7)

Start NAV Search

Search – Client Configuration

Default is W1 – change the Config file if necessary

NAV Search Installation

location

DEMO